Nemawashi: How Japanese Companies Actually Make Decisions

If you have ever sat in a meeting with a Japanese company and wondered why nothing seemed to get decided, you were watching the wrong part of the process. The decision was not supposed to happen in that room. It already happened — in hallways, over coffee, in a series of quiet one-on-one conversations that took place days or weeks before the meeting was scheduled.

That process has a name: nemawashi.

Understanding nemawashi is not optional if you want to do business with Japanese organisations. It is the single most important concept in Japanese corporate decision-making, and it is the one that European companies misread most often.

What Nemawashi Means

Nemawashi (根回し) is a gardening term. Literally, it means "going around the roots." In horticulture, nemawashi refers to the process of carefully preparing a tree's root system before transplanting it — digging around each root, loosening the soil, making sure the tree can survive the move. You do not just yank it out of the ground. You prepare each root individually.

In business, the metaphor holds. Nemawashi is the practice of meeting individually with every relevant stakeholder before a formal decision is made. You present the idea, explain the reasoning, listen to concerns, adjust the proposal, and move to the next person. By the time the formal meeting happens, every person in the room has already been consulted. The meeting is not a debate. It is a confirmation.

This is not a soft cultural preference. It is how decisions actually get made in most Japanese companies, from small family businesses to the largest corporations. Skipping nemawashi does not just feel rude — it makes your proposal structurally unable to proceed.

How Nemawashi Works in Practice

Nemawashi is not a single conversation. It is a sequence, and the order matters.

Step 1: Identify every stakeholder. Not just the decision-maker — every person whose opinion, cooperation, or sign-off will affect whether the proposal moves forward. In a Japanese company, this often includes people who would not be in the room for the same decision at a European firm. Administrative staff, adjacent department heads, and senior advisors who no longer hold operational authority but whose opinion still carries weight.

Step 2: Start with the least senior people. This is counterintuitive for European executives, who typically go straight to the top. In nemawashi, you build from the bottom up. Junior staff and mid-level managers are consulted first, partly because their technical input shapes the proposal, and partly because they need to feel ownership of the outcome. A proposal that arrives from above without their input will meet silent resistance.

Step 3: Present the idea informally. These are not formal presentations. They are conversations — often over lunch, during a walk, or after hours. The tone is exploratory, not persuasive. You are not selling the idea. You are asking for input and gauging reactions.

Step 4: Listen for objections and adjust. This is where the real work happens. Each stakeholder will have concerns, questions, or conditions. Some are substantive. Some are political. All of them need to be addressed before you move to the next person. The proposal that emerges from nemawashi is often substantially different from the one that went in — and that is the point.

Step 5: Build toward the senior decision-maker. By the time you reach the most senior person, you should be able to say: "I have spoken with everyone on your team. Here is the proposal. Here are the concerns that were raised and how we addressed them. Everyone is comfortable with this version." That senior person can then approve it without taking a personal risk, because the consensus already exists.

Step 6: Hold the formal meeting. This is the confirmation step. The agenda is known. The outcome is expected. Participants may ask clarifying questions, but the direction has been set. The meeting exists to create an official record, not to generate a decision.

Nemawashi vs European Decision-Making

The contrast is sharpest when you watch the same type of decision move through both systems.

Example: approving a new vendor partnership.

In a typical European company, the process might look like this: a manager identifies the opportunity, prepares a proposal, schedules a meeting with the relevant stakeholders, presents the case, fields questions and pushback in real time, and either gets a decision in the room or is asked to revise and come back. The entire cycle might take one to three meetings over two to four weeks. Decisions are often made by the most senior person present, sometimes over the objections of others in the room.

In a typical Japanese company, the same decision follows a different path. The manager identifies the opportunity and begins nemawashi — meeting individually with every affected department head, the finance team, the legal team, and any senior advisors. This takes two to six weeks. Concerns are surfaced and addressed one by one. The proposal is reshaped. When the formal meeting finally happens, it takes 30 minutes and the outcome is unanimous.

Phase	European approach	Japanese approach
Consultation	Happens in the meeting	Happens before the meeting
Decision speed	Fast (days to weeks)	Slow (weeks to months)
Decision maker	Usually one person	Group consensus
Dissent	Expressed openly in the room	Expressed privately beforehand
Post-decision alignment	Often incomplete	Usually strong
Execution speed	Slower (resistance, rework)	Faster (everyone already aligned)

Neither system is inherently better. They optimise for different things. The European model optimises for speed of decision. The Japanese model optimises for quality of execution.

Why It Looks Inefficient but Is Not

