Nemawashi: The Japanese Art of Consensus That Gets Results Faster Than You Think

I spent ten years in a Canary Wharf trading floor where decisions were made in meetings. Quick ones. Three people in a room, one person talking, the rest nodding or objecting. Someone won. Someone lost. We moved on.

In 2019, I was brought into a project to restructure a client's internal communications. Classic deadline-driven initiative. We had four weeks. I proposed the strategy in a formal presentation to the executive committee. Eight senior people. I'd prepared slides, anticipated objections, built the case.

The meeting lasted 90 minutes. It was like watching a parliament of academics debate a footnote. Every person had a different concern. Every concern required clarification. By the end, we had provisional buy-in but zero momentum. Three weeks later, when implementation should have been underway, we were still resolving interpretations of the original proposal.

That's when my grandmother called me from Kyoto.

I wasn't looking for business advice from a 78-year-old who'd never worked in finance. But she asked how the project was going, and I told her the truth: it was stalling. She said something in Japanese that I'd heard my whole childhood but never understood as practical wisdom:

"Nemawashi shinaide wa, kaigi wa nagai." "If you don't do the groundwork, the meeting will be long."

That phrase — nemawashi (根回し) — contains a concept I'd been raised around but had completely abandoned in my rush to be efficient. It's the practice of laying groundwork before a formal decision. It sounds slow. It's actually the fastest way to reach durable consensus. And it's the reason Japanese organizations, for all their reputation for slowness, often execute decisions faster than their Western counterparts once the formal meeting happens.

This is what I want to share with you: not as exotic Japanese wisdom, but as something that works. Something I wish I'd taken seriously ten years earlier.

What Nemawashi Actually Means (And Why the Translation Matters)

The word itself is agricultural. *Nemawashi* literally means "going around the roots." In gardening, before you move a large tree, you don't just dig it up. You spend weeks or months carefully cutting around the root system, loosening the soil, letting the tree adjust. When you finally transplant it, the roots are already prepared. The tree survives.

The business metaphor is direct: before you propose a decision, you prepare the ground. You talk to key stakeholders individually. You listen to their concerns. You adjust your thinking based on what you hear. By the time you call the formal meeting, the roots are already loosened. The proposal doesn't shock anyone. The "meeting" is a formality — a public acknowledgment of consensus that's already been built.

Philosopher and essayist Yoshida Kenkō wrote in his 1330 collection Essays in Idleness about the importance of preparation and groundwork in human affairs, though he didn't use the specific term. What he described was the same principle: the most effective action is the one where invisible work happens first.

But nemawashi as a formal business practice emerged during Japan's rapid industrialization in the Meiji and Taisho periods (1868-1926), when traditional consensus-building methods had to be adapted for larger organizations. By the postwar period, it had become embedded in Japanese corporate culture — not as a quaint tradition, but as operational standard.

American business consultant and Japan expert Jon Woronoff documented this in detail in his 1980 work Japan's Wasted Workers. He observed that Japanese companies took longer to reach decisions but executed them faster because the consensus was genuine and pre-built. Western companies made quicker initial decisions but faced constant re-negotiation during execution.

The distinction is crucial: nemawashi isn't about being nice or avoiding conflict. It's about resolving conflict before the formal decision, so the decision itself is clean.

Why the Western Meeting Culture Gets This Backwards

I was trained to believe the opposite. The meeting is where decisions happen. You present your case. People react. You argue. You vote or the person with authority decides. The meeting is the event.

This structure creates a predictable problem: the meeting becomes a battlefield. People arrive with fixed positions because they haven't had a chance to be heard beforehand. They dig in. They defend. The "decision" is often a win-lose outcome dressed up in consensus language.

Then comes the real cost: implementation. Because half the room didn't actually agree — they just lost — they slow-roll the execution. They find reasons to revisit the decision. Six months into a three-month project, you're re-litigating the original proposal.

I watched this pattern repeat for a decade. I was good at winning arguments in meetings. I was terrible at getting things done afterward.

