Nemawashi Consensus Decision Making
Decide slowly by consensus, then implement rapidly
Nemawashi is Toyota's process of building consensus before formal decisions are made. The word literally means 'going around the roots' (preparing a tree for transplanting by carefully working the root system). In practice, it means thoroughly discussing a proposed decision with all stakeholders before any formal meeting, incorporating their concerns, and refining the proposal until genuine agreement exists.
The counterintuitive insight is that slowing down the decision phase dramatically accelerates the implementation phase. In most Western organizations, decisions are made quickly by a few leaders and then spend months being rolled out against organizational resistance. At Toyota, decisions take longer to make but implementation is nearly instantaneous because everyone has already been consulted, their concerns addressed, and their commitment secured.
The A3 report is the primary tool for nemawashi. A single A3-sized sheet of paper (11x17 inches) forces the proposer to distill their analysis, root cause identification, proposed countermeasures, and implementation plan into a concise format. The proposer then takes this document to every affected stakeholder, presenting, listening, revising, and building consensus one conversation at a time.
- The quality of a decision includes the quality of its implementation, not just its logic
- Broad consensus before commitment eliminates resistance during execution
- One-page thinking forces clarity; verbose proposals hide weak logic
- The person proposing a change must personally build consensus with each stakeholder
- A decision that cannot survive stakeholder scrutiny should not be implemented
- Thoroughly Understand the ProblemBefore proposing a solution, grasp the situation at the gemba using genchi genbutsu. Define the problem clearly, identify root causes, and consider multiple alternatives. Document your analysis on a single A3 sheet.Pro tipToyota insists on considering at least three or four alternatives before recommending one. If you have only one option, you have not thought broadly enough.
- Identify All Affected StakeholdersMap every person and group who will be affected by or involved in implementing this decision. Include upstream and downstream functions, not just your direct team. Include people who might oppose the change.Pro tipThe stakeholders you are most tempted to skip are often the ones whose early input would save the most rework later.WarningSkipping nemawashi with a key stakeholder group virtually guarantees implementation problems.
- Take the A3 to Each Stakeholder IndividuallyPresent your analysis and proposal to each stakeholder in one-on-one or small-group conversations. Listen to their concerns, answer their questions, and incorporate their feedback. Revise the A3 between conversations as your understanding deepens.Pro tipThe nemawashi process is as much about the proposer learning as it is about persuading others. Each conversation should refine your thinking.
- Revise Until Genuine Consensus ExistsContinue the consultation process until all stakeholders understand and support the proposal. This is not unanimous enthusiasm but genuine acceptance that this is the best path forward. The formal decision meeting should be a formality.Pro tipIf the formal meeting produces surprise objections, the nemawashi was incomplete. Go back and do more groundwork.WarningConsensus does not mean everyone is delighted. It means everyone has been heard, their concerns addressed, and they can commit to the decision.
- Implement RapidlyWith genuine consensus in place, execute the decision immediately and fully. There should be no rollout delays, no pilot politics, and no passive resistance because the groundwork has been laid.Pro tipTrack the ratio of decision time to implementation time. Healthy nemawashi produces long decision periods and very short implementation periods.
When Toyota decided to enter the luxury car market with Lexus, the decision involved years of nemawashi across engineering, manufacturing, sales, and executive leadership. Chief engineer Ichiro Suzuki spent extensive time building consensus around the audacious goal of matching Mercedes and BMW quality while maintaining Toyota's manufacturing efficiency. Every stakeholder group was consulted about what it would take.
At the Toyota Technical Center, team members at all levels are expected to present A3 reports to the president. The preparation process, which involves extensive nemawashi with colleagues and supervisors, is considered more valuable than the meeting itself because the team member learns deeply through the process of consulting, revising, and refining.
Nemawashi comes from traditional Japanese gardening practice, where moving a tree requires months of careful root preparation to ensure it survives transplantation. Toyota adopted this metaphor for organizational decision making because they observed that decisions transplanted without root preparation (stakeholder alignment) rarely survived implementation.
The A3 reporting format became the standard vehicle for nemawashi at Toyota because it enforced conciseness and structured thinking. A leader cannot hide behind a 100-page report. On a single sheet, every assumption is visible and every gap in logic is exposed, making the nemawashi conversations more productive.