NemawashiJapanese: 根回し — "going around the roots"

Nemawashi (根回し) literally means 'going around the roots' — a horticultural term for the practice of carefully digging around a tree's root system before transplanting, so the tree survives the move. Japanese management adopted the metaphor to describe the structured one-on-one groundwork that prepares stakeholders for a decision before the formal decision meeting. By the time the meeting convenes, every person whose support, expertise, or veto matters has been consulted privately, their concerns surfaced, their objections addressed or accommodated, and their position aligned with the proposal. The meeting itself becomes a confirmation, signature, and trigger for immediate implementation — not a debate.

The discipline is misunderstood in Western contexts as 'lobbying' or 'back-room dealing.' That framing is wrong. Lobbying privately pressures decision-makers; nemawashi privately surfaces objections, gathers technical input, and refines the proposal so the resulting decision is genuinely better — not just easier to push through. The proposer is expected to change the proposal in response to what nemawashi reveals. A proposer who runs nemawashi and returns to the meeting with the original proposal unchanged has performed political theatre, not nemawashi.

Jeff Liker's The Toyota Way articulates the discipline as Principle 13: 'Make decisions slowly by consensus, thoroughly considering all options; implement decisions rapidly.' The phrasing is the inversion of the Western default. Most Western organisations make decisions fast (the senior executive decides in the meeting, often without consultation) and implement slowly (because every function discovers the decision after the fact and pushes back, renegotiates, and works around it for months). Toyota does the opposite — and delivers projects in roughly half the elapsed time, because implementation begins immediately and proceeds without political friction.

A nemawashi cycle is structured, not improvisational. The proposer (often a team leader or project manager working an A3) follows a documented sequence: identify the stakeholders, sequence the conversations, document each conversation, refine the proposal between conversations, and only then convene the decision meeting. Toyota teaches the sequence as a 5-step pattern.

1. Identify stakeholders. List every person whose support, expertise, or veto matters for the decision — functional owners, affected operators, regulatory + quality, finance, IT, customer-facing leaders, executive sponsors. Err on the side of including; the cost of consulting an extra person is one conversation, the cost of excluding a relevant person is months of implementation drag.
2. Sequence the conversations. Start with stakeholders most likely to refine the proposal substantively (technical experts, affected operators, function owners closest to the work). Move outward to influencers and decision authorities. Save the executive sponsor for last — they need to see a proposal already shaped by the experts, not a raw idea.
3. Conduct one-on-one conversations. Each conversation walks the stakeholder through the A3 (background, current state, target, root-cause analysis, proposed countermeasure, expected outcome, implementation plan). Listen for objections, technical concerns, blind spots, resource constraints. Capture them. The conversation typically lasts 20–60 minutes.
4. Refine the proposal between conversations. After each conversation, update the A3 to reflect what was learned. The proposal that goes into conversation 7 should be visibly different from the proposal that went into conversation 1 — incorporating accepted refinements, with explicit rationale for rejected refinements. Stakeholders who see their input incorporated become advocates; stakeholders who see their input ignored become blockers.
5. Convene the decision meeting. Only after every stakeholder has been consulted and the refined A3 reflects the consensus does the formal meeting happen. The meeting reviews the A3, surfaces any remaining residual objections (rare if nemawashi was done well), signs the decision (with Part 11 e-sig in regulated environments), and triggers immediate implementation. Meeting typically takes 30–60 minutes for a decision that would have consumed half a day in a non-nemawashi culture.

Nemawashi conversations are not held empty-handed. The vehicle is the A3 — Toyota's one-page (A3 paper size) structured-storytelling artefact that captures the proposal in a form a stakeholder can absorb in 5 minutes and respond to substantively. John Shook's Managing to Learn (LEI, 2008) is the canonical reference. The A3 evolves through the nemawashi cycle: an early A3 carried into the first conversation may have placeholder root-cause analysis or a tentative countermeasure; by the final conversation the same A3 has been refined through every stakeholder's input.

Left side of the A3 = Plan (background, current condition, target, root-cause analysis, countermeasures). Right side = Do/Check/Act (implementation plan, measured results, follow-up actions). The constraint of one page forces brevity, prioritisation, and visual thinking. Stakeholders mark up the A3 during the conversation; the proposer takes the marked-up A3 away and incorporates the input. Version-stamping the A3 makes the refinement visible — a mature nemawashi cycle produces v1 through v8 of the same A3, each one visibly improved.

In regulated manufacturing nemawashi is the discipline that makes change control, CAPA, and hoshin-kanri actually work. The change-control board, the CAPA review board, and the management review meeting all formally require multi-function input — but in practice, when the input is solicited only at the meeting itself, the meetings degenerate into either rubber-stamp theatre (if executives push through) or paralysed renegotiation (if functions block). Nemawashi between the proposer and each affected function before the meeting transforms the meeting from a debate into a confirmation.

• 21 CFR 211.100 (a) / 211.160 / EU GMP Ch.4 — change control. 'Any change to a written procedure must be reviewed and approved.' Pre-meeting nemawashi with QA, production, validation, regulatory and engineering means the change-control board reviews a proposal already aligned with each function's constraints. Approval times collapse from weeks to days.
• 21 CFR 820.30(i) / ISO 13485 §7.3.9 — design changes. Design changes require review + approval by independent functions. Nemawashi between the design owner and each independent reviewer before the formal review meeting collapses the cycle from typical 4-6 weeks to 1-2 weeks without sacrificing rigour.
• 21 CFR 820.100 / 211.192 — CAPA. CAPA effectiveness depends on the countermeasure being accepted by the function that has to execute it. Nemawashi between the CAPA owner and the executing function before the CAPA closure meeting means the executing function has shaped the countermeasure and owns it.
• ICH Q10 §3.2.3 — change management. 'An effective change management system ensures continual improvement.' The 'effective' qualifier is the nemawashi requirement — change management that produces decisions nobody owns is ineffective.
• ICH Q10 §2.7 / 21 CFR 820.20 / ISO 13485 §5.6 — management review. Management review meetings without nemawashi degenerate into status-theatre. Pre-meeting nemawashi between the QA owner and each functional leader on each agenda item produces management reviews where decisions are made with executive engagement, not at executive arms-length.
• Hoshin kanri catchball — 2-4 rounds of structured nemawashi up + down the cascade. The 'catchball' metaphor is nemawashi institutionalised at strategic scale.

