- Why does a Japan lead agree on the call and then a plan stalls anyway?
- Because the live, mixed-language call is often not where the real deliberation happens. In Japanese business practice, disagreement and negotiation are frequently worked through privately beforehand — a process known as nemawashi — so the formal meeting confirms what's already settled rather than debating it in the open. HQ reads the calm agreement as consensus; it's often closer to a formality layered on top of concerns nobody has surfaced yet.
- What should HQ do differently?
- Stop treating the group call as the venue for deliberation. Send the actual proposal ahead of time in Japanese, hold a short private conversation with the Japan lead before the group meets, and use the live call to confirm rather than to ask for the first reaction. The objection you need to hear is far more likely to surface one-on-one than in front of the room.
TL;DR
A Japan office that has been running for a couple of years often looks aligned from HQ's side: the video calls are calm, the Japan lead agrees with the plan, nobody pushes back. Then, weeks later, the plan quietly stalls — a launch date slips, a campaign never gets fully executed, a hire never gets made — with no explicit objection ever recorded. This isn't passive resistance and it isn't a language problem. It's a structural one: real deliberation in Japanese business practice tends to happen privately, before the meeting, through a process called nemawashi, while the formal meeting exists to confirm what's already been worked out. When HQ runs the live call as the only venue for debate, it gets a polite yes instead of the real answer, and only finds out the real answer months later, as a stall with no name attached to it. The fix isn't asking harder for pushback on the call — it's building a private channel where the pushback can happen at all.
Key Takeaways
- A calm call is not proof of alignment. The absence of objection on a live, mixed-language HQ call tells you very little about whether the plan actually works locally.
- Nemawashi means the meeting is often the ratification, not the deliberation. The real back-and-forth may already have happened in a smaller, private conversation before anyone hit "join."
- Silence isn't a personality trait — it's a venue problem. The same person will often raise the same concern clearly, in detail, one-on-one.
- A stalled plan with no recorded objection is a symptom, not a mystery. Look for where the disagreement went, not just why the plan didn't move.
- You can build the private channel on purpose. A short pre-call and materials sent ahead in Japanese do more than a longer, more open agenda on the day.
The Call Where Nothing Went Wrong
Picture a fairly ordinary QBR between a foreign HQ team and its Japan office, roughly two years into the market. The Japan lead is capable, has closed real deals, and speaks good English. The call covers a Q4 push: a new pricing tier, a partner co-marketing push, a target headcount add for the local sales team. Everyone on the call agrees. There are a couple of clarifying questions, nothing that sounds like resistance. HQ leaves the call feeling like the Japan office is finally firing on all cylinders — plan set, team aligned, execution next.
Two months later, the pricing tier still hasn't launched. The co-marketing push happened, but late and scaled down. The headcount add is still an open req. Nobody said no to any of it. Nobody sent an email flagging a problem. It just didn't happen, at roughly the pace everyone agreed to.
Where the Real Meeting Actually Happens
The concept that explains this gap has a name: nemawashi (根回し), literally "going around the roots" — the practice, common in Japanese organizations, of quietly building consensus with the people who matter before a decision is put in front of a formal meeting. By the time a proposal reaches the group, in a well-run Japanese-only process, the real negotiating has usually already happened in smaller conversations. The meeting exists to confirm the outcome, not to discover it.
Now put a foreign HQ team into that same structure, running the meeting Western-style — open floor, real-time debate expected, disagreement welcomed as useful input. The Japan lead on the call is operating inside two different sets of expectations at once. HQ is waiting for live pushback as the signal that people are engaged. The Japan lead may be waiting for the meeting to be the formality it's supposed to be, because the actual working-through of concerns is something that, in their operating context, belongs somewhere else — a private conversation with a trusted colleague, a message sent afterward, not a comment made in front of the group and the people they report to.
Neither side is wrong about how meetings are supposed to work. They're just not running the same meeting.
Why Saying No Live Costs More Than It Looks Like
It's tempting to read the silence as excessive deference, or worse, as a lack of a strong opinion. That's rarely accurate. Raising an unresolved objection live, in a mixed-language call, in front of more senior people from HQ, carries a social cost that a private one-on-one doesn't: it can look like putting someone — often the person running the call — on the spot, in a setting that generally treats visible disagreement as something to handle carefully rather than something to display. The concern doesn't go away. It just moves to a venue where it's safer to say out loud, which is usually not the room HQ is sitting in.
This is also why "we specifically asked if anyone had concerns, and no one raised any" is a weaker signal than it sounds. Asking the group, on the call, in the room where the cost of speaking up is highest, is asking the question in the one place it's least likely to get an honest answer.
The shift in one line: if the objection has to be voiced in the highest-cost setting to count, you've built a process that filters out exactly the information you need.
The Two-Meeting System
The practical fix isn't a cultural-sensitivity slide or a request to "please speak up more." It's a structural change: deliberately separate where deliberation happens from where the decision gets confirmed, and stop expecting the same 30-minute call to do both.
Send the real proposal ahead of time, in Japanese, with real lead time. Not a summary slide dropped in the invite ten minutes before the call — the actual plan, in enough detail that someone can find the parts that won't work, translated well enough that reading it doesn't itself become the obstacle. Two to three business days, not two hours.
Hold a short private conversation with your Japan lead before the group call. Ten or fifteen minutes, one-on-one, in whichever language is more comfortable for them. Ask directly: what part of this doesn't work on your end? What would make this hard to execute by the date on the slide? This is the nemawashi conversation HQ can actually participate in, instead of one it never sees.
Treat the live call as confirmation, not discovery. If the pre-call surfaced a real issue, the group call is where you present the adjusted plan, not the original one. The people in the room see a plan that already accounts for the thing that would have quietly killed it — which is a far more useful outcome than a unanimous yes on a plan nobody could actually run.
The Signal You're Actually Missing
Once you stop expecting the objection to show up live, you start noticing where it actually does. It shows up as a qualified yes rather than a flat no — "let's move forward, though the timeline might need to flex a little." It shows up as a message sent an hour after the call, adding one more clarifying question that, read carefully, is actually the concern. It shows up as a plan that gets full agreement and then slips two weeks later with a reasonable-sounding operational excuse. None of these are lies. They're the same information, delivered through the channel where it was safe to deliver it.
The manager who learns to read a qualified yes as a request for a follow-up conversation — rather than as a green light — catches the real objection weeks before it becomes a missed deadline with no name attached to it.
A Quieter Question for Your Own Calls
You probably already know whether your HQ-Japan calls run smoothly. Most GMs a couple of years in can answer that one; the calls are pleasant, everyone's polite, decisions get made.
Here's the one worth asking instead: when was the last time a plan changed because of something raised on the call itself, live, in the room — as opposed to something that surfaced beforehand, or something that just quietly didn't happen afterward? If you can't remember one, the deliberation isn't missing. It's just happening somewhere you haven't built a way to hear it yet. A Japan Readiness Check looks at exactly this kind of structural gap, not just the words on the page.
Frequently Asked Questions
What is nemawashi, and why does it matter for HQ-Japan calls?
Nemawashi (根回し) is the practice of quietly building agreement with the people involved before a formal meeting, so the meeting itself confirms a decision rather than debates one. On a mixed HQ-Japan call, if your Japan side treats the live call as the real deliberation while your Japan colleagues treat it as the ratification of something already worked out beforehand, both sides can walk away thinking they agreed on something neither fully explained.
Why would a Japan-based employee not just say they disagree on the call?
Voicing an unresolved objection live, in front of a foreign HQ audience and often more senior people, can read as putting someone on the spot in a culture that generally handles disagreement privately and indirectly. It is rarely about lacking an opinion — it is about the venue. The same person will often raise the same concern clearly in a smaller, private conversation beforehand.
How do you tell the difference between real agreement and a polite yes?
Listen for qualified language rather than a flat no: phrases like "let me check internally," "we may need to adjust the timeline," or a plan that gets accepted live but quietly stalls without an explicit objection in the following weeks. A yes with no questions attached, on a plan with real local complexity, is itself worth double-checking rather than taking as a settled decision.
What's a practical way to surface disagreement before it becomes a stalled project?
Separate deliberation from ratification on purpose. Send the actual proposal in Japanese with enough lead time for a private read, hold a short one-on-one with your Japan lead before the group call to ask directly what won't work, and treat the live HQ call as confirming what was already surfaced — not as the first time anyone hears the plan.
Does this only apply to formal negotiations, or also to internal team calls?
It applies most visibly in negotiations and procurement, but the same pattern shows up in ordinary internal planning and QBR calls between HQ and a Japan office. Any recurring meeting where a Japan-based colleague is expected to raise objections live, in English, in front of the people they report to, is a setting where the real conversation is likely to happen somewhere else first.