Before you add another Japan dashboard, write the threshold

The Japan region now has its own dashboard, the data flows nightly, and the regional review still ends without a decision.

The reflex at HQ is to add a view. It rarely works, because the missing piece is not the number. It is the sentence that says what the number has to reach and what happens when it does.

Visibility is not the constraint in Japan

Japanese sales organisations are close to evenly split on whether they decide with data at all. In HubSpot Japan’s annual survey (published 19 February 2024, fielded 24 to 27 November 2023, n=1,545 sellers at companies with 51 to 5,000 employees, commissioned by HubSpot and fielded by Macromill), 44.5% said their organisation prioritises data in how it runs, evaluates and decides on sales activity, and 55.5% said it prioritises human judgement. In the same survey, 79% reported some difficulty using their data, and 28.1% said data inside the sales department is not properly managed.

Gartner’s survey of data use at Japanese companies (published 8 January 2026, fielded September 2025, individuals at Japanese companies; the sample size is not stated in the press release) found that only 2.4% report sufficient results company-wide, and 13.8% report sufficient results in part of the business. The top reasons given for low engagement were that the data people want is hard to obtain, that using data in day-to-day work is difficult, and that data quality and reliability are low.

None of those three is solved by another view.

Why a bare number stalls a Japanese decision

A Japanese decision usually has to survive more than one approval layer. In the IDEATECH and Hiroyasu Kitagawa joint study (published April 2026, n=307, restricted to people who took part in a B2B purchase of 3 million yen or more alongside at least one colleague), 60.9% of purchases required two approval stages and more than 80% required two or more.

That study describes buying decisions, not internal reporting. But the mechanism is the same one your Japan team faces internally when they ask for budget, headcount or a pricing exception. The person who reads your dashboard is not the person who approves. They have to carry the number upward, in writing, to someone who has never seen the view.

A number travels through that structure only when it arrives with a rule attached. “Pipeline coverage is 2.4x” invites debate at every layer. “Coverage below 3x for two consecutive months triggers a demand-generation review” is something a manager can put in a request and get signed.

Write one line per metric, then cut the rest

The order matters. Write the rule first, then keep only the numbers needed to test it.

• If attainment is at or above 85% and new-logo share is at or above 30%, approve the additional spend.
• If opportunity-creation rate falls five points below its trailing three-month average, review lead sources within one week.
• Name the conditions under which an exception is allowed, and require one line of reasoning whenever one is granted.

Three rules that someone owns beat nine dashboards that no one opens. Note also that in the HubSpot survey above, internal meetings and internal reporting have ranked at the top of wasteful activities in all five annual rounds. A view built for reporting adds reporting time.

The principle

One generalisation is worth keeping.

Before you add a metric, decide what number triggers what action, in one line.

Take one figure from your last Japan review and write that line. If you cannot write it, the metric does not belong in the review.

Numbers are held to decide with, not to display. The wider frame is in Japan Market GTM and Messaging.

Related reading

Be careful which statistic the threshold is built on. Why Japan’s “3% SaaS churn” benchmark misleads your HQ shows what happens when an average carries an outlier.

Other notes on the same problem are collected under Revenue data.