Nemawashi: Building Consensus Before Decisions
Prepare plant decisions through early stakeholder consultation while keeping formal review, approval and release with authorized people.

On this page · 11 sections
- 1What nemawashi actually is
- 2Toyota context: prepare decisions without delaying action
- 3Nemawashi versus consultation, consensus, A3 and change control
- 4How a nemawashi cycle runs from concern to decision
- 5Use an A3 to connect the proposal, evidence and concerns
- 6Apply the regulatory overlay by product and jurisdiction
- 7Worked plant cases: staging, allergen scheduling and instructions
- 8Connect the handoff and recover from changed assumptions
- 9Measure decision quality, not agreement volume
- 10Common failure modes and proportionate controls
- 11Review readiness before moving the proposal forward
How does Nemawashi apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What nemawashi actually is
Nemawashi is a management practice for developing stakeholder acceptance of a proposal before formal approval. The Lean Enterprise Institute definition of nemawashi describes evaluating the idea first, then the plan, with management and stakeholders. The purpose is to gather input, anticipate resistance and incorporate other perspectives and organizational priorities into the proposed change.
In a regulated plant, that commonly means discussing the concern before presenting a finished solution: understand how affected people see the problem, develop a workable proposal, then revise it in light of their concerns. Consultation is useful when it can still change the plan—not merely collect endorsements for a decision already made.
LEI distinguishes this preparation from formal approval, describing a meeting to sign off on the final proposal. That description is not a universal meeting format for plants; the site's applicable approval procedure determines how authorization is recorded.
- Acceptance of the problem means stakeholders recognize the concern deserves attention.
- Agreement with an option means they support a proposed response, potentially subject to conditions.
- Authorization to implement means the designated approvers have permitted the change through the applicable process.
Nemawashi is not a regulatory requirement or a substitute for formal change control. As an operational boundary, keep quality review, approval and release with authorized people, including the applicable QA disposition step. Consultation exposes concerns; it neither entitles the proposer to a favorable decision nor demands unanimity. An unresolved objection remains information for the decision-maker, not something to conceal to demonstrate consensus.
02Toyota context: prepare decisions without delaying action
Toyota’s Toyota Production System overview describes an objective of eliminating waste and shortening lead times to deliver vehicles quickly, at low cost and with high quality. This is context for lean operating priorities, not a regulatory rule for plant decisions.
Applied as management practice, nemawashi involves a trade-off: spend effort preparing a decision now, or risk discovering avoidable conflicts during implementation. A proposed material route may look efficient on a layout but obstruct cleaning access or compete with maintenance work. Discussion grounded in observations at the gemba can expose those conflicts while alternatives remain practical.
That reasoning does not guarantee shorter lead time. Preparation consumes time too. Use value stream mapping to focus discussion on affected flows and handoffs rather than collecting opinions about every aspect of the plant.
Useful consultation needs a defined decision, a named owner and an escalation route for unresolved concerns. Set a review point tied to the decision’s urgency. If a concern remains open, identify who can resolve it and what evidence they need; do not keep circulating the proposal merely to obtain agreement. The aim is informed action, not indefinite discussion.
03Nemawashi versus consultation, consensus, A3 and change control
These approaches answer different questions: whose input is needed, how a proposal develops, how agreement is reached, who decides, and how work proceeds. The comparison below describes common operational usage; terminology and decision rights vary by organization.
| Approach | Main purpose | Typical output | Decision authority |
|---|---|---|---|
| Nemawashi | Iteratively develop a proposal through stakeholder dialogue | Revised proposal and remaining concerns | Remains with designated decision-makers |
| Stakeholder consultation | Gather affected parties’ knowledge and views | Comments, constraints and suggestions | Consultation alone assigns none |
| Consensus decision-making | Reach agreement through a defined group process | Shared position or unresolved objections | As assigned by the organization’s decision rule |
| A3 problem-solving | Structure problem analysis and proposed countermeasures | Concise reasoning summary | Not conferred by the document |
| Formal change control | Assess and authorize controlled changes | Change record and disposition | Designated change approvers |
| Implementation planning | Coordinate execution and dependencies | Tasks, owners and readiness checks | Assigned execution owners within approved scope |
Stakeholder consultation is broad input-gathering: a review meeting or request for comments can qualify. Nemawashi emphasizes using that input to revise the proposal and revisit affected stakeholders, rather than merely collecting responses.
A method for building agreement is not the organization’s decision rule. Specify who decides and how unresolved objections are handled; participation does not itself confer a veto. An A3 can carry the reasoning between conversations, but completing it is not the consultation itself.
As covered above, the authorization boundary remains intact. Formal change control handles the controlled decision; implementation planning organizes execution. Use the site’s quality assurance process to locate applicable approval responsibilities, rather than treating stakeholder support or a populated task plan as approval.
04How a nemawashi cycle runs from concern to decision
Use this suggested facilitation workflow for regulated plant proposals, adapting the depth of consultation to the consequences of the decision.
Frame the decision
Write the decision to be made, the current condition, the affected process and the proposal’s boundaries. Identify what is outside scope and what constraints are fixed. Include a baseline option: continue the current arrangement. Output: a decision brief that makes the case for investigation without presuming that change is necessary.
Map the people affected
Select stakeholders by operational knowledge, exposure to consequences and decision responsibility—not seniority alone. Include operators, maintenance, engineering, planning and quality where relevant. Consider different shifts and downstream users. Output: a stakeholder map stating why each person is involved and who owns the eventual decision.
Investigate before advocating
Discuss the problem before presenting a preferred solution. Use focused conversations and, where useful, observation at the gemba to uncover assumptions, local workarounds, dependencies and contrary evidence. Ask what would make the proposal fail during ordinary work. Output: observations and questions, with facts distinguished from interpretations.
Record positions against a revision
For each stakeholder, record support, conditional support, unresolved concern or objection against the specific proposal revision discussed. Capture the reason and any condition attached. Keep a missing response separate from support; arrange follow-up rather than interpreting silence. Output: a position log that preserves disagreement without reducing it to a vote.
Revise and revisit
Compare alternatives, including the baseline, against the same decision criteria. Assign an owner and a next action to each open question. A material revision affecting workload, risk, interfaces or implementation conditions calls for renewed consultation with affected stakeholders. Output: a revised proposal and updated positions, not inherited agreement from an earlier version.
Prepare the decision handoff
Assemble the proposal, supporting evidence, alternatives considered, unresolved matters and proposed implementation conditions. An A3 summary can orient the decision owner. For remaining objections, state the consequence, owner and requested decision: investigate further, revise, defer or proceed for formal consideration. Carry this package to the formal-approval boundary described above; preserve unresolved positions in the handoff.
- Frame the DecisionIdentify the problem, scope and baseline option.
- Map affected peopleInclude process knowledge, consequences and decision responsibilities.
- Explore the concernTest assumptions before defending a preferred solution.
- Compare optionsConnect alternatives to evidence and operational constraints.
- Revise the ProposalResolve concerns or assign explicit follow-up conditions.
- Confirm review positionsRecord responses against the relevant proposal revision.
- Hand off for DecisionSubmit reasoning, evidence and unresolved matters together.
05Use an A3 to connect the proposal, evidence and concerns
Use an A3 as a readable decision summary, not as the entire controlled record. The following is a proposed practice design for nemawashi consultation, not a mandatory template or a description of any software product’s database.
Structure the summary around the decision
- Problem and current condition: describe the operating difficulty, its boundaries and supporting observations.
- Desired condition and alternatives: explain the intended improvement and credible options, including retaining the current arrangement.
- Evidence and stakeholder concerns: link each material assertion or objection to its supporting record and contributor.
- Proposed decision and follow-up conditions: identify the preferred option, remaining dependencies, accountable owners and the evidence needed to close them.
Keep detail in linked observations, drawings, risk assessments, trial records and other relevant records rather than copying their contents into the A3. Identify the supporting record’s revision or dated state so readers can reconstruct the reasoning. Direct gemba observations should remain distinguishable from conclusions drawn later.
Separate evidence types and concern dispositions
An observation records what was seen or measured. An assumption states something provisionally treated as true. An interpretation explains what the evidence may mean. An acceptance criterion defines how an outcome will be judged; it is not itself evidence that the outcome passed.
For a hypothetical access concern, record a resolved issue if an assessed drawing demonstrates clearance; a condition if a clearance trial remains necessary; or an explicitly unresolved decision item if reviewers dispute whether the proposed criterion is adequate. Preserve the rationale, not merely a closed label.
Preserve identity across revisions
Give the proposal a stable identity and each revision a distinct reference. Attach consultation entries and evidence links to the revision reviewed, retaining contributor and date. Do not transfer earlier agreement silently to changed wording. Give conditions owners and statuses. Link the proposal to a formal change record with its own identity and review state; human approval belongs in that formal process.
Proposal
Defines the decision under discussion.
- proposal_id
- revision
- scope
- decision_owner
Consultation
Preserves a reviewer's position and concern.
- proposal_id
- revision
- stakeholder_role
- response_state
- concern_text
Evidence
Links supporting observations to the revision.
- evidence_id
- proposal_id
- revision
- source_reference
Decision Condition
Makes follow-up ownership and status visible.
- condition_id
- proposal_id
- acceptance_criterion
- condition_owner
- status
Formal Change Link
Connects consultation with the separate review record.
- proposal_id
- revision
- change_record_id
- review_status
06Apply the regulatory overlay by product and jurisdiction
Keep binding law, regulator-issued guidance, industry explanations and management practice distinct. The LEI lexicon explains stakeholder preparation; Toyota’s corporate overview explains its production philosophy. Both are industry material, not regulatory instructions. Nemawashi is a management practice, not a regulatory requirement or a substitute for formal change control.
Applicability checks
| Jurisdiction and product | Scope question | Decision-preparation output. |
|---|---|---|
| US human-drug production | What product and production process are affected? Check the current text and applicability of 21 CFR 211.100 for scope and obligations. | Product/process description and questions for the responsible quality reviewer. |
| US dietary supplements and food | Which product category, process and destination market apply? Use the supplement and food frameworks as separate applicability checks. | Category rationale, process-impact questions and named quality or food-safety reviewer. |
| US medical devices | Which device, manufacturing process and intended market are affected? | Affected operations, supporting evidence and responsible quality/regulatory reviewer. |
| Chemical manufacturing | Which chemical, use, process, site and destination market are involved? | Product/process boundaries and questions assigned to product-stewardship, safety and regulatory reviewers. |
| EU, UK and other-market operations | Which product framework and site obligations apply in each market? | Market-specific applicability questions and responsible reviewers identified before selecting the formal review route. |
Management recommendations
Use consultation to assemble process-impact questions, supporting evidence and responsible reviewers—not to decide legal applicability by consensus. Keep unresolved scope questions visible for specialist review. Label any regulatory guidance separately from binding provisions when preparing the decision record.
Treat software support as a separate implementation choice: assess record routing and traceability against the site’s needs. Software does not make a site compliant; review, approval and release remain human responsibilities.
07Worked plant cases: staging, allergen scheduling and instructions
These hypothetical cases illustrate management practice, not legal requirements or customer results. Each consultation changes a proposed option rather than authorizing implementation. Decisions about authorization remain with the human reviewers and formal route described above.
US pharmaceutical packaging: relocating material staging
Assumptions: A US pharmaceutical packaging operation proposes relocating staging without changing the product or packaging recipe. Initial proposal: Put incoming packaging materials beside the line entrance to shorten collection walks.
Stakeholder concern: Operators identify a blind spot during line-clearance checks. Warehouse staff explain that unused materials return through the same entrance. Quality questions whether incoming and returned materials would remain distinguishable when carts accumulate. Revised option: Retain closer staging, but change the layout to separate incoming and return positions, preserve label visibility and keep clearance inspection points accessible.
Evidence needed: Use a proposed-layout walkthrough and representative cart arrangements to examine material identity, clearance access and return flows. Walking distance in metres per batch and handling events per batch are possible observations, not demonstrated savings. A gemba observation can expose workarounds missing from the drawing. Decision consequence: Advance the separated-layout option for review only if those checks support it; persistent ambiguity would favour retaining the existing staging location.
Food manufacturing: changing an allergen schedule
Assumptions: Products with different allergen profiles share equipment. Initial proposal: Group similar runs into a longer campaign to reduce changeovers, then manufacture a product without the preceding product’s allergen ingredients.
Stakeholder concern: Sanitation identifies inaccessible residue locations and questions whether longer running changes soil removal. Production flags pressure to restart before cleaning work is complete. Quality asks whether existing cleaning evidence covers the proposed transition and campaign conditions. Revised option: Reject grouping solely by scheduling convenience; retain grouping only where the transition and cleaning arrangements have adequate support. Treat campaign changeover planning as a dependency, not proof of cleaning effectiveness.
Evidence needed: Observe changeover duration in minutes per changeover separately from cleaning evidence addressing relevant residues, locations and operating conditions. Decision consequence: Supported cleaning performance under the proposed conditions could justify advancing the revised schedule. An uncovered transition would leave that scheduling option on hold, even if fewer changeovers appear attractive.
Medical-device assembly: revising a work instruction
Assumptions: An assembly task runs across shifts, with different fixture configurations at point of use. Initial proposal: Replace a detailed positioning step with a shorter instruction and a photograph.
Stakeholder concern: Operators on another shift cannot reproduce the pictured orientation using their fixture. Engineering confirms that the photograph assumes a locating feature absent from that configuration. Revised option: Reject the photograph-only revision; retain the clarification objective, but develop instructions matched to the tooling or separately propose tooling standardization.
Evidence needed: Compare observed execution across shifts and fixture configurations against defined assembly acceptance criteria. Record task duration in seconds per unit separately from evidence of correct orientation, sequence and completed assembly. Decision consequence: Consistent execution without verbal rescue could support advancing the matched instruction. Continued ambiguity would send the proposal back for revision, regardless of apparent speed.
08Connect the handoff and recover from changed assumptions
Treat these handoffs as system-neutral design practices, not regulatory requirements. Keep a stable consultation identifier and a revision-specific proposal reference across linked records. Assign an owner to each handoff and identify which record governs each decision, rather than copying a status label between systems.
| Proposed handoff | Reference and responsibility |
|---|---|
| Consultation → change control | Proposal owner links the reviewed revision, unresolved positions and receiving change identifier. |
| Change control → risk assessment | Risk owner links affected assumptions, assessment revision and resulting decisions. |
| Change control → document management and training | Document and training owners link instruction revisions, effective status and associated learning records. |
| Change control → maintenance or production | Execution owner links the applicable work order, trial or production record and returns execution findings. |
Define state mappings explicitly: consultation complete means ready for the designated decision process, not approved for implementation. Keep formal approval and release status separate, with decisions remaining with authorized people. For MES–QMS handoffs or maintenance–production links, assess software for record organization, revision-specific linking, ownership visibility and exception reporting. These are selection considerations, not claims about a particular product.
Recover at the affected boundary
- Changed scope: identify which assumptions, risks and affected roles changed. Issue a revised proposal and return that revision to the appropriate reviewers. Preserve unaffected conclusions with their rationale; do not automatically replay every discussion.
- Contradictory trial evidence: document the discrepancy between the expected and observed result, linking the trial conditions and proposal revision. Follow the site's authorized trial, hold or recovery process rather than treating prior agreement as permission to continue.
- Broken handoff: reconcile record identity, revision and status with the sending and receiving owners before relying on the downstream record. Record the correction and notify affected users. Restoring communication does not reverse physical implementation; any equipment, material or instruction rollback needs its own authorized recovery decision.
09Measure decision quality, not agreement volume
Use a balanced set of practice measures, not a consensus score. Pair consultation speed with information completeness and downstream rework when reviewing proposals entering change control.
- Elapsed time: measure hours from the first circulation of a documented proposal for consultation to its handoff for formal review. Report withdrawn proposals separately rather than treating withdrawal as a fast handoff.
- Active working time: total participant-hours spent preparing, discussing and revising that proposal within the same interval. Keep elapsed hours and participant-hours separate: waiting affects elapsed time; attendance affects effort.
- Early discovery: count distinct material concerns identified before formal review for each proposal. Define material as affecting the proposed decision, controls or implementation conditions; distinguish new concerns from repeated comments.
- Missing information: count proposals returned by formal reviewers because decision-relevant information was absent, alongside all proposals first submitted during the reporting period.
- Downstream rework: count consultation issues reopened after implementation for each implemented proposal, using the same follow-up window and recording the reason.
Supportive-response counts alone cannot show whether evidence was challenged or affected work understood. Compare similar proposal types and risk contexts; avoid a single speed target for unlike changes. Use DMAIC to investigate patterns, setting benchmarks only from measured site data rather than assuming faster consultation means better decisions.
10Common failure modes and proportionate controls
Use these observable signals to diagnose weak nemawashi, rather than judging consultation by attendance or apparent harmony. The controls below are facilitation practices, not regulatory requirements; apply them proportionately to the affected work and decision.
| Failure mode | Observable signal | Practical control |
|---|---|---|
| Predetermined decision disguised as consultation | Feedback can change wording, but never the proposed approach. | Identify what remains genuinely open, distinguish fixed constraints, and state which decisions have already been made. |
| Missing shift or contractor perspectives | Day-shift managers speak for work performed by absent crews. | Map participation to affected tasks and working conditions, not organizational rank; use shift pattern scheduling to identify coverage gaps. |
| Silence recorded as support | Unanswered requests appear among supportive responses. | Keep unanswered requests visible as unresolved participation; distinguish no response from an expressed position. |
| Seniority suppresses dissent | Observations change after the most senior participant speaks. | Gather independent observations before consolidating positions; retain conflicting accounts for examination rather than smoothing them away. |
| Scope moves during consultation | Participants discuss different versions as though they were identical. | Identify the proposal revision, describe the changed scope, and assess whose earlier input needs reconsideration. |
| Rejected alternatives lose their rationale | A materially different option disappears without explanation. | Preserve the reason for rejection and the assumption or evidence behind it, so later reviewers can understand the choice. |
| Consultation continues without a decision route | The same unresolved questions return at successive meetings. | Assign each unresolved question to an owner and use the established escalation path to reach the appropriate decision authority. |
11Review readiness before moving the proposal forward
Use this suggested practice checklist before handing a proposal into formal review. Readiness means the reasoning is reviewable—not that implementation is authorized.
- Decision statement: Identify the decision requested, its scope and what remains outside it.
- Proposal revision: Identify the version being handed over and summarize changes arising from consultation.
- Affected stakeholders: Record whose work is affected, who contributed and any missing perspectives needing follow-up.
- Alternatives: Show the credible options considered, including retaining the current approach, and why the preferred option was selected.
- Evidence and assumptions: Link supporting observations or records; distinguish established facts from assumptions still needing a check at the gemba.
- Acceptance criteria: Separate proposed pass/fail conditions and their basis from stakeholder preferences; identify who will review their suitability.
- Open concerns and dependencies: Give each an owner, follow-up action and resolution point; flag anything that could change the recommendation.
- Formal handoff: Name the decision owner, review route and downstream record references, using the regulatory and integration sections above to check the route.
Introduce the method through a bounded plant proposal with a facilitator and decision owner. Ask whether consultation changed the reasoning, not merely whether participants agreed.
After the decision, review surprises, misunderstood conditions and unnecessary consultation effort. Adjust the local method from those findings rather than impose a universal template. Consider taking recurring coordination problems to management review.
Frequently asked questions
Q.Can a proposal move forward when operators support it but quality still has an unresolved concern?+
It can move forward for investigation or revision, but operator support is not a reason to implement a disputed change. Nemawashi is a management practice, not a regulatory requirement or a substitute for formal change control. Ask quality to identify the specific failure scenario, missing evidence, and acceptable resolution. Record the concern and assign an owner. Keep proposal development separate from implementation authorization and any affected quality disposition decision; those remain with the designated human decision-makers.
Q.How much consultation is proportionate for a small, low-risk plant change?+
Scale consultation to the change’s reach, reversibility, and possible consequences rather than its apparent simplicity. For a tool-storage relocation, a short workplace observation with affected operators may reveal access, cleaning, or mix-up concerns. Include other functions where those concerns touch their responsibilities. A focused discussion and a marked-up proposal may be enough to prepare the decision. If the change affects standard work, include whoever maintains the instructions and whoever performs the task on other shifts.
Q.What should the decision owner do when an affected stakeholder does not respond?+
Treat silence as an unknown, not agreement. Send a focused request stating the proposed change, the question needing their expertise, and when a response would help the decision. Check availability and seek a delegated representative where appropriate. If the missing input could materially change the assessment, pause the decision or escalate through the site’s governance route. Recurring gaps in functional ownership can become a management review topic rather than a repeated chase for individual replies.
Q.When is it reasonable to reopen a rejected proposal after new evidence appears?+
Reopen it when the new evidence addresses the recorded reason for rejection or changes a material assumption. A new sponsor or stronger enthusiasm is not, by itself, new evidence. Summarize the original objection, what has changed, and which uncertainties remain in an A3 problem-solving summary. Invite the people who raised the objection to challenge the revised reasoning. Where rejection followed an unsuccessful corrective action, connect the new evidence to the relevant effectiveness check rather than restarting the discussion without context.
Q.How can nemawashi help during an urgent equipment problem without delaying immediate response?+
Separate immediate response from choosing the longer-term solution. Use the site’s established emergency, equipment-isolation, and product-containment arrangements first; do not wait for a consensus meeting. An abnormality signal can bring the appropriate responders into the discussion. Once the situation is controlled, use brief consultations to compare repair options, identify restart concerns, and assign evidence-gathering tasks. Keep the immediate incident owner clear so that informal discussion does not create competing instructions or obscure who decides the next action.
Q.How should supplier-confidential information be handled during cross-functional consultation?+
Define what each participant needs to evaluate, then share the minimum technical detail that serves that purpose within agreed access arrangements. In a technology transfer, operators may need operating constraints without needing the supplier’s proprietary design details. Use an access-restricted technical annex where appropriate, with a decision summary that preserves relevant risks and assumptions. If confidentiality prevents a competent assessment, seek an authorized disclosure route or an alternative assessment arrangement; do not treat inaccessible information as reassuring evidence.
Q.Can nemawashi work across shifts and sites without gathering everyone in the same meeting?+
Yes. Circulate a shared proposal with explicit questions, collect comments asynchronously, and return a revised version showing how conflicting views were handled. A shift handover report can surface operating conditions that daytime reviewers miss. Across sites, use yokoten to share lessons while inviting each location to challenge their local applicability. Name a coordinator and make the current proposal easy to identify. Reserve live discussion for unresolved trade-offs rather than repeating the same presentation to every group.
Q.How can a team show that stakeholder input changed the proposal without retaining every informal exchange?+
Maintain a concise decision history: the issue raised, the contributing role, the resulting revision, and the reason for accepting or declining the suggestion. Link supporting technical evidence where it matters. Apply attributable recording to this summary so readers can distinguish stakeholder input from the decision owner’s interpretation. Follow the site’s record-retention arrangements; a summary is not permission to discard records designated for retention. The useful test is whether another reviewer can reconstruct why the proposal changed.
Primary sources
Want to see how Nemawashi could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
