Most organizational change initiatives fail. Not because the strategy was wrong. Not because the resources were inadequate. Because the change was announced before it was understood, decided before it was built, and implemented before it was owned.
The most effective approach to organizational change I have encountered in practice comes from an unlikely source: the Japanese manufacturing concept of nemawashi. It is not a technology or a framework — it is a philosophy of how decisions get made and how change gets adopted in human organizations.
What Is Nemawashi?
Nemawashi (根回し) is a Japanese term that literally means “going around the roots” — the process of carefully tending to the roots of a plant before transplanting it to ensure it survives the move. In organizational practice, it refers to the process of building informal consensus around a significant decision before it is formally announced.
In Toyota’s production system, nemawashi is standard operating procedure. Before a major change is presented to the team or approved by leadership, the decision-makers spend time in informal one-on-one and small group conversations — sharing the problem they are trying to solve, listening to concerns and perspectives, incorporating input, and building the kind of understanding and buy-in that makes formal adoption much smoother.
The concept sits at the heart of the LEAD leadership and team workshop methodology — because understanding how alignment is built before a decision is announced is one of the most undervalued organizational leadership capabilities.
Why Most Change Initiatives Fail
The standard change management model looks like this: leadership develops the change in a small group, announces it to a wider audience, faces resistance, addresses resistance through communications and Q&A sessions, and then either pushes through the resistance or retreats from the change.
This model has a structural flaw: it treats resistance as a response problem — something that needs to be overcome through better communication after the decision is made. But resistance is almost always a process problem — it is the natural result of people being asked to adopt a decision they were not part of making, do not fully understand, and have not had the chance to influence.
The nemawashi model inverts this sequence. Resistance is minimal not because people were sold the change more effectively after the decision — but because the people who would otherwise resist were consulted during it, and their concerns either shaped the decision or were explicitly addressed before the announcement.
The Four Stages of Effective Organizational Change
Stage 1 — Problem Clarity Before Solution Development
The first stage of effective change is not deciding on the solution. It is building shared understanding of the problem. Most change initiatives skip this stage, moving directly from “here is what we are going to do” to implementation. The result is that people are being asked to change without understanding why the current state is insufficient.
Nemawashi starts with the problem. The leader’s first informal conversations are not about the proposed change — they are about the problem the change is designed to solve. “I have been thinking about X. I am not sure we are addressing it well. What is your read on the situation?” This builds shared understanding of the problem before the solution is on the table.
Stage 2 — Informal Consultation Before Formal Announcement
Once the leader has a proposed direction — even a rough one — nemawashi involves sharing it informally with key stakeholders before any formal process. Not as a consultation theater (where feedback is gathered but does not influence the outcome) but as genuine input-seeking that shapes the proposal.
The conversations are one-on-one or in small groups. They are candid: “Here is what I am thinking. What am I missing? What concerns would you have? What would need to be different for this to work for your team?” The information gathered in these conversations invariably improves the proposal. More importantly, the stakeholders who were consulted become advocates rather than skeptics when the formal announcement comes.
Stage 3 — Incorporation of Concerns Into the Design
The concerns raised in informal consultation should actually change the design of the change. This is what makes nemawashi real rather than performative. If the informal consultation process produces a list of concerns that leadership acknowledges and then proceeds without addressing, it is not nemawashi — it is consultation theater, and it will be recognized as such.
Not every concern can be incorporated. But every concern should be addressed: either “we changed the approach based on this concern” or “we heard this concern and here is why we are proceeding differently anyway.” The explicit acknowledgment that concerns were heard and considered is itself trust-building, even when the answer is “no.”
Stage 4 — Formal Announcement Into Pre-Built Alignment
When the formal announcement of a change is made after a thorough nemawashi process, the room is different. The loudest voices in the room are the people who were consulted and whose input shaped the proposal — and they are advocates rather than skeptics. The questions in the Q&A are informational rather than oppositional. The resistance is lower not because people were persuaded but because they were involved.
Who to Consult and When
Effective nemawashi requires a stakeholder map: who has the most to gain or lose from this change? Who has the organizational credibility to shape others’ views? Who is likely to surface the most important objections? Who needs to be an active advocate for the change to succeed?
These are your primary nemawashi targets. The sequence matters: start with your most trusted advisors who can help you stress-test the proposal. Then move to potential skeptics — consulting them before they hear through other channels turns potential opponents into invested stakeholders. Then the broader influential group. The formal announcement comes after this sequence, not before.
This stakeholder analysis connects directly to the new leadership role entry process — which includes a stakeholder mapping exercise that is essentially a nemawashi preparation tool. The conflict management framework is also relevant here — nemawashi specifically addresses the peer conflict that often underlies resistance to organizational change.
The Identity Dimension of Change Leadership
Nemawashi requires patience. It requires the leader to be genuinely influenced by what they hear. And it requires tolerating the ambiguity of a period where the decision is not yet made. For leaders whose identity is organized around decisiveness and control, this process feels uncomfortable.
But the leader who can slow down before the decision to build genuine alignment moves faster after it. The leader who skips the nemawashi process moves quickly to announcement and then spends months managing resistance. The net time is longer, the implementation quality is lower, and the organizational relationships are more damaged.
Leading organizational change well — through informal consensus-building before formal decision — is one of the most visible expressions of leadership maturity. It requires the Quiet Authority that comes from an identity secure enough to share power, to be influenced, and to trust that the best decisions emerge from broad input rather than individual conviction.
Key Takeaways
- Most change initiatives fail because resistance is treated as a communication problem rather than a process problem.
- Nemawashi — building informal consensus before formal announcement — prevents resistance by involving people during the decision.
- Four stages: problem clarity, informal consultation, incorporation of concerns, formal announcement into pre-built alignment.
- Consult skeptics early — turning potential opponents into invested stakeholders is the highest-leverage move.
- The leader who slows down before the decision moves faster after it.
Frequently Asked Questions
What is nemawashi in organizational change?
Nemawashi is a Japanese concept meaning ‘going around the roots’ — the practice of building informal consensus around a significant decision before it is formally announced. In organizational practice, it involves one-on-one and small group conversations with key stakeholders during the decision-making process, incorporating their input into the proposal so that the formal announcement meets pre-built alignment rather than fresh resistance.
Why do change management initiatives fail?
Most commonly because resistance is treated as a response problem — something to overcome after the decision — rather than a process problem created by making decisions without involving the people who will be most affected. Change initiatives that skip informal consensus-building, announce decisions to people who feel blindsided, and then try to overcome resistance through communication campaigns tend to fail or produce minimal adoption.
How do you reduce resistance to organizational change?
By building alignment before the formal decision is announced. This means: creating shared understanding of the problem first, consulting key stakeholders informally while the proposal is still being shaped, genuinely incorporating their concerns into the design, and making the formal announcement into a room that already understands and has shaped the change. Resistance is not primarily a communication problem — it is a process problem.
What is the role of a leader in organizational change?
The leader’s primary role in organizational change is not to announce decisions and overcome resistance — it is to build the alignment and understanding that makes decisions stick. This requires more front-end investment in informal consultation and genuine input-seeking, and less back-end effort managing the resistance that results when that investment is skipped.
Build leaders who drive organizational change through alignment rather than authority. Explore the LEAD program or schedule a strategy call.
