Working With Japan · Module 4 of 7
How Decisions Get Made
The decision you're waiting for was made before the meeting started. This module shows you the machinery, and how to work it instead of fighting it.
By the end of this one
10 min read
You'll be able to:
- Take a decision you're waiting on right now, drop it into the five stage lifecycle, and name the stage it's stuck in.
- Run one 'nemawashi' conversation with the four moves, starting with your 'senpai' and then the person most likely to object.
- Disagree with someone senior using the four move stack, so your point lands and nobody in the room loses face.
Before you start
What stuck from last time
Three questions on Module 3: Decode the Room. Pulling it back out of memory is what makes it stick, and that beats re reading the module. Nothing here gets saved or scored.
'Nemawashi' is the practice of building agreement one private conversation at a time, before a decision is ever discussed in a meeting. By the time a proposal reaches the conference room, everyone who matters has seen it, shaped it, and agreed to it. The meeting ratifies what the conversations built.
The word comes from gardening. 'Nemawashi' literally means digging around the roots of a tree and preparing them, carefully and over time, so the tree survives transplanting. Move the tree without the root work and it dies, and the same is true of a proposal.
Module 3 taught you to read the room. This module explains why the room reads the way it does, because the meeting you learned to decode was never where the decision happened.
The decision lifecycle
A Japanese corporate decision runs through five stages, and only one of them is visible from the conference room.
- 01 Idea
- 02 Nemawashi Serial one to one talks
- 03 Soft alignment
- 04 The meeting Ratification
- 05 Execution
Where the decision is actually made, and the part a visitor never sees
The only stage on your calendar
Where the decision is actually made, and the part a visitor never sees
The only stage on your calendar
- 1.
Idea
Someone sees a problem or an opportunity and starts sketching a proposal.
- 2.
Nemawashi
One to one conversations with everyone affected, in rough order of influence. The proposal changes with each one.
- 3.
Soft alignment
The refined proposal circulates. Everyone who matters knows where everyone else stands.
- 4.
The meeting
The group ratifies, in public, what it already agreed in private.
- 5.
Execution
It starts fast, because nobody is discovering the decision for the first time.
This is why raising a fresh objection in a Japanese meeting lands so badly. The room hears it as interrupting a ceremony, and it exposes whoever ran the process, because a surfaced objection means someone was left out of the conversations.
Why the system exists
'Nemawashi' survives because it solves three problems at once. It preserves 'wa', the group harmony you met in Module 1, by moving disagreement into private rooms where nobody loses face. It distributes risk, because a decision everyone shaped has no single owner to blame if it fails.
And it builds real buy in. People execute with conviction what they helped author, and by ratification day the proposal has many authors.
A 2024 review of Japanese corporate decision making found exactly this trade. 'Nemawashi' and the related 'ringi' approval system build inclusivity and spread risk, while costing speed on individual decisions and raising the risk of groupthink (Kawaguchi, 2024).
So any one decision takes longer, and the organization as a whole usually ends up moving faster.
Two sequences, compared
The direct sequence
Looks fast, often slow
The decision arrives early and the calendar looks efficient. The cost lands later, paid by whoever has to execute against people who never agreed out loud.
The nemawashi sequence
Looks slow, often fast
Nothing visible happens for weeks, then the meeting takes twenty minutes and the work actually starts. Same destination, less total time.
The direct sequence
Looks fast, often slow
Idea, then the meeting, then open debate, then a decision.
The debate is public and the decision is quick. Then execution slows, because the resistance that never spoke in the room does its work afterward.
The Japanese sequence
Looks slow, often fast
Idea, then serial one to one conversations, then refinement, then ratification.
The alignment is built in private and the meeting is short. Execution starts fast, because everyone already agreed and helped shape the plan.
Neither sequence is right everywhere. But if you run the direct sequence inside a 'nemawashi' culture, you'll get polite nods in the meeting and three weeks of silence afterward, which is exactly the story most frustrated foreign managers tell us.
The framework
The Nemawashi Conversation Script
One conversation, four moves. Use it before your next proposal.
- 1.
Open with relationship
Start with the person, their work, their team. The conversation is happening inside a relationship, so give the relationship a few minutes first.
- 2.
Frame as half formed
Bring a draft and call it a draft. Saying 'I'm still shaping this and I'd value your view' gives them room to change it. A finished proposal only leaves them yes or no.
- 3.
Listen, don't defend
Every concern that comes out here is one that won't ambush you in the meeting. Take notes, ask follow up questions, and skip the urge to win the point.
- 4.
Close with shaping
'Could I come back with a refined version next week?' Now they expect the next draft, and their fingerprints are on it.
You're shaping the proposal rather than selling it, and the other person ends up a co author of the thing you bring to the room.
From our channel
The first move of the script comes first for a reason. Japanese business trust is built person to person before it's built task to task, and Jay explains the two kinds of trust in this lesson.
How to disagree without breaking anything
'Nemawashi' conversations will put you in rooms where you disagree with someone senior. The disagreement stack gives you four moves, used in order, that let you say a hard thing without forcing anyone to lose face.
1. Frame indirectly
Open with 'I may be misunderstanding, but…' and everyone has an exit before you've said anything.
2. Add context first
Walk through the data you're both looking at before you give your reading of it. Your point then arrives as an observation rather than a challenge.
3. Offer it as a question
'Would it be worth considering…?' does more work than anything else in the stack, because a question lets a senior person pick the idea up as their own.
4. Defer authority
Close with 'I'd value your perspective on this.' You've said the hard thing, and the decision is still visibly theirs.
Run the stack a few times and your Japanese colleagues usually start inviting your directness, because you've shown you understand what it costs.
Voice research supports the design. A 2023 review found that flagging problems is consistently harder for employees than offering ideas, and that a context that makes speaking feel safe matters more than any particular phrasing (Morrison, 2023). The stack builds that safety into the sentence itself.
Never skip cold
One rule sits above the whole system. Never take a proposal above your 'senpai' without briefing them first.
An engineering lead we trained learned this the expensive way. He sent a genuinely good idea two levels up, his manager heard about it secondhand, and the manager lost face in front of his own boss. The idea was adopted, and the relationship took six months to repair.
Skipping levels reads as an attack on the chain you met in Module 3, even when you meant it as initiative. Brief your 'senpai' first, every time, and the chain becomes the thing that carries your idea upward.
Try this week
Run one nemawashi conversation
Before your next proposal, book fifteen minutes with the person most likely to object. Use the four moves: open with relationship, frame it as half formed, listen without defending, and close with shaping.
One conversation is a small investment, and it changes what happens in the room. The objection you hear in private this week is the one that won't kill your proposal in public next week.
Companion toolkit
The Decision Phrase Bank
25 phrases in 5 categories that surface hesitation, clarify decisions, and make silence speak. The printable companion for every conversation in this module.
Open the phrase bank →
Before you go
Common questions
What does 'nemawashi' literally mean?
'Nemawashi' comes from gardening. It means digging around the roots of a tree and preparing them, carefully and over time, so the tree survives transplanting. In business it means building agreement through private one to one conversations before a decision reaches a meeting.
Is 'nemawashi' just office politics?
It can look that way from outside, and the difference is purpose and transparency. Everyone knows the process is happening, the proposal genuinely changes as people shape it, and the goal is buy in rather than advantage. Lobbying sells a fixed conclusion, while 'nemawashi' revises one.
Doesn't 'nemawashi' make decisions slower?
For a single decision, yes. For the organization, often no, because execution starts with everyone aligned instead of colliding with hidden resistance. Research on Japanese corporate decision making finds the same trade: more inclusivity and shared risk, at the price of speed on any one call.
Who should my first 'nemawashi' conversation be with?
Your 'senpai' first, always, so nobody senior is surprised later. After that, the person most likely to object, because their concerns improve the proposal most and their support carries the most weight in the room.
← Previous · Module 3
Decode the Room
What 'hai' really means, why pauses matter, and how to hear the polite no.
Next · Module 5 →
Write So It Lands
The five shifts that make your email readable in a Japanese office.
Want your team to practice these conversations out loud before the stakes are real? That's what our workshops are for. See how we work or email us.
About this module
Written and designed by Peak Potential Consulting, and free to use. Print it, share it with your team, and keep the credit with it. If you quote or adapt it, name us and link back. For use inside a paid training programme, talk to us first.
© 2026 Peak Potential Consulting · peakpotentialconsulting.com · hello@peakpotentialconsulting.com