Decision-Making in Japan: Nemawashi, Ringi, and the European Pipeline

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.

The working method that travels, the thing actually worth learning, is a two-stage sequence, not a list of meeting etiquette: nemawashi (informal consensus-building before the meeting) followed by ringi (the formal circulating-approval document that records it). Get the sequence right and Japanese decision-making stops looking opaque and starts looking like what it is: a system that front-loads consultation so that execution is fast and unanimous. Get it wrong, treat the meeting as the place a decision is made, and your proposals will keep stalling for reasons no one on your side can quite reconstruct.

This guide takes the sequence from the European seller's and manager's perspective. It covers the consensus logic underneath both stages, the practical nemawashi → ringisho → final approval flow, realistic timing week by week, and the part most intercultural training never reaches: what the consensus model does to a European sales pipeline, and how to forecast a Japan deal without mis-reading the delay.

The decision was not supposed to happen in the meeting. It already happened, in hallways, over coffee, in quiet one-on-one conversations.

How Japanese decisions actually get made

Why Japanese organisations decide by consensus

Before the mechanics, the logic. Japanese consensus decision-making is structural, not a soft cultural preference layered on top of a normal hierarchy. Two well-documented cultural patterns explain why it persists.

The first is collectivism. In Japanese business decision-making and bargaining, consensus from the group is treated as necessary rather than optional, and an individual who disagrees too strongly or insists on a different opinion is seen as disrupting the harmony of group consensus. That is the cultural reason no single manager wants to approve something their colleagues have not seen: visible unilateral action carries a social cost the European equivalent does not.

The second is a long-term, risk-attentive orientation. Japanese leadership tends to see the company as an enduring structure rather than a vehicle for this quarter's result, which favours a slow, thorough approach over a fast one. Uncertainty avoidance, in the cultural sense of how comfortable a society is with ambiguity and unstructured situations, reinforces it: a decision is not considered ready until the ambiguity has been consulted out of it.

There is one frame Europeans get wrong more than any other, and it is worth naming early. Hierarchy and decision style are independent axes. A culture can be strongly hierarchical and still decide by consensus. Japan is the standout example: although strongly hierarchical, it is one of the most consensual societies in the world, deciding bottom-up through the ringi system. A European who assumes "hierarchical" means "the boss decides quickly" will misread the entire pace of a Japanese deal. The boss does decide, but only to ratify a consensus that the organisation built underneath them first.

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 a confirmation, not a debate.

This 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 a sequence, not a single conversation, and the order matters.

1. 1

   Identify every stakeholder

   Not just the decision-maker. Every person whose opinion, cooperation, or sign-off affects whether the proposal moves, including people a European firm would not invite to the same decision.
2. 2

   Start with the least senior

   Build from the bottom up. Junior and mid-level staff are consulted first, for their technical input and so they feel ownership. A proposal handed down from above meets silent resistance.
3. 3

   Present the idea informally

   These are conversations, over lunch or after hours, not presentations. The tone is exploratory, not persuasive. You are asking for input, not selling.
4. 4

   Listen for objections and adjust

   Each stakeholder raises concerns, substantive or political. All are addressed before you move on. The proposal that emerges is often substantially different, and that is the point.
5. 5

   Build toward the senior decision-maker

   By the time you reach the most senior person you can say: everyone has been spoken with, here are the concerns and how we addressed them, everyone is comfortable. They approve without personal risk.
6. 6

   Hold the formal meeting

   The confirmation step. The agenda is known and the outcome expected. The meeting exists to create an official record, not to generate a decision.

The step Europeans find hardest to accept is the second one. Going to the junior people first is the opposite of the European instinct to take a serious proposal straight to the person who can say yes. But in a consensus system the person who can say yes will not, until the people underneath them have. The ringi process that follows is participatory and bottom-up by design, and nemawashi is the informal stage that feeds it.

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. The ringi system circulates that document to every manager affected by the decision, 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 carry every other stamp. The senior leader's approval is the final confirmation of a consensus that already exists. The system is openly criticised, including inside Japan, for how long the consensus process takes, and it can be genuinely difficult to operate across cultures. That criticism is fair, but it misreads the trade-off: the slow front end buys a fast, unresisted back end.

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 ringisho document, briefly

