Continuous Improvement Culture

Nemawashi

Prepare the roots quietly. So the meeting is a confirmation, not a fight.

Updated
·
4
min read
Definition

What is Nemawashi?

Nemawashi is the Japanese lean practice of building consensus quietly, one conversation at a time, before a decision is made in public. The word literally means "preparing the roots," a gardening metaphor for the careful work that happens before a tree gets transplanted. In manufacturing, it is the behind-the-scenes alignment that makes a decision meeting a confirmation rather than a fight.

Nemawashi is one of the most useful lean disciplines and one of the least taught. The word means "preparing the roots," and it refers to the quiet, careful alignment work a decision-maker does in one on one conversations before a decision is announced in public. It is the opposite of the surprise announcement at the all-hands meeting. Done well, it makes the formal meeting fast and the implementation smooth. Skipped, it produces meetings that go too long and decisions that get sandbagged afterwards.

"If the meeting is the first time anyone hears your proposal, the meeting is already broken."

How nemawashi works

Nemawashi is a sequence of short conversations, usually one on one, with each person who will be affected by an upcoming decision. The conversations happen in the days or weeks before the formal meeting. The proposer does not show up to lobby; they show up to listen. They share the rough shape of what they are thinking, name the trade-offs they are wrestling with, and ask the other person what they are missing. They take notes. They go back to their desk and adjust the proposal.

Three things make nemawashi different from political lobbying. First, the proposer's goal is to improve the proposal, not to sell it. If a concern is real, the proposal changes. If a concern is misinformed, the proposer clarifies and the concern resolves. Second, the conversations are direct, not strategic. There is no triangulating against opponents; there is only honest conversation with each affected party. Third, the proposer is willing to abandon the proposal if the conversations reveal it is wrong. Nemawashi is sometimes how a bad idea gets killed quietly before anyone wastes a meeting on it.

The output of nemawashi is twofold. The proposal that walks into the formal meeting is a sharper, more realistic version of what the proposer started with. And the people in the room have already had their concerns heard privately, so they show up ready to confirm rather than ready to fight. The meeting is short. The decision sticks because nobody feels surprised or steamrolled.

Where nemawashi fits on the shop floor

Imagine the operations manager of a 40-person plastics injection shop who wants to move from two long shifts to three shorter shifts to reduce overtime. Without nemawashi, they bring it to the leadership meeting in October. The HR lead is blindsided about scheduling, the maintenance lead pushes back on the changeover cadence, and the shift supervisors are furious that they were not consulted. The meeting goes three hours. The decision gets tabled. Two months later, nothing has changed.

With nemawashi, the same manager spends two weeks before the meeting having five quiet conversations. They sit with HR and walk through the scheduling implications. They walk the floor with the maintenance lead and look at when changeovers would actually happen. They have coffee with each shift supervisor and ask what they would worry about. Each conversation surfaces something. HR points out a compliance issue with one proposed shift length. Maintenance suggests a different changeover window. One supervisor names a real concern about handoffs that gets folded in.

By the time the meeting happens in November, the proposal has been adjusted three times. The leadership meeting takes 30 minutes because everyone in the room has already shaped their piece. The change rolls out in January and sticks because the people who had to make it work helped design it.

Common mistakes with nemawashi

  • Confusing it with lobbying. Lobbying is selling a fixed proposal. Nemawashi is willing to change the proposal. The difference shows up fast.
  • Skipping it for "speed." Skipping nemawashi is usually slower in total because the meeting that follows goes longer and the implementation gets sandbagged.
  • Talking to allies only. Nemawashi works best with the people most likely to push back, not the people guaranteed to agree.
  • Going behind backs. Nemawashi is private but not secret. Everyone affected should get a conversation, not just the convenient ones.
  • No follow-through in the meeting. If the formal meeting ignores what was discussed privately, trust in nemawashi collapses for the next round.

Nemawashi and related Lean tools

Nemawashi is the quiet one on one cousin of catchball, the more structured public dialogue. Both feed into hoshin kanri, the lean planning system that cascades breakthrough goals through the organization. Underneath both practices is the lean principle of respect for people, the idea that the workers affected by a decision should help shape it. Together these practices form the backbone of what most texts call lean leadership, the discipline of leading without surprising the people who do the work.

Common questions

The questions we hear most about this term.

How does nemawashi work in practice?
Before a decision needs to be made in a meeting, the person proposing it has a series of short one on one conversations with everyone who will be in the room. The point of these conversations is not to lobby. It is to hear concerns, surface objections, and adjust the proposal where the feedback is right. By the time the formal meeting happens, the people in the room have already had their say privately. The meeting is shorter, the decision is better, and nobody is blindsided. The discipline is patience: nemawashi takes days or weeks, not hours.
How is nemawashi different from catchball?
They overlap but they happen differently. [Catchball](https://arda.cards/glossary/catchball) is usually structured and public, often part of a formal planning cycle, with explicit back and forth rounds of proposal and pushback. Nemawashi is quiet and individual, conversations between two people behind the scenes. Catchball happens in the meeting. Nemawashi happens in the hallway before the meeting. A healthy lean organization uses both. Nemawashi prepares the ground so catchball can be productive instead of contentious.
Is nemawashi the same as catchball?
No. Nemawashi is the private one on one alignment work; catchball is the public iterative dialogue. The Japanese tradition treats them as separate disciplines that work together. Nemawashi makes catchball easier because the surprises have already been worked out. Catchball does the formal commitment in the open. A meeting that opens with everyone hearing the proposal for the first time is missing the nemawashi step, and the meeting almost always goes longer and produces worse decisions than it should.
Why does nemawashi matter in lean manufacturing?
Because most bad decisions in manufacturing happen when the people affected hear about them in the meeting where they get announced. They push back hard, the decision gets watered down or stuck, and the result is a compromise nobody likes. Nemawashi prevents that. By the time the meeting happens, the people who would have objected have had their objections heard. The good ones got folded into the proposal. The proposal that survives is the one that already has the rough consensus. Decisions implement faster because the resistance has already been worked through.
What does nemawashi look like on the shop floor of a small manufacturer?
Quiet enough that you almost miss it. The owner of a 30-person fab shop wants to change the layout of the assembly bay. Before the all-shop meeting where they would announce it, they spend a week having five minute conversations with the lead assembler, the kitting tech, the materials handler, and the shift supervisor. Two of those people raise practical concerns that the owner had not thought of. The owner adjusts the proposal. By the time the all-shop meeting happens, the people who actually work in the bay have already shaped the change, and the meeting is fifteen minutes of confirmation instead of two hours of arguing.
From the blog

Go deeper

Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.

No items found.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.