The most common complaint from European executives working with Japanese partners is: "Everything takes so long." They are measuring the front end of the process — the time from proposal to decision — and finding it slow by European standards.

What they miss is the back end. Once a Japanese company decides, execution is fast. There is no internal resistance to manage, no departments that were not consulted, no mid-level managers dragging their feet because they were not involved. Everyone was already brought along during nemawashi.

European decisions often look fast on paper but take longer in total when you count the implementation phase. How often have you seen a decision made in a meeting on Monday, only to spend three months getting everyone actually aligned on what was agreed?

Research on Japanese management practices bears this out. A study by Katsuhiro Umemoto published in the European Journal of Information Systems found that Japanese companies consistently spend more time on the pre-decision phase and less time on the implementation phase compared to Western companies. The total elapsed time from idea to completed implementation is often comparable — or shorter.

The question is not "why is this taking so long?" The question is "where in the process are you willing to invest the time?" Nemawashi front-loads that investment.

How Nemawashi Connects to Ringi

Nemawashi does not exist in isolation. It pairs with ringi (稟議), the formal document-based approval process that creates the institutional record of a decision.

Think of them as two halves of one system:

Nemawashi is the informal phase. It happens in conversations, over meals, in the hallway. It is where opinions are shaped, objections are surfaced, and consensus is built. Nothing is written down during nemawashi — it is entirely verbal and relational.

Ringi is the formal phase. Once nemawashi is complete, the proposal is written up as a ringisho (稟議書) — a formal request document. This document circulates through the organisation, and each stakeholder stamps it with their hanko (personal seal) to indicate approval. The ringisho moves from junior to senior, collecting stamps as it goes.

By the time the ringisho reaches the most senior decision-maker, it should already have every other stamp on it. The senior leader's approval is the final confirmation of a consensus that already exists.

For European companies, the practical takeaway is this: if you are asked to submit a formal proposal to a Japanese partner, do not treat that as the starting point of the decision process. The starting point was nemawashi. If you have not done the informal groundwork, your beautifully formatted proposal will sit in a queue — not because it is bad, but because no one has been prepared for it.

The Meeting Paradox

This is where European companies make their biggest mistake.

A European executive flies to Tokyo, schedules a meeting with the Japanese counterpart's team, prepares a strong presentation, and walks in ready to negotiate the terms of a deal. They have data, they have arguments, they have fallback positions.

The meeting goes well. The Japanese team is attentive, polite, asks thoughtful questions. But nothing gets decided. The European executive leaves confused and slightly frustrated: "They seemed interested, but we could not pin them down on anything."

Here is what happened: the European executive tried to use the meeting as the decision-making venue. In the Japanese system, the meeting is not where decisions get made. It is where decisions get confirmed. By walking in cold — without having done nemawashi with the individual stakeholders — the European executive created a situation where the Japanese team could not possibly say yes, even if they wanted to.

No one in that room had been consulted individually. No one had had the chance to raise concerns in private. No one was prepared to put their approval on the line in front of their colleagues without prior consultation. The polite attentiveness was genuine — but it was the attentiveness of people who are gathering information to begin their own internal nemawashi process after you leave.

"We will study this carefully" is not a brush-off. It means: "We need to do nemawashi now."

How European Companies Can Participate in Nemawashi

You do not need to be Japanese to do nemawashi. You need to be willing to invest time in relationships before pushing for outcomes.

Arrive early. If you have a meeting scheduled for Wednesday, arrive on Monday. Use the extra days to meet individually with as many stakeholders as you can. Even a 20-minute coffee with a mid-level manager can change the dynamic of the formal meeting.

Request one-on-one introductions. Ask your primary contact to introduce you to the other team members individually before the group meeting. Frame it as wanting to understand each person's perspective and concerns. Most Japanese professionals will appreciate this — it signals that you understand how things work.

Share documents in advance. Send your proposal, data, and supporting materials at least one to two weeks before the meeting. Japanese teams need time to review materials internally and begin their own nemawashi. A presentation dropped into a meeting with no advance notice is almost impossible to act on.

Do not push for in-room decisions. If you ask "Can we agree on this today?" in a formal meeting, you are creating an uncomfortable situation. The answer will almost always be "We need to discuss this internally" — which is polite for "You skipped the process." Instead, present your position clearly, ask for questions, and explicitly say that you welcome further discussion after the meeting.

Learn to read the signals. "This is very interesting" means they are listening but have not formed a position. "We will consider this carefully" means nemawashi has not happened yet. "We have some concerns" means there are specific objections that need to be addressed individually. "This will be difficult" is often the closest thing to a "no" you will hear directly.

