Nemawashi

Definition

Nemawashi is the practice of building consensus through informal, one-on-one discussions with all relevant stakeholders before a formal decision is made or a proposal is presented. The purpose is to surface concerns, gather input, adjust the proposal, and secure alignment — so that when the proposal reaches a formal meeting or approval step, there are no surprises and no opposition that wasn’t already addressed.

At Toyota, nemawashi is not optional politeness or corporate maneuvering. It is a disciplined management practice that ensures decisions are well-informed, broadly supported, and implemented smoothly. A proposal presented without nemawashi — no matter how good — will typically be sent back. Not because the idea is wrong, but because the process was wrong.

Japanese Origin

根回し combines 根 (ne, “root”) and 回し (mawashi, “going around, turning”). The literal meaning — “going around the roots” — comes from Japanese gardening and forestry. Before transplanting a large tree, a gardener cuts and prepares the roots in stages over months or even years, so that the tree survives the move. You don’t just yank the tree out of the ground — you prepare the root system carefully in advance.

The metaphor is precise: a decision, like a tree, has roots — the stakeholders, departments, processes, and people it touches. If you try to move a decision without preparing those roots, the decision fails. Nemawashi is the patient, deliberate work of preparing every root before the move.

History at Toyota

Nemawashi is a broad Japanese cultural practice, not a Toyota invention. It is how decisions are made in Japanese companies, government agencies, and organizations generally. What Toyota did was integrate nemawashi deeply into its management system, making it a structural prerequisite for the A3 process and hoshin kanri.

The A3 connection — John Shook, who worked at Toyota’s headquarters in the 1980s as the first American manager in the company, describes nemawashi as inseparable from the A3 process. Writing an A3 is not a desk exercise — it requires taking your draft to each stakeholder, discussing it, incorporating their feedback, revising, and going back again. The A3 document itself evolves through nemawashi. By the time it reaches formal review, every person who needs to support it has already had input. The A3 is the artifact; nemawashi is the process that produces it.

Ringi-sho and the formal approval system — Japanese organizations traditionally use a ringi (稟議) system, in which a formal proposal document circulates through the management chain for stamp approval (hanko). Nemawashi is what happens before the ringi document circulates. If nemawashi is done well, the ringi is a formality — approvals come quickly because every stakeholder already understands and supports the proposal. If nemawashi is skipped, the ringi stalls or gets rejected.

Hoshin kanri — The catchball process within hoshin kanri is a structured form of nemawashi. Goals and plans are passed back and forth between levels of the organization, with each level providing input and adjusting, until alignment is achieved. This is nemawashi applied to strategic planning.

How It Actually Works

The Process

1. Draft a proposal. Start with a clear articulation of the problem, your analysis, and your proposed countermeasure. At Toyota, this is typically an A3.

2. Identify all stakeholders. Who will be affected by this decision? Who needs to approve it? Who needs to implement it? Who has expertise that could improve it? The list is often longer than you think.

3. Visit each stakeholder individually. Not by email. Not by group presentation. One-on-one, face to face. Explain the situation, present your thinking, and — critically — ask for their perspective and concerns.

4. Listen and revise. This is not a persuasion exercise. The purpose of nemawashi is not to convince people you’re right. It is to genuinely incorporate their input. If a stakeholder raises a valid concern, revise your proposal. If they have information you lacked, update your analysis.

5. Go back to stakeholders whose input changed the proposal. If Stakeholder A’s feedback caused you to change something that affects Stakeholder B, you must revisit Stakeholder B with the revised version. This iteration continues until the proposal is stable.

6. Present the final proposal formally. At this point, the meeting or approval step is confirmation, not debate. Everyone has already contributed. The decision moves forward smoothly.

What Makes It Work

Time invested up front saves time in implementation. A decision reached quickly in a meeting but without nemawashi will face resistance, misunderstandings, and rework during implementation. A decision that took longer to reach through nemawashi moves through implementation with far fewer problems. Toyota’s saying: “Slow decision, fast execution.”

It develops the proposal. Nemawashi is not just about building buy-in — it genuinely improves the quality of the decision. Each stakeholder sees the problem from their angle. Their input catches blind spots, adds relevant information, and strengthens the countermeasure.

It surfaces problems early. If a key stakeholder will block the proposal, you find out in a private one-on-one conversation — not in a formal meeting in front of senior management. This gives you the opportunity to understand their concern and address it, rather than having your proposal shot down publicly.

Common Mistakes

Treating nemawashi as selling. If you go to stakeholders to convince them you’re right rather than to genuinely seek their input, you are not doing nemawashi — you are lobbying. Stakeholders can tell the difference. If you’re not willing to change your proposal based on what you hear, you’re not doing nemawashi.

Doing it by email. Nemawashi requires face-to-face (or at minimum voice-to-voice) conversation. Email does not allow for the nuance, the follow-up questions, the reading of concerns, or the dialogue that makes nemawashi work. Sending an email with “please review the attached proposal and let me know your thoughts” is not nemawashi.

Skipping people who will be affected. If someone learns about a decision that affects them only when it’s announced, your nemawashi was incomplete. The most common failure is skipping the people closest to the work — the ones who will actually implement the change.

Confusing nemawashi with consensus. Nemawashi aims for alignment, not unanimous agreement. The goal is that every stakeholder has been heard, their concerns addressed, and they understand the reasoning — not that every person enthusiastically agrees. In Japanese organizations, silence after proper nemawashi means consent, not disagreement.

Viewing it as slow or bureaucratic. Western managers often see nemawashi as an obstacle to fast decision-making. This misses the point entirely. The speed that matters is not decision speed — it is execution speed. A poorly prepared decision implemented badly is far slower than a well-prepared decision implemented smoothly. Toyota’s overall cycle from problem identification to complete implementation is frequently faster than organizations that skip nemawashi and make “quick” decisions.