Digging Around the Roots
Imagine you want to transplant a large tree. If you just yank it out of the ground, the roots tear and the tree dies. Instead, skilled gardeners spend weeks carefully digging around the roots, loosening the soil, and preparing the root ball — so that when the tree is finally moved, it survives and thrives. This is the literal meaning of Nemawashi (根回し): "digging around the roots."
In business, Nemawashi — popularized by Toyota as part of the Toyota Production System — means building informal alignment before the formal decision. It is the practice of having one-on-one conversations with every key stakeholder before the meeting where the decision will be made. By the time the group convenes, there are no surprises. Concerns have been heard. Objections have been addressed. The formal meeting becomes a confirmation of a decision that has already been shaped collaboratively.
The Common Mistake:
You walk into a meeting with 12 people, present a brand-new controversial idea — say, replacing your monitoring stack with OpenTelemetry — and expect everyone to agree on the spot. They won't. Here's why:
- Surprise triggers defensiveness. People who hear an idea for the first time in a group setting feel ambushed. Their instinct is to find problems, not solutions.
- Public disagreement escalates. In a group, people feel they must defend their position to save face. A concern that could have been resolved in a 10-minute hallway chat becomes a 45-minute debate.
- Information asymmetry. You've spent weeks thinking about this. They've spent 30 seconds reading your slide. The conversation is inherently unequal.
The Nemawashi Method — Step by Step:
1. Identify Stakeholders
List every person who will be in the decision meeting, plus anyone who could block the decision even if they're not in the room — for example, a VP whose team is affected but who won't attend.
2. Map Their Concerns
For each stakeholder, predict their likely objection. The security lead will ask about compliance. The SRE lead will ask about reliability. The finance person will ask about cost. Write these down before you pick up the phone.
3. Conduct 1-on-1 Conversations
Meet with each stakeholder individually — coffee, a walk, a 15-minute video call. The script is simple: "I'm working on a proposal to do X. Before I bring it to the group, I wanted to get your perspective on [their specific concern area]. What am I missing?"
4. Listen and Incorporate
This is the critical step. You are not selling. You are genuinely gathering input. If the security lead raises a valid concern about audit logging, you modify your proposal to address it. If the SRE lead suggests a phased rollout, you incorporate that. If your proposal doesn't change through Nemawashi, you either had a perfect proposal (unlikely) or you weren't actually listening.
5. Close the Loop
Go back to each person: "Based on your feedback, I changed the proposal to include [their suggestion]. Does this address your concern?" Now they feel like a co-author, not a critic. This is the step most engineers skip — and it's the most important one.
6. The Formal Meeting
When the group convenes, your proposal already reflects everyone's input. The security lead sees their audit logging requirement on slide 7. The SRE lead sees the phased rollout on slide 9. They nod. The meeting takes 20 minutes instead of 2 hours.
When Nemawashi Fails:
Nemawashi is not manipulation or back-room dealing. It fails when: (a) you use it to avoid legitimate debate rather than to prepare for it, (b) you selectively share different information with different stakeholders, creating conflicting expectations, or (c) you treat it as a checkbox exercise — "I talked to them" — rather than genuinely incorporating feedback. The goal is not to eliminate disagreement. It is to ensure disagreements surface early, in low-stakes settings, where they can be resolved constructively.
When asked "Tell me about a time you drove a technical decision across multiple teams," structure your answer around the Nemawashi pattern: (1) I identified the stakeholders, (2) I met with each one individually to understand their concerns, (3) I incorporated their feedback into the proposal, (4) the final meeting was a formality because alignment was already built. This demonstrates organizational awareness and influence without authority — exactly what staff+ interviews probe for.
Key Point: Nemawashi inverts the typical decision flow. Instead of "present → debate → decide," it becomes "consult → incorporate → confirm." The investment is front-loaded — more 1-on-1 time — but the total time-to-decision is dramatically shorter because you eliminate the multi-meeting debate cycle. Senior engineers who master this pattern can drive decisions that would otherwise take months.