Bring your Japan team in while one decision is still open

Published Sep 8, 2026

Every rollout has someone who does not want it. When that person gets pulled into the process is usually decided by preference rather than design.

Bring them in early and the schedule stretches. Bring them in late and it turns into a fight. Both have happened, so neither settles the question.

The variable is not timing. It is whether anything the person can still change exists on the day you invite them.

Silence in the Japan feedback call is not agreement, and HQ finds out through a metric

“Involve them early” is sound advice. The failure mode I see more often is the early meeting that makes things worse.

Here is the usual shape. HQ locks the global design, then schedules a session with the Japan entity to gather input. Required fields: decided. Stage definitions: decided. Go-live date: decided and already on a board slide. The Japan team is then asked for feedback.

In a Japanese office, objecting in a group meeting to something visibly already approved carries a cost the objector pays personally. It reads as questioning the judgement of people senior to them, in front of an audience, on behalf of a decision they were not part of. So the room goes quiet, someone says the plan looks reasonable, and HQ writes down alignment.

The correction arrives about three weeks after go-live, in the adoption dashboard.

The other outcome is worse. If someone does object across the board, they now hold a position rather than an opinion. Opinions move when information arrives. A position, once taken publicly in front of colleagues, cannot be abandoned without loss of face, and everything after that costs several times more to move.

Neither of those is a timing problem. Both are what happens when you invite someone to a meeting with nothing to hand them.

The objection is about time, about purpose, or about being seen, and only the third one needs the meeting

Filing all of this under “change resistance” leaves exactly one available move, which is more communication.

Split it and other moves appear.

Mazrica’s survey on SFA and CRM usage (fielded by IDEATECH, 25 to 28 November 2024, published 28 January 2025, n=101 sales managers and team leads at Japanese B2B companies; a survey run by a company that sells sales software, on a small sample, so read it directionally) asked why salespeople do not enter data. Entering it takes too long, 54.5%. It is tedious, 39.6%. The benefit of entering it is unclear, 32.7%. And: I do not want my results visible to other people, 27.7%.

That last one rarely shows up in other surveys. It also never gets said out loud in a training session, and it will not be said in your feedback call either.

Keywalker’s survey (fielded 8 to 10 October 2025, published 11 November 2025, n=1,034 sales staff and managers at Japanese companies already using SFA, CRM or BI tools, run online through PRIZMA; a survey by a company that sells BI implementation services) asked the same question from the other side. The strongest motivator to enter data was a clear purpose and a clear use for it, 54.8%, followed by seeing their own results and progress made visible, 40.1%.

Line those up and the objection splits three ways. Time taken. Purpose not visible. Exposure changed.

The first two dissolve with information. The third does not. It only moves if the design moves, or if an operating commitment moves.

So the reason to bring the objector in is not to win agreement. It is to find out, before go-live, where the third one is sitting.

Decide what the Japan entity gets to decide, then the date picks itself

Reverse the order. Do not start from the calendar. Start from what is genuinely transferable.

In a global CRM or process rollout, three decisions can usually be handed to the local team without breaking global consistency.

Which fields are mandatory. Not all of them. Hand it over as a budget: “five fields can be required, HQ sets three of them, you choose the other two”
When data gets entered. Immediately after the meeting, batched at end of day, or before the weekly pipeline review. Let the local team pick the operating rhythm
Which meeting and which report the entered data shows up in. Exposure is the one objection that can only be handled here, and only by naming the audience

None of the three threatens global reporting, which is why they can be given away. Stage definitions, the object model, and whether the rollout happens at all cannot be. Offering to “co-design” something already fixed is the fastest way to lose a Japan team’s trust, and they will not tell you they have stopped believing you.

Once the transferable decisions are named, the date follows. Hold the session shortly before the last day those decisions can still move.

Objections to a decision that already has approval belong outside the room

Not every objection belongs on the agenda.

Japanese decisions carry more people than HQ usually expects. In a survey by Professional Tech Research Institute, part of Bengo4.com (fielded 25 September to 31 October 2024, published 16 January 2025, n=312; respondents were users of the CloudSign e-signature service, so this sample skews toward companies further along with digitisation), the most common complaint about the internal approval process was that too many people are involved before approval completes, at 41.0%. Second was that the consultation and groundwork before the approval document is even written takes too long, at 35.9%.

That second number is the one worth sitting with. A material share of the objection handling in a Japanese company happens before any document exists, in one-to-one conversations HQ never sees. The formal meeting is often where a conclusion is confirmed, not where it is reached.

Use that rather than fight it. An objection to something already approved, such as the investment itself or whether to adopt the platform, should be taken by the local manager one to one, before the session. Put it on the agenda instead and every other attendee reads it as evidence that the decision is still open, and the two things you actually needed decided that day will not get decided.

Handle only the objections that fall inside the decisions you handed over. State that boundary in the first two minutes and it holds.

Invite the objector while one decision is still theirs to make. A meeting with nothing left to change does not produce objections. It produces agreement that does not hold.

Common mistakes

Using one word for “give us input” and “make this call.” The person invited assumes the second. Open by naming the two things they are deciding today
Making the loudest objector the local project owner. That works when the objection was about unclear purpose. When it was about exposure, the objector now writes the operating rules around their own discomfort, and the design gets more rigid rather than less
Adding more enablement sessions to build consent. Repetition answers the purpose objection. It does nothing for the exposure objection, and it does nothing at all once no decision remains

Even after the exposure question is settled, a Japan team keeps entering data only if something comes back to the person who entered it. That design order is covered in why your Japan team won’t log data.

Other notes on the same problem are collected under Change management.