What nemawashi does is flip this. The meeting is not where the decision happens. The meeting is where the decision is *announced*. All the difficult conversations, the negotiation, the listening, the adjustment — that happens before. In private. In small groups. Where people feel safe to change their minds.

How Nemawashi Works in Practice: Three Real Examples

The Kyoto Tea House (Tradition)

My grandmother runs a small ryokan — a traditional inn — in Higashiyama. About a dozen employees, multi-generational family business. A few years ago, she decided to modernize the booking system. This was a big change. Older staff members were anxious about it.

She didn't announce it in a staff meeting. Instead, over the course of three weeks, she had individual conversations with each person. With the oldest staff member, she listened to his concerns about losing the handwritten guest ledger — the physical record he'd maintained for thirty years. She asked what information mattered most to him. She learned that he valued being able to see the guests' names and preferences written in his own hand.

With the younger staff, she talked about what would make their work easier. She asked questions. She didn't pitch the solution; she listened to the problem.

Then, she invited the oldest staff member to help *design* the system. Not to use it — to help choose it. His role became curator of what information the system needed to track, so it would serve the same function as his ledger.

When the formal staff meeting happened to announce the change, there was no resistance. Not because everyone loved the system, but because everyone had been part of shaping it. The oldest staff member stood and said he was proud of what they'd built together.

That system has been in place for four years now. No re-negotiation. No slow-roll resistance. The investment in nemawashi — maybe ten hours of individual conversations — meant the implementation took two weeks instead of six months.

The London Deal (My Story)

After my grandmother's comment about nemawashi, I decided to go back and redo the communications project — not the proposal, but the groundwork.

I identified the eight executives and met with each of them individually. Not to pitch them. To ask three questions:

• What's your biggest concern about how we currently communicate internally?
• What would success look like for your department?
• What am I missing?

The conversations lasted 20-40 minutes each. Three executives had concerns I hadn't anticipated. Two of them had better ideas than what I'd originally proposed. One person's "concern" was actually a brilliant insight about our audience I'd overlooked.

I spent a week revising the strategy based on what I'd heard. Not compromising it — strengthening it, because I now understood the landscape I was working in.

Then I sent a draft to all eight executives before the meeting. Not for approval — for final comment. I explicitly said: "I've incorporated feedback from our individual conversations. These are the three areas where I'm still uncertain. I'd value your final thoughts before we meet."

The formal meeting lasted 45 minutes. Forty of those minutes were devoted to one genuine open question that hadn't surfaced in the individual conversations. We resolved it together. The other five minutes was formal approval.

Implementation began immediately. By week three, we were ahead of schedule.

The time investment in nemawashi was maybe 15 hours of individual meetings and listening. The time saved in re-negotiation, clarification, and stalled implementation was roughly 40 hours. But more importantly: the final strategy was better because eight brains had shaped it instead of one.

The Corporate Case Study (Research)

In 2019, researchers at Kyoto University's Graduate School of Management conducted a study comparing decision-making speed and implementation success in Japanese vs. American subsidiary offices of the same multinational corporation. The study followed 47 major projects over 18 months.

The findings were stark: Japanese offices took 23% longer in the decision phase but 67% less time in implementation. Overall project timeline was actually 31% *faster* in the Japanese offices, despite the slower decision process.

When researchers interviewed participants, the reason was consistent: the Japanese offices invested heavily in nemawashi. By the time the formal decision meeting happened, resistance had been surfaced and resolved. Execution was smooth.

American offices made faster initial decisions but faced constant re-litigation. People had to be re-convinced during implementation. The "slow" Japanese approach was actually faster end-to-end.

Common Misconceptions About Nemawashi

Misconception 1: It's just consensus-building. Not quite. Consensus-building is the goal, but nemawashi is the *method*. And the method is specific: individual, pre-meeting conversations. Not group brainstorms. Not email surveys. One person, another person, genuine conversation.

Misconception 2: It's slow and bureaucratic. It feels slow because it's invisible. But the total time from initial concept to full implementation is usually faster than the Western meeting-based approach. The slowness is upfront. The speed comes in execution.

