Nemawashi
Nemawashi is the practice of holding informal consultations before making a formal decision. A project proposer speaks with stakeholders individually across affected departments. The proposer shares a draft proposal on paper with each person. They discuss concerns and gather practical feedback during these one-on-one visits. The author revises the document on the spot based on their input. All disagreements are resolved before the formal meeting takes place. The final decision meeting confirms the agreed plan without debate.
- First visit at the press
- The engineer shows the one-page proposal to the maintenance technician. He rests his hand on the die cart. He notes that 12 minutes of setup is external work. The press can run during that time. He agrees to the plan if the plant builds a second die cart first. Nemawashi begins at the work site with the person who maintains the equipment.
- Second visit at the bench
- Four people stand together near the assembly line. The supervisor holds a clipboard while an operator points at the white sheet. They discuss staffing for the changeover. The team decides the second person will come from this line. No new hire is needed. Nemawashi brings operators into the planning before any schedule changes take effect.
- Third visit at the desk
- The controller reviews the sheet at an office desk overlooking the shop floor. He points a pen at the numbers beside his calculator. He limits the second die cart cost to $4,000. He also requests a four-week pilot before permanent adoption. Nemawashi resolves budget limits and testing conditions before anyone submits an expenditure request.
- Fourth visit in the office
- The plant manager reads the sheet in her glass-walled office. She holds her chin while reviewing the targets. She sponsors the proposal on one condition. The four-week pilot must show 25 minutes or better per changeover. Nemawashi allows leadership to set clear success thresholds before the formal sign-off meeting.
- Fifth visit in the meeting
- All five stakeholders gather in a glass meeting room around a table. A round wall clock marks a 10-minute session. The plant manager signs the white sheet. No one raises new objections during the meeting. Nemawashi ensures that all disagreements are addressed one on one beforehand. The final meeting serves only to confirm shared agreement.
Key facts
- Japanese term
- 根回し — preparing the roots
- Claim
- 40 → 20 min changeover
- Visits before meeting
- 4
- Cart cap
- $4,000
- Pilot
- 4 weeks
- Meeting
- 10 min
By Matthew Savas — Founder of Kaizumi. Reviewed 2 September 2026.
Nemawashi is the practice of conducting informal consultations before making a formal decision. The term originated in Japanese horticulture. It refers to digging around the roots of a tree before transplanting it. In lean management, nemawashi prepares an organization for technical and operational changes. A project proposer speaks with stakeholders individually across departments. The proposal is shared on paper and revised through one-on-one dialogue. By the formal meeting, all participants have reviewed and adjusted the proposal. They have resolved disagreements and accepted the implementation plan. The final meeting confirms consensus rather than hosting debates.
Horticultural origins and translation to lean management
In traditional Japanese gardening, nemawashi describes preparatory root care before tree relocation. Gardeners dig a narrow trench around the root ball months before moving it. They cut lateral roots to stimulate the growth of small root hairs. These fine root hairs absorb moisture and nutrients after the relocation. The tree survives the transplant without experiencing root shock or dying.
Industrial organizations adapted this practice for complex decision-making processes. Toyota integrated the concept into its management system during the twentieth century. Abrupt operational mandates often trigger strong organizational resistance. When leaders announce sudden procedural changes, projects encounter hidden resistance and delays. Technical obstacles often emerge late in the implementation timeline. Nemawashi prevents organizational shock during operational transitions. The practice identifies process constraints before finalizing any proposal. It incorporates practical frontline feedback into the plan before work begins.
Stepwise consultation on a press changeover proposal
A practical case illustrates how nemawashi functions in a production facility. A process engineer wants to improve changeover performance on a stamping press. The baseline die changeover requires 40 minutes of total downtime. The engineer proposes cutting the changeover duration to 20 minutes. This improvement relies on SMED techniques to streamline tasks. The engineer outlines the proposed setup on a one-page document. The plan shifts the changeover from a single worker to a two-person team. Instead of scheduling an immediate decision meeting, the engineer conducts four individual visits.
The engineer begins the process at the stamping press on the gemba. She reviews the one-page proposal with the maintenance technician. The technician reviews the setup sequence and notes physical bottlenecks. He identifies that 12 minutes of the setup is external work. The press can continue operating while technicians prepare tools nearby. However, a two-person setup requires a second die cart. The technician agrees to the plan if the plant builds the cart first. The engineer amends the proposal to include building the second cart first.
The engineer carries the amended sheet to the assembly bench line. She meets with the shift supervisor and two line operators. They discuss staffing requirements for the new two-person changeover routine. A dedicated setup worker would require hiring additional factory staff. The supervisor analyzes workload distributions across the bench line. The team determines that the second person will come from this line. The changeover will not require hiring a new worker. The operators suggest standard visual cues for coordinating the swap. The engineer adds these frontline adjustments to the document.
The engineer visits the plant controller at his office desk. The controller reviews the revised proposal with his financial calculator. He assesses the expense of manufacturing a second die cart. The controller caps the fabrication cost at $4,000. He also requires a four-week pilot before approving permanent changes. The trial period will verify cycle times and process safety. The engineer adds the $4,000 budget limit and pilot condition to the sheet.
The engineer visits the plant manager in her office. The plant manager reviews the one-page document and the accumulated amendments. She evaluates the labor plan, the capital limit, and the pilot schedule. The plant manager agrees to sponsor the project under one condition. The four-week pilot must achieve changeovers of 25 minutes or better. The engineer documents this target threshold on the sheet.
The formal decision meeting takes place after completing all four visits. Five stakeholders gather around a conference room table. The scheduled meeting lasts exactly 10 minutes. The plant manager signs the finalized sheet. No participants raise new objections during the session. Because everyone modified the document earlier, the team starts implementation immediately.
Integration with structured problem solving
Nemawashi integrates directly with A3 problem solving workflows. An A3 report condenses problem analysis, countermeasures, and schedules onto a single page. The compact size makes the document portable during shopfloor investigations. Authors carry the sheet directly to workstations to gather critique. Lean practitioners do not view the A3 as a static presentation. The document acts as a dynamic communication device throughout the consultation phase.
Every one-on-one conversation generates technical refinements and updates. This systematic iteration supports broader kaizen initiatives across an enterprise. Direct participation fosters personal ownership among operational staff. Employees do not view the approved plan as an imposed management decree. They recognize their own recommendations within the finalized operational standards. This mutual agreement eliminates passive resistance during standard work deployment.
Operational boundaries with catchball and ringi
Organizations frequently confuse nemawashi with other Japanese collaborative management methods. Clear boundaries distinguish nemawashi from catchball and ringi.
Catchball is the structured negotiation of targets across organizational levels. It forms the operational backbone of hoshin kanri strategic deployment. In catchball, senior executives propose high-level organizational targets. Frontline managers analyze operational capabilities and return pragmatic resource proposals. The objective moves vertically between levels until mutual targets are established. Catchball defines what goals the company commits to achieve.
Ringi represents the formal administrative circulation of a decision document. In this system, a written proposal circulates among authorized managers. Each manager presses their personal seal onto the page to record authorization. Ringi provides legal and administrative validation for organizational expenditures.
Nemawashi provides the informal groundwork that precedes both catchball and ringi. It occurs before an author circulates a ringi document for executive stamps. It resolves technical disagreements before formal catchball reviews begin. Without nemawashi, ringi proposals often stall due to unaddressed managerial concerns. Without nemawashi, catchball discussions can degenerate into adversarial budget disputes. Nemawashi tests concepts informally, allowing stakeholders to modify proposals without losing face.
Alignment with lean management principles
The nemawashi process embodies the core lean principle of respect for people. Imposing unannounced procedural changes disregards the professional insights of frontline staff. Consulting operators directly recognizes their detailed understanding of daily machine operations. Nemawashi also protects interpersonal relationships within technical teams. Public meetings often create social pressure and defensive postures.
When challenged publicly, individuals tend to defend initial assumptions aggressively. One-on-one dialogues permit open discussion of operational risks and personal uncertainties. Stakeholders can express logistical doubts without fear of public embarrassment. Authors can resolve departmental friction privately before presenting shared solutions. This private alignment preserves organizational trust while improving technical accuracy.
Barriers to effective consultation
Improper execution of nemawashi can introduce organizational waste and operational friction. A common failure occurs when consultation becomes a tool for coercion. If managers use private discussions to enforce compliance, psychological safety disappears. True nemawashi requires an author willing to modify core assumptions based on feedback. If the author ignores valid feedback, consultation becomes an empty corporate ritual.
Another operational error involves consulting too many uninvolved individuals. Broadcasting proposals to unnecessary departments causes analysis paralysis and project delays. Proposers must limit consultations to stakeholders directly impacted by the countermeasure. Targeted discussions ensure that the groundwork remains rapid and purposeful. When teams execute nemawashi correctly, project implementation proceeds rapidly. Early alignment eliminates downstream design revisions, union grievances, and equipment rework.
Structural comparison of decision tools
Different lean tools serve distinct functions during organizational decision-making cycles.
| System | Primary function | Communication format | Administrative status |
|---|---|---|---|
| Nemawashi | Build consensus and refine plans | Informal one-to-one dialogue | Informal preliminary groundwork |
| Catchball | Align targets with capabilities | Iterative vertical discussions | Structured strategic framework |
| Ringi | Authorize formal operational decisions | Sequential document circulation | Formal administrative approval |
| A3 report | Document root cause investigations | One-page structured summary | Working technical document |
Frequently asked questions
- What is the horticultural origin of nemawashi?
- In traditional Japanese gardening, nemawashi describes the preparatory root care performed months before relocating a tree. Gardeners dig a trench around the root ball and cut lateral roots to stimulate fine root hairs that absorb nutrients and moisture after transplantation. Industrial organizations adapted this technique to introduce operational changes smoothly and prevent organizational shock.
- How does nemawashi differ from ringi?
- Nemawashi is the informal, one-on-one dialogue used to test ideas, resolve technical disagreements, and modify proposals before formal submission. Ringi is the subsequent administrative process where a written proposal circulates among authorized managers to collect formal approval stamps. Without nemawashi to address managerial concerns beforehand, ringi documents often stall during circulation.
- How does nemawashi differ from catchball?
- Catchball is a structured negotiation that moves vertically between management tiers to align high-level goals with operational capabilities in hoshin kanri. Nemawashi is the informal consultation across departments that resolves operational friction before formal discussions begin. While catchball establishes what targets an organization commits to achieve, nemawashi lays the groundwork so proposals can be evaluated without defensive conflict.
- What operational mistakes cause nemawashi to fail?
- Nemawashi fails when managers use private consultations to coerce compliance instead of modifying plans based on critique, which destroys psychological safety. It also breaks down when authors consult uninvolved departments, resulting in analysis paralysis and unnecessary project delays. Successful nemawashi requires limiting discussions to directly affected personnel and genuinely adjusting proposals to incorporate operational feedback.
- How does nemawashi function within A3 problem solving?
- In lean problem solving, an A3 report serves as a dynamic communication device that an author carries directly to workstations on the gemba. Authors use the one-page document during one-on-one visits to gather frontline critique and update technical assumptions on the spot. This iterative consultation ensures that affected workers see their own input reflected in the standard work, preventing passive resistance during rollout.