The ringisho is usually one to three pages: a proposal summary in plain Japanese, the rationale (why this, why now, why this supplier), the financial impact, the approval matrix, supporting evidence, and any conditions. The routing list on the first page names every signatory in sequence, with a box for each hanko stamp. The 2020 datsu-hanko policy push has digitised much of the stamping, but the medium changed, not the process: the routing, the upstream nemawashi, and the consensus expectation are unchanged. For the full mechanics of the document, the routing logic, and the document trail a European seller should provide at each stage, see the companion guide to the ringi approval process for European sales teams.

Nemawashi versus European decision-making

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

Example: approving a new vendor partnership. In a typical European company, a manager identifies the opportunity, prepares a proposal, schedules a meeting, presents the case, fields pushback in real time, and either gets a decision in the room or is asked to revise. One to three meetings over two to four weeks, often decided by the most senior person present, sometimes over the objections of others.

In a typical Japanese company the same decision follows a different path. The manager begins nemawashi, meeting every affected department head, finance, legal, and any senior advisors individually. This takes two to six weeks. Concerns are surfaced and addressed one by one. 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.

Where the Dutch and German styles collide hardest

European baselines are not interchangeable, and the size of the collision with consensus decision-making depends on where a team starts. Two patterns recur.

The Dutch baseline collides on pace and directness at once. Flat-hierarchy instinct says go straight to the decision-maker; consensus says do not. Dutch frankness, a genuine strength at home, reads in the room as someone trying to force a position before the group has formed one. The Dutch reflex to "just get a yes today" is precisely the move that makes a yes impossible, because no one can give it without prior consultation.

The German baseline starts closer. German respect for hierarchy, preparation, and precision maps well onto the ringi expectation that decisions are evidenced and detailed, and Japanese decision-makers reward exactly that: they are detail-focused and expect claims backed by case studies and survey results. The German collision is narrower but real, and it is about pace and Klartext. The cultural pride in plain speaking turns a flat "this will not work" into something that lands as aggression in a room built on harmony, and the expectation of a clean in-meeting resolution underestimates the consensus timing.

Why it looks inefficient but is not

The most common complaint from European executives is "everything takes so long." They are measuring the front end, 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 department that was not consulted, no mid-level manager dragging their feet because they were left out. Everyone was brought along during nemawashi.

European decisions often look fast on paper but take longer in total once you count implementation. How often have you seen a decision made on Monday, then spent three months getting everyone actually aligned on what was agreed? The Japanese model pays that cost up front. The question is not "why is this taking so long?" It is "where in the process are you willing to invest the time?"

The meeting paradox

This is where European companies make their biggest mistake.

A European executive flies to Tokyo, schedules a meeting with the counterpart's team, prepares a strong presentation, and walks in ready to negotiate. They have data, arguments, fallback positions. The meeting goes well. The Japanese team is attentive, polite, asks thoughtful questions. But nothing gets decided. The executive leaves confused: "They seemed interested, but we could not pin them down."

Here is what happened. The executive tried to use the meeting as the decision-making venue. In the Japanese system the meeting is where decisions get confirmed, not made. By walking in cold, without nemawashi, the executive created a situation where the Japanese team could not say yes even if they wanted to. No one in that room had been consulted individually. No one had raised concerns in private. No one would put their approval on the line in front of colleagues without prior consultation. The polite attentiveness was genuine, but it was the attentiveness of people gathering information to begin their own internal nemawashi after you leave.

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

Pipeline arithmetic: what consensus does to a European forecast

Everything above is culture. This is the part that costs European companies money, and it is the part most intercultural training never reaches.

Consider a European sales representative carrying a EUR 3 million opportunity with a Japanese enterprise account, paid on monthly attainment. The rep runs a strong first meeting in March. The Japanese team is engaged and asks for detailed materials. The rep, reading European signals, marks the deal 60% and forecasts a Q2 close.

What actually happens: the materials trigger the start of nemawashi, not the end of evaluation. Through April the originator on the Japanese side is having quiet one-on-ones across three departments. The rep, hearing nothing decisive, reads silence as cooling interest, drops the deal to 30%, and stops investing. In May the originator, now needing more detail to finish a conversation with finance, asks for a JPY-denominated breakdown. The rep, by now focused on closeable European deals, responds slowly. The nemawashi stalls on the missing material. The ringisho never starts circulating. By the time the rep re-engages in July, the internal momentum has dissipated and a competitor who fed the originator the right material in Japanese has the inside track.

