Nemawashi is the quiet, informal groundwork of talking with each affected stakeholder one at a time, before a decision is formally proposed, to gather their input and build agreement. By the time the proposal reaches the meeting, consensus already exists, so the decision meets little resistance and implements fast.
Most stalled improvements do not fail in design; they fail in the room. A good idea gets sprung on people in a meeting, someone feels blindsided, and the objection that kills it is really about not being consulted. Nemawashi is the Toyota practice that prevents exactly that. It is a pillar of the lean approach to change, and it is the reason some plants can make big changes stick while others relitigate the same decision for months. Toyota formalized it as Principle 13 of the Toyota Way: "make decisions slowly by consensus, thoroughly considering all options; implement decisions rapidly" (Toyota Motor Corporation, The Toyota Way 2001).
What Is Nemawashi?
Nemawashi is the process of discussing a problem and its possible solutions with everyone affected, before a formal decision, to collect their ideas and secure their agreement on the path forward. It happens in hallways and one-on-one conversations, not in the decision meeting itself. The point is not to win people over to a finished plan; it is to shape the plan with their input so that by the time it is presented, it already carries their fingerprints and their support.
Crucially, nemawashi does not mean everyone gets what they personally want. It means everyone gets a genuine, impartial hearing and understands the reasoning before anything is locked in. The result is a decision that is both better, because more perspectives shaped it, and more durable, because no one is defending their ego against a plan they had no part in.
Where Does the Word Nemawashi Come From?
Nemawashi is a gardening term. It literally means "going around the roots," and it describes what a Japanese gardener does before transplanting a tree: rather than yanking it out and hoping it survives, the gardener digs carefully around the root ball over time, trimming and preparing each root so the tree can be moved without shock and will take hold in its new spot. Move a mature tree without that preparation and it dies; prepare the roots patiently and it thrives.
The metaphor is exact. A decision is the tree; the stakeholders are the roots. Skip the groundwork and even a good decision goes into shock when it is transplanted onto the floor, rejected by the very people meant to sustain it. Do the groundwork, and the decision takes root because its roots were prepared to receive it.
How Does Nemawashi Fit the Toyota Way?
Nemawashi is the engine behind one of the Toyota Way's most quoted principles: decide slowly by consensus, implement rapidly. Western management often reads that as a contradiction, because "decide slowly" sounds like indecision. It is the opposite. The slow part is front-loaded consensus-building, all the one-on-one conversations that surface objections, gather better ideas, and align people before the decision is set. Because that work is done up front, the implementation can be fast: there is no one left to convince, no ambush objection, no quiet sabotage from a group that was skipped.
This is why nemawashi pairs so naturally with the rest of the Toyota Way's people practices. It draws on going to the floor to understand the real situation, it feeds structured problem-solving like A3 where the proposal is socialized as it develops, and it is the horizontal cousin of the vertical alignment in hoshin kanri whose catchball is essentially nemawashi applied to strategy deployment.
How Do You Actually Run Nemawashi?
Nemawashi is deliberate, not just "being nice about it." It follows a rough sequence, adapted to how big the decision is and how many people it touches:
- Map who is affected. List every person and group the decision touches, the operators who will run it, the functions it depends on, the people who can quietly block it. Missing a stakeholder here is how you get ambushed later.
- Go to each one, individually, early. Have the conversation before you have a finished plan. Share the problem and your rough thinking, then listen more than you talk. The goal is to learn what you are missing, not to sell.
- Fold their input into the proposal. Actually change the plan based on what you hear. Nemawashi is fake if the plan never moves; people can tell the difference between being consulted and being managed.
- Circle back and close the loop. Return to each stakeholder with how their input shaped the plan, including what you could not take and why. An impartial hearing they can see honored is what earns real support.
- Bring an aligned proposal to the decision meeting. By now the meeting is a confirmation, not a debate. Everyone has already seen the plan, shaped it, and made their peace with it, so the decision is quick and clean.
- Implement rapidly, together. With consensus already banked, move fast. The speed of execution is the visible payoff of all the quiet groundwork that came before.
Why Does Nemawashi Make Lean Changes Stick?
Nemawashi works because it moves the hard conversations before the decision instead of after it. A change forced through a meeting still has to survive contact with the floor, where the people who were not consulted find a hundred quiet ways to let it fail. A change built through nemawashi arrives on the floor already owned by the people running it, so it holds. The trade is simple: pay the time up front in conversations, or pay it later, with interest, in resistance, rework, and abandoned initiatives. There is a second, quieter payoff too. The conversations themselves usually improve the plan, because the operator who runs the step every day knows the constraint the planner missed, and nemawashi is the mechanism that surfaces that knowledge before it becomes a costly surprise. A decision made without those voices is not just harder to implement; it is often simply worse, built on a picture of the work that only looks complete from the office.
What Nemawashi Is Not
Nemawashi is easy to caricature, and the caricatures are worth naming so you can avoid them. It is not backroom politicking to stack a vote; the aim is a better decision through genuine input, not a rigged one. It is not endless consensus-seeking that never decides; the slow phase is bounded, and it exists precisely so the decision, once made, is final and fast. It is not rubber-stamping, where consultation is theater and the plan never changes; if the proposal does not move in response to what people say, it was not nemawashi. And it is not a way to offload the decision; the leader still owns the call, but makes it with far better information and far broader support. Done honestly, nemawashi is one of the clearest expressions of respect for people, gathering the knowledge of those closest to the work before deciding, which is why it underwrites durable employee engagement and a real lean culture rather than a compliance one.
There is a cultural translation to make here, because nemawashi is not a licence for slow decisions in every setting. The skill is matching the depth of groundwork to the stakes: a small change to one station's layout might need a two-minute word with the operator, while relocating a line or changing a shift pattern earns days of careful conversations. Reading that correctly is judgment, not procedure. The failure mode in a hurry-up culture is skipping the groundwork on exactly the big, irreversible decisions where it matters most, and then spending three times as long fighting the resistance that the skipped conversations would have prevented.
Where Does Nemawashi Show Up in a Lean Plant?
You see nemawashi wherever change is proposed and expected to last. Before a line is rebalanced, the person leading it walks the idea past the operators, the material handlers, and maintenance first. Before a new standard is rolled out, it is socialized with the crews who will run it. Before a capital decision, the functions that depend on the equipment are consulted individually. It is also the connective tissue of a good obeya room where cross-functional teams do much of their alignment in the smaller conversations around the walls, not only in the formal review, and it depends on the same honest, shared picture that good visual management puts in front of everyone. The through-line is the same: decisions built with the people who live with them hold, and decisions imposed on them do not. Harmony's own line, "no rip-and-replace," is a nemawashi idea at heart, changing how a plant runs by working with the systems and people already there rather than around them, the same spirit behind our connected-worker approach.