Invest in the relationship layer. Nemawashi works because of trust. The informal conversations only function when people feel comfortable being honest. That trust takes time to build — shared meals, repeated visits, consistent follow-through. There is no shortcut.

For companies that need structured support with this, cross-cultural negotiation training can help teams practice these patterns before they encounter them in real business situations.

When Nemawashi Goes Wrong

Nemawashi is not foolproof. It can fail, and understanding how it fails helps you avoid the most common traps.

Skipping stakeholders. If you miss even one person in the nemawashi process, you risk a block at the formal stage. The person who was not consulted may not object openly, but they will withhold their support — and in a consensus-based system, passive resistance is just as effective as active opposition. This is especially dangerous when dealing with Japanese organisations where informal influence structures do not map neatly to the org chart.

Doing nemawashi with the wrong people. Consulting the people you know rather than the people who matter is a common mistake. Your main contact may not be the person with the most influence over the decision. Ask explicitly: "Who else should I speak with about this?"

Treating nemawashi as lobbying. Nemawashi is not about persuading people to agree with you. It is about genuinely incorporating their input. If people sense that you are going through the motions of consultation while pushing a predetermined outcome, the process breaks down. The difference between nemawashi and lobbying is whether you are actually willing to change your proposal based on what you hear.

Rushing the timeline. European companies often try to compress nemawashi into a single trip. "We will meet everyone on Tuesday and have the formal meeting on Thursday." Two days is not enough. Nemawashi takes the time it takes. Trying to accelerate it signals that you do not value the process — or the people in it.

Applying European transparency norms. In a European context, you might share the same information with everyone simultaneously and let them debate openly. In nemawashi, conversations are sequential and somewhat confidential. What one person tells you in their one-on-one is not necessarily meant to be repeated to the next person verbatim. Navigate this carefully.

Nemawashi Is Not Going Away

Some commentators predict that younger Japanese companies, especially startups, are moving away from nemawashi toward faster, more Western-style decision-making. There is some truth to this in the tech sector. But for the vast majority of Japanese companies — and certainly for any large or traditional organisation — nemawashi remains the operating system.

If you are doing business with Japan, you have two choices: work with nemawashi, or work against it. Working against it means faster meetings, slower results, and a lot of confusion about why your excellent proposals keep stalling. Working with it means slower meetings, faster execution, and relationships that compound over time.

The investment is front-loaded. The returns are back-loaded. That is the deal.

---

Frequently Asked Questions

What does nemawashi mean in English?

Nemawashi (根回し) literally translates to "going around the roots," from the Japanese gardening practice of preparing a tree's root system before transplanting. In a business context, it refers to the process of informally consulting each stakeholder individually before a formal decision is made — preparing the ground so the decision can take root without resistance.

How long does the nemawashi process take?

It depends on the decision's scope and the number of stakeholders involved. For a routine operational decision within a single department, nemawashi might take a few days. For a significant strategic decision involving multiple departments or external partners, it can take several weeks to two months. The timeline is driven by the number of people who need to be consulted and the complexity of the issues raised.

Can European companies do nemawashi?

Yes, and the best ones already do. You do not need to be Japanese to consult stakeholders individually before a formal meeting. The key adjustments are: arrive early, request individual introductions, share materials in advance, and do not push for decisions in the room. If you are new to working with Japanese partners, cross-cultural training can help you practice these dynamics before encountering them in a live deal.

What happens if you skip nemawashi?

Your proposal stalls. In a consensus-based system, a proposal that has not been through nemawashi cannot proceed because no individual stakeholder is willing to approve something their colleagues have not been consulted on. You will hear polite responses — "We will study this," "This needs further discussion" — but nothing moves forward until the informal consultation process catches up. In practice, skipping nemawashi adds time rather than saving it.

How is nemawashi different from lobbying?

The critical difference is intent. Lobbying aims to persuade people toward a predetermined position. Nemawashi aims to surface concerns, incorporate feedback, and shape a proposal that everyone can support. In lobbying, you win by convincing. In nemawashi, you succeed by adapting. If you approach nemawashi as a lobbying exercise — going through the motions of consultation while pushing your original plan unchanged — experienced Japanese professionals will recognise it immediately, and trust erodes.

---

Work With Us

If your organisation is preparing for a Japanese partnership, market entry, or cross-border collaboration and you want practical guidance on navigating decision-making processes like nemawashi, we can help.

Browse our Japan expert network to find specialists with direct experience in the Japan-Europe business corridor, or explore our training programmes for team-level preparation.

For a deeper look at the cultural dynamics behind Japanese business relationships, see our guide on Japanese business culture.