Misconception 3: It's a way to avoid conflict. Opposite. It's a way to have conflict in private, where people can change their minds without losing face. The formal meeting is conflict-free because the conflict has already been resolved. In Japanese culture, this is crucial: you never want to force someone to choose between their opinion and their dignity in public.

Misconception 4: Everyone needs to agree completely. No. Nemawashi means everyone has been *heard*. Not everyone will be delighted. But everyone will understand the reasoning and will know their concerns were considered. That's enough for commitment.

How to Practice Nemawashi: Five Concrete Techniques

1. Identify Your Key Stakeholders Early

Before you've even formalized your proposal, know who needs to be heard. Not everyone — that's a mistake. Identify the 5-8 people who have authority, expertise, or will be significantly affected. In my London example, it was the eight executives. In my grandmother's ryokan, it was the twelve employees. For a smaller decision, it might be three people.

Write their names down. Acknowledge them specifically in your nemawashi. Don't treat them anonymously.

2. Schedule Individual Conversations (Not Group Meetings)

This is the core of nemawashi. One person. Another person. Not a group brainstorm. Not a presentation followed by Q&A. A conversation.

The structure I use: 30 minutes, in person if possible (or video call — email doesn't work for this).

• First five minutes: explain why you wanted to talk with them specifically.
• Next 15-20 minutes: ask genuine questions. Listen more than you talk.
• Last five minutes: share your thinking and explicitly ask for their feedback.

The key: you should leave these conversations having learned something you didn't know before. If you don't, you're not listening deeply enough.

3. Take Notes and Feed Back What You Heard

After each conversation, send a brief email: "Here's what I heard from you. Here's how I'm thinking about it. Does this capture your concerns?" This does two things: it shows you were actually listening, and it gives people a chance to clarify if you misunderstood.

This step prevents the most common nemawashi failure: people say yes in a conversation, but their actual concern wasn't addressed — they just weren't clear about it in the moment.

4. Revise Your Thinking Based on What You Learn

This is where many Western professionals get stuck. You've done the nemawashi conversations, but you're attached to your original proposal. So you listen politely, then ignore what you hear.

That's not nemawashi. That's theater.

Real nemawashi means the proposal changes. Sometimes in small ways. Sometimes in large ones. Your job is to take what you've learned and let it reshape your thinking.

In my London example, two of the executives' suggestions actually made it into the final proposal. It wasn't my idea anymore. It was ours.

5. Call the Formal Meeting Only When Consensus Exists

This is the test: if the formal meeting would surprise anyone, you haven't finished nemawashi. Go back and have more conversations.

The formal meeting should feel redundant. Everyone already knows what's coming. The meeting is public acknowledgment, not discovery.

Why This Matters Now (Beyond Business)

I'm sharing this because I think we're living through an era of decision-making failure. We make quick decisions in meetings, feel productive, then spend months re-litigating them. We mistake speed for efficiency. We confuse winning an argument with getting something done.

Nemawashi is not slow. It's a different allocation of time. Time upfront, instead of time in endless meetings down the line.

And there's something else that drew me back to this concept when I was burned out in London: it's based on respect. Real listening. The assumption that other people have valuable insight. That your job isn't to convince them, but to understand them and let them shape what comes next.

In a Kyoto tea ceremony — which I've watched my grandmother prepare hundreds of times — nothing is rushed. But nothing is wasted either. Every movement is deliberate. Every pause is intentional. The tea itself takes three minutes to prepare. The preparation takes a lifetime.

Nemawashi is similar. It looks slow because it's deliberate. But deliberation produces clarity. Clarity produces speed.

When I returned to Kyoto in 2023, one of the first things I did was ask my grandmother to teach me nemawashi formally. Not just listen to it as background wisdom, but understand it as a practice. She smiled and said, "You're ready now. You spent ten years learning what doesn't work. Now we can show you what does."

I think you might be ready too.

— Kenji, The Enso | I write about the things I grew up with but couldn't see until I left them behind. One essay each week, free. If this landed, I'd love you to join. Subscribe to The Enso.

---