Your review cadence sets how long Japan waits for answers
Adoption in the Japan entity is behind the other regions, so HQ does the standard two things. An executive sponsor is named. Japan gets a standing slot in the monthly regional business review.
A quarter later the slide still says amber. Then comes the usual conclusion: Japan needs more change management maturity, or a stronger local leader.
Both readings assume the Japan team is failing to do something. Usually they are waiting for something, and the review you just added is what sets the length of the wait.
Reporting flows up. Almost nothing flows back down
Keywalker surveyed 1,034 people at Japanese companies already running SFA, CRM or BI tools and asked what they actually use their dashboards for. (Published November 2025, 527 individual contributors and 507 managers, fielded online through PRIZMA. Keywalker sells BI implementation services, so read the ratios as orders of magnitude.)
Managers said: checking numbers in the sales meeting 58.2%, reviewing activity 46.6%, tracking performance 41.0%, preparing reports for their own superiors 35.9%. Deciding the next action came last, at 15.4%. Individual contributors put that same item at 20.7%, which is to say higher than their managers.
The further up you go, the smaller the share of reporting that ends in a decision. Confirming, and packaging the confirmation for the next level up, take the top slots.
Rollout reporting inherits that shape by default. Login rates, field completion, training attendance. It looks like work is happening, and that is about as far as it goes. None of it is built to be decided on.
So adding a monthly slot adds a monthly deck, which the Japan team assembles, and returns nothing to them.
The Japan backlog is a queue of decisions with no approval route
About a month after go-live, the local project owner starts collecting requests that nobody in Japan can close.
Can our team be excluded from the new required field, because our deals do not carry that information at that stage. Can we keep double-entering into the legacy ledger this month. If we record the discount on the deal, procurement in another division can see it, and next time someone will point at the rate we approved last quarter, so the rep would rather not type it. Is that intended.
Not one of these can be settled by the Japan sales manager alone, because each one touches another department. None of them carries a monetary value or changes a written rule either, so none of them qualifies for a ringi, the internal written approval that travels a defined route.
The local project owner could raise it directly with the division head. In practice they rarely do. Bringing “can we drop that field after all” to a meeting means going back on a requirement their own team signed off, in front of people from other departments. Do it once and the next item gets harder to table.
The formal route is slow and still returns an answer. The informal one does not
Japanese approval is often described as slow, and by headcount it is. But it has a route, and routes return answers.
The survey on ringi practice from Professional Tech Soken, run inside Bengo4.com (published 16 January 2025, n=312; every respondent uses an electronic contract service, so this sample skews toward digitally advanced companies and the elapsed times are almost certainly shorter than the market as a whole) found that two to three days was the most common answer at 52.5%, and that 73.5% take a day or more. The complaints were about the number of people involved and about the informal pre-alignment that happens before the document is even written.
A request that qualifies for the formal route comes back in days. A request that does not qualify has exactly one destination: the next project meeting, or the next review with you.
On a monthly cadence that is fifteen days on average, thirty at worst. The unofficial decision is slower than the official one.
Two things then happen that you do not see. Nobody raises the backlog in the regional call, because a question about an approved global design, asked in a second language in front of the region, reads as an objection to it. And the team solves it locally. The legacy ledger stays open, the CRM gets whatever the pipeline call needs, the discount does not go in the field.
The Japan team is good at this. Give them no answer and they will still close the quarter. The only problem is that nobody reports the workaround, because it works. A workaround running for a month is not a workaround any more, it is how the Japan office operates.
Meanwhile the adoption dashboard holds up, because it counts logins and filled fields rather than whether the record describes the business. In the cases I have seen, this surfaces about a year in, and not through the dashboard. Through a forecast that does not reconcile.
Set the cadence by days-to-workaround
Ask the local project owner for two dates on every open item: when the request went out, and when local practice changed without an answer. The gap between them is your number. In the rollouts I have worked on it has been somewhere around seven working days, which is roughly how long it takes to conclude that nothing is coming.
Have the list sorted by who can actually close each item. Local manager, local project owner, or someone above both. Count only the third group. That count tells you more about the rollout than the adoption percentage does.
Then put someone who can decide in front of that queue more often than your number. It does not have to be a meeting. Fifteen minutes with a person who holds the decision rights, answering on the spot, beats an hour with a room full of people who each have to check with someone else.
The part only you can do is the delegation. Name one person who can answer these during Japanese business hours without a second approval. Most of what is stuck is genuinely small, and it is stuck because the person authorised to say yes is asleep, or in a different quarter’s priorities.
Stop weekly when the “one decision we need from you” line comes back empty three times running. Not on a date. Keep meeting after the decisions run out and you get reporting written for the sake of the meeting.
One option I would not take is opening a direct escalation line from the Japan team to the global project owner. On wait time alone it is the fastest design. But it routes around the local manager, and in a Japanese organisation that costs them standing in front of their own team. What you get afterwards is a team that stops telling that manager things, and a manager who stops telling you things.
There is a version that keeps the speed without the cost. The list of unresolved items goes out under the local manager’s name, in writing, ahead of the call. Contents reach you directly. The person who owns the relationship is still the one raising them.
Then change what the report contains. Two items in place of a status percentage: the one decision you need from this forum, and what became of the decision made last time.
The first turns the review into a place where things get decided. The second sends the result back to the person who raised it.
Common mistakes
- Treating executive attendance as the intervention. A vice president in the room changes nothing if nobody present can answer on the spot. The number to watch is decisions returned to Japan per review. Two consecutive zeros means you have a reporting forum rather than a decision forum
- Recording the decision in the minutes and stopping there. If it does not get back to the person who raised it, in Japanese, it did not happen. The Japan team is not watching your governance structure. They are watching what became of the one thing they asked
- Reading silence in the regional call as agreement. It is the least likely place for an open question about an approved global design to surface. Collect the backlog in writing before the call
- Cleaning up workarounds as soon as you find them. Each one records how long an answer took. Before removing it, ask when the request went out and when the team gave up waiting. That interval is the only real measurement you have of what your cadence should be
Related reading
Setting the cadence handles the decisions that flow up. Changing what the Japan team’s own weekly meeting runs on is the other half, and is covered in Your Japan team will not read the guide. Change the weekly meeting.
Other notes on the same problem are collected under Change management.