• Stakeholder coverage — % of identified stakeholders consulted before the decision meeting. World-class >95%; below 80% means meetings will surface unresolved objections.
• A3 revision count — how many revisions the A3 went through during nemawashi. Healthy: 4-8 revisions reflecting substantive input. <2: nemawashi was performative. >12: scope was unclear, proposer was iterating without convergence.
• Decision-meeting duration — meetings should compress to 30-60 minutes for decisions that previously took half a day. If meetings are not compressing, nemawashi was not done.
• Time from decision to first implementation action — target <48h. Toyota benchmark: same-day. If implementation lags, decision was not actually aligned.
• Post-decision change rate — % of decisions revisited or reversed within 90 days. World-class <5%. Above 15% means decisions were forced through without genuine alignment.
• Stakeholder engagement survey — 'I had meaningful input into the decisions that affect my work.' Toyota cultures score 70%+. Western non-nemawashi cultures typically score <30%.
• Total delivery time (decision + implementation) — the only metric that matters. Nemawashi cultures consistently deliver in half the calendar time of fast-decision cultures.

1. Confusing nemawashi with lobbying. Lobbying pressures stakeholders; nemawashi surfaces their objections and refines the proposal. If the proposer returns from nemawashi with the original proposal unchanged, it was lobbying.
2. Skipping the A3. Conversations without a shared artefact produce divergent stakeholder understandings. Every stakeholder reacts to a slightly different proposal in their head, and the meeting cannot converge.
3. Sequencing wrong. Going to the executive sponsor first produces a 'because the boss said so' dynamic that suppresses substantive input from the experts. Save the executive for last.
4. Excluding inconvenient stakeholders. The stakeholder you do not consult becomes the implementation blocker. Err on inclusion.
5. Treating nemawashi as a one-off. Major decisions require multiple nemawashi cycles as the proposal evolves; one round is rarely enough for substantive change.
6. Running nemawashi but not changing the proposal. Stakeholders who see their input ignored become more obstructive than stakeholders who were never consulted. Visible refinement is the trust-building mechanism.
7. Calling rapid-fire individual approvals 'nemawashi.' A 5-minute hallway 'are you OK with this?' is not nemawashi. The discipline requires substantive 20-60 minute conversations with the A3 in hand.

V5 ships nemawashi as the substrate under change control, CAPA, management review, kaizen, and hoshin catchball. The platform does not replace face-to-face conversations — but it does enforce the structure, capture the A3 evolution, track stakeholder coverage, and prevent decision meetings from convening without the groundwork.

• A3 workspace integrated with change control, CAPA, kaizen, hoshin tactic and management-review agenda item. Every decision has an A3; the A3 is versioned automatically; every revision carries a delta-summary and the conversation that drove it.
• Stakeholder identification matrix. Per decision type (change control, CAPA closure, design change, hoshin tactic) a default stakeholder list pre-populates; proposer adds context-specific stakeholders; matrix tracks consulted / pending / dissenting status per stakeholder.
• Conversation logging. Each nemawashi conversation is logged with date, attendees, summary of input, accepted refinements, rejected refinements (with rationale), and stakeholder position (support / neutral / dissent / blocking). Captured at the conversation, not retrospectively.
• Pre-meeting readiness gate. The decision meeting cannot be scheduled until stakeholder coverage threshold is met (configurable per decision type — typical 90%+ for change control, 80%+ for kaizen). Forces the discipline before the meeting calendar fills.
• A3 revision dashboard. Every A3 shows revision count, delta-summary per revision, stakeholder coverage, and time-in-nemawashi. Proposers see their A3 health; coaches see the population.
• Catchball workflow integration. Hoshin catchball uses the same nemawashi engine — 2-4 rounds of structured conversation up + down the cascade, A3-equivalent X-matrix versioning, dissent capture, and final commitment.
• Decision meeting record. The meeting itself produces a record auto-populated from the A3, stakeholder positions, and nemawashi log. Decision sign-off is Part 11 e-sig; implementation triggers fire immediately.
• Effectiveness verification at 90 days. Was the decision implemented as designed? Did stakeholders execute willingly? Did implementation surface issues nemawashi should have caught? Feedback loop refines the stakeholder matrix for future cycles.
• Regulated overlay (211.100 / 211.160 / 820.30(i) / 820.100 / 211.192 / ISO 13485 §5.6 / §7.3.9 / ICH Q10 §3.2.3 / §2.7 / EU GMP Ch.4). Change control + CAPA + management review + design control all share the nemawashi substrate — auditors see one coherent decision-making discipline, not parallel compliance processes.
• Part 11 + Annex 11 audit trail. Every A3 revision, conversation log, stakeholder position update, readiness-gate decision and final sign-off is timestamped, attributed, and retained.
• Mobile-safe (iPhone ≤390px). Nemawashi conversations happen on the floor and on the road — A3 review, conversation logging, and stakeholder updates all work on mobile.