Nemawashi is a Japanese management concept describing the informal groundwork performed before a formal decision or major change.
The idea is to discuss the proposal with affected people early, understand concerns, gather knowledge, and improve the plan before the formal approval point.
It is not secret lobbying.
Done well, it is disciplined preparation.
Why Nemawashi matters
Large decisions often fail because the formal meeting is the first time key people see the proposal.
That creates predictable problems:
- hidden technical concerns;
- resource conflicts;
- resistance;
- missing information;
- cross-functional surprises.
Nemawashi moves those discussions earlier.
Understand before persuading
The purpose is not simply to convince everyone to agree.
A stronger approach asks:
- What does this team know that we do not?
- What operational constraint have we missed?
- What risk do they see?
- What support will be required?
- What would make the proposal more practical?
This is consistent with Respect for People, because people are involved as contributors to the decision.
Nemawashi and Change Management
Change Management helps people adopt and sustain a new way of working.
Nemawashi strengthens the front end of that process by creating understanding before the formal rollout.
People who help shape the solution are more likely to understand both the reason for change and the tradeoffs behind it.
Nemawashi vs Catchball
Nemawashi and Catchball both involve two-way communication, but they are not identical.
Catchball is strongly associated with Hoshin Kanri and the back-and-forth alignment of objectives, measures, and plans.
Nemawashi is broader. It refers to preparing the ground for a decision or change through early dialogue.
Avoid false consensus
Nemawashi should not be used to hide disagreement.
If important concerns remain, they should be visible.
The goal is better-informed alignment, not artificial unanimity.
Practical use
Nemawashi is especially useful before:
- major capital decisions;
- organizational changes;
- process redesign;
- policy changes;
- strategic initiatives;
- cross-functional projects.
The larger the dependency between groups, the more valuable early dialogue becomes.
Common mistakes
Presenting a finished solution and calling it consultation, speaking only with supporters, avoiding difficult objections, delaying decisions indefinitely, and treating disagreement as disloyalty all weaken the approach.
Practical sequence
- Define the proposal clearly.
- Identify affected stakeholders.
- Discuss the proposal before the formal decision.
- Ask for operational and technical concerns.
- Identify dependencies and resource needs.
- Refine the proposal.
- Resolve major disagreements where possible.
- Make the formal decision with fewer surprises.
- Communicate the final rationale.
- Follow through on commitments made during discussion.
The practical lesson
Nemawashi improves decision quality by moving important conversations earlier.
The formal meeting should confirm a well-understood proposal, not discover basic problems for the first time.