Nothing in that story is a culture problem in the room. It is a forecasting problem. The rep mis-priced the cycle, mis-read the delay, and mis-timed the investment, all because the forecast was anchored to a European six-week cadence rather than to the nemawashi phase the deal was actually in.

The fix is to forecast against the phase, not the calendar. Map confidence to where the deal sits in the consensus sequence, and treat "no visible movement" during active nemawashi as normal rather than as a warning sign.

Phase the deal is in	What you can observe	Realistic confidence	What the rep should do
Pre-nemawashi (primary contact only)	One or two good meetings; materials requested	Low (10-25%) regardless of meeting warmth	Provide internal-conversation material in Japanese; ask who else should be consulted
Nemawashi underway	Originator consulting other stakeholders; questions arrive in waves; quiet stretches	Low-to-medium (25-45%)	Feed the originator the evidence each conversation needs; stay close, do not push
Nemawashi near-complete	Stakeholder questions stop; a JPY/format-specific proposal is requested	Medium-to-high (50-70%)	Supply a clean, JPY-denominated, JCT-handled proposal the originator can attach
Ringisho circulating	Document is moving; stamps accumulating; occasional clarification requests	High (70-90%)	Be patient, supply clarifications via the originator only, never approach signatories
Final approval / stamped	Routing complete to the required authority level	Very high (90%+)	Move to onboarding; begin post-decision relationship work

Two operational consequences follow for any European sales organisation selling into Japan. First, publish a Japan-specific sales-cycle baseline for forecasting, separate from the European average, so finance does not read a normal nemawashi timeline as country-team underperformance. Second, compensate and coach reps to invest during nemawashi, the phase that looks quiet, rather than pulling back from it. The deal you cannot see moving is often the deal that is actually moving.

Provenance note: the worked example above is a composite illustration of a recurring pattern, not a specific named account. The euro figure and timeline are realistic but illustrative. A field-sourced version with a real (anonymised) EUJC sales-leader account is a first-party gap for Patric to supply.

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 the meeting is Wednesday, arrive 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 changes the dynamic of the formal meeting.

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

Share documents in advance, in the right language. Send your proposal, data, and supporting materials one to two weeks ahead, and where it matters, in Japanese. Japanese teams need time to review internally and begin their own nemawashi. A deck dropped into a meeting with no notice is almost impossible to act on.

Do not push for in-room decisions. Asking "can we agree on this today?" creates an impossible situation. Present your position clearly, ask for questions, and explicitly 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 to address 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, and that trust takes shared meals, repeated visits, and consistent follow-through. There is no shortcut.

For companies that need structured support with this, Japan negotiation training helps teams practise these patterns before they encounter them in a live deal.

When nemawashi goes wrong

Nemawashi is not foolproof. Understanding how it fails helps you avoid the common traps.

• 1

  Skipping a stakeholder

  Miss even one person and you risk a block at the formal stage. The un-consulted person rarely objects openly; they withhold support, and passive resistance is as effective as active opposition.

• 2

  Consulting the wrong people

  Talking to the contacts you know rather than the people who matter. Ask explicitly: who else should I speak with about this?

• 3

  Treating it as lobbying

  Going through the motions of consultation while pushing a predetermined outcome. Experienced Japanese professionals spot it immediately and trust erodes.

• 4

  Rushing the timeline

  Compressing nemawashi into a single trip. Two days is not enough; trying to accelerate it signals you do not value the process or the people in it.

• 5

  Applying European transparency

  Sharing the same information with everyone at once and inviting open debate. Nemawashi conversations are sequential and somewhat confidential; handle them carefully.

• 6

  Escalating over the originator

  Emailing the buyer's senior sponsor to apply pressure. It undermines the originator building consensus underneath, and either response from the senior slows or kills the deal.

What good preparation looks like

Reading a guide is necessary but not sufficient; the sequence only sticks when a team has practised it against its own cultural defaults. The working method we use with European teams has three parts.

1. Baseline first. Identify the team's home-country defaults and where they diverge most from Japan. A Dutch team and a German team need different drills even for the same deal.
2. Sequence rehearsal. Run the stakeholder-mapping, the one-on-one cadence, and the document hand-off as practice, not theory. The first real engagement should not be the first time anyone has done it.
3. Forecast calibration. Reset internal expectations so the team does not treat nemawashi delay as a stalled deal and does not pressure counterparts for premature commitments. This is where sales operations and finance get the Japan-specific baseline.

This is the substance of Silkdrive's cross-cultural communication training for European teams and our broader intercultural training programmes. The decision-making sequence sits inside the wider protocol system covered in our Japanese business etiquette guide for European executives, and the cultural foundations behind it are in our working guide to Japanese business culture. For teams entering the market rather than visiting, see the Japan market entry guide and, for Dutch firms specifically, the Japan-Netherlands business corridor analysis.

Nemawashi is not going away

Some commentators predict younger Japanese companies, especially startups, are moving 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. Group orientation extends to buyer committees and the whole approval process in Japanese B2B purchasing, and that is not a habit that dissolves in a few product cycles.

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 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. A routine operational decision within a single department might take a few days. A significant strategic decision involving multiple departments or external partners can take two weeks to two months, and capital or strategically novel decisions can run three to nine months. The timeline is driven by how many people must be consulted and how complex the issues raised are.

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 in Japanese where it matters, and do not push for decisions in the room. If you are new to working with Japanese partners, cross-cultural communication training helps you practise 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 until the informal consultation catches up. 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 everyone can support. In lobbying you win by convincing; in nemawashi you succeed by adapting. If you go 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 working through consensus decision-making, 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. To talk through a specific deal, book a call.

Related resources

• Ringi: The Japanese Approval Process European Sales Teams Keep Misreading, the formal documentation step that follows nemawashi, with the full ringisho mechanics
• Japanese Business Etiquette for European Executives, the wider protocol system the decision-making sequence sits inside
• The Complete Guide to Japan Market Entry for European Companies, the EU-Japan entry framework that nemawashi sits inside
• The Netherlands-Japan Business Corridor, why this bilateral relationship is the densest EU-Japan corridor in 2026
• The Real Cost of Entering the Japanese Market, budget reality for European companies committing to a Japan engagement
• Japanese Business Culture, full cultural framework: hierarchy, wa, honne-tatemae, and the systems that make nemawashi function
• Hofstede's Cultural Dimensions Applied to Digital Marketing, why Japan's high uncertainty avoidance predicts the nemawashi pattern
• EU-Asia Communication Mistakes That Tank Marketing Campaigns, the communication patterns that intersect with consensus decision-making

About this guide and its sources

This guide is written by Patric Sawada, founder of Silkdrive and an external expert for the EU-Japan Centre for Industrial Cooperation. Married into a Japanese family and based in Amsterdam, he has spent more than a decade in cross-cultural growth work between Europe and East Asia. The cultural claims are anchored to academic and institutional sources rather than travel-guide folklore:

1. Sagi, S. "Ringi System": The Decision Making Process in Japanese Management Systems: An Overview. International Journal of Management and Humanities. On the ringi circulation process, its bottom-up participatory nature, and the criticism of its long consensus cycle.
2. Meyer, E. (2014). The Culture Map: Breaking Through the Invisible Boundaries of Global Business. PublicAffairs. On the independence of hierarchy and decision style, and Japan as the strongly-hierarchical-yet-consensual exception that decides bottom-up through ringi.
3. Kadoi, M. Japanese Negotiation Styles in Business. Ural Federal University. On consensus from the group being treated as necessary in Japanese decision-making and bargaining.
4. JETRO (Gundling, E., Meridian Resources Associates). Communicating with Japanese in Business. On strong disagreement being seen to disrupt the harmony of group consensus.
5. Hofstede, G. (2011). Dimensionalizing Cultures: The Hofstede Model in Context. On uncertainty avoidance as a society's tolerance for ambiguity in unstructured situations.
6. House, R. J. et al. (Project GLOBE). On uncertainty avoidance as reliance on social norms, rituals, and bureaucratic practices to reduce uncertainty.
7. Katz, L. (2008). Negotiating International Business: Japan. On Japan's long-term orientation favouring a slow, thorough approach.
8. Adachi, Y. Business Negotiations between the Americans and the Japanese. Purdue Research Foundation. On Japanese leadership seeing the company as an enduring structure.
9. EU-Japan Centre for Industrial Cooperation. How to Succeed with B2B Marketing in Japan. On group orientation extending to buyer committees and the approval process, and on Japanese decision-makers being detail-focused and expecting evidence-backed claims.