Nemawashi & Ringi: How Decisions Really Get Made in Japanese Companies

If you have ever presented to a Japanese company, watched everyone nod politely, and then heard nothing for two months, you did not lose the deal in that room. You lost it — or won it — in a dozen conversations you were never invited to. And there are ways to read which direction those conversations are going.

In Japanese organizations, the visible approval meeting is the last step, not the first. The real decision is built beforehand, informally and privately, through a process called nemawashi, and then ratified formally through a paper trail called ringi. Understand these two mechanics and most of the “slow,” “opaque,” and “consensus-obsessed” behavior that frustrates overseas teams stops looking irrational and starts looking like a process you can support.

One caveat before the mechanics: how strictly this plays out varies by company. Large, traditional enterprises run the process formally and slowly; younger firms and startups often run a lighter, faster version. Calibrate what follows to your specific prospect.

What “nemawashi” actually means

Nemawashi (根回し) is the informal, one-on-one groundwork of privately consulting every affected stakeholder to build agreement before a decision is formally proposed.

Literally, nemawashi means “going around the roots.” It comes from gardening: before you transplant a tree, you dig carefully around its roots and prepare them so it survives the move. In business, it means preparing the ground for a decision by talking to every affected stakeholder one at a time, privately, before anything is proposed formally.

The point of nemawashi is that no one should be surprised — or lose face — in the actual meeting. Objections are surfaced and resolved quietly, in advance. By the time a proposal is formally tabled, everyone who matters has already been consulted and has already signaled agreement. As GLOBIS Europe describes it, the groundwork is laid “informally through personal discussions” long before any formal decision appears.

For an outsider, this is the single most counterintuitive part of Japanese business. The meeting is not where you persuade people. If you are still trying to persuade people in the meeting, the nemawashi failed.

What nemawashi looks like in practice

• A manager floats an idea one-on-one over coffee, not in a group setting.
• Concerns from each department are collected and quietly folded into the proposal.
• The proposal is revised — sometimes several times — before anyone commits to it in writing.
• Only once broad informal agreement exists does the idea become a formal document.

Example. Say a Japanese manufacturer is weighing an overseas SaaS platform. The internal sponsor does not call a decision meeting. She raises it privately with IT (“can this integrate?”), then security (“what happens to our data?”), then finance (“how does a recurring cost fit the budget?”), adjusting the framing after each. Only when all three are quietly on board does she write it up as a ringisho and start the formal approval flow. From the vendor’s side none of this is visible — you see a good meeting, then weeks of quiet, then either a request for more materials or a signed contract.

Nemawashi and the Toyota Way: “decide slowly, execute fast”

Many Western readers first meet the word through lean and the Toyota Production System. In The Toyota Way, Jeffrey Liker describes a principle of making decisions slowly and by consensus, considering all options, then implementing rapidly. Nemawashi is the consensus mechanism behind the first half: the slow groundwork is what allows fast, friction-free execution afterward. If you arrived from a lean or Agile context, this is the same idea seen from the org-culture side rather than the shop floor.

What “ringi” is, and how it differs from nemawashi

If nemawashi is the informal groundwork, ringi (稟議) is the formal ratification. Ringi is the structured, bottom-up approval process by which a proposal is documented and circulated for sign-off.

The document at the center of it is the ringisho (稟議書): a written proposal typically stating a title, summary, background and purpose, and supporting data. It starts lower in the hierarchy and moves upward, department by department, each relevant party reviewing and marking their approval before it advances. Importantly, the ringisho is an internal document written in Japanese by the internal team — a point that matters a great deal for overseas vendors, as we will see.

The two systems are complementary, not alternatives. Nemawashi builds the consensus; ringi records it. By the time a ringisho begins circulating, the outcome is usually already settled — the paperwork confirms a decision the informal process has effectively already made.

The ringisho and the hanko: the mechanics of sign-off

The ringisho is not just a form. It is the audit trail of a shared decision, and the way it is marked matters.

Traditionally, each reviewer approves the document with a hanko (also called inkan) — a personal seal used in place of a signature. By tradition, the seal’s orientation is even said to carry meaning: the Wikipedia entry on Japanese management culture notes some reviewers place it “right side up” to agree, “upside down” to disagree, and sideways for undecided — more workplace folklore than universal rule today. Increasingly the step is digital anyway, but the logic is the same: every affected party leaves a visible, individual mark of where they stand.

This is why the number of stakeholders matters so much to timing. A ringisho that must pass through five departments needs five sets of eyes and five approvals — and if any one was not properly prepared during nemawashi, the document can stall there indefinitely, with no single person “saying no.”

Why it takes so long — and why that is not a bug

Western teams routinely read this pace as indecision or lack of interest. It is usually neither.

The consensus model deliberately front-loads deliberation. Because every affected party is consulted before the decision is finalized, risks and objections surface early rather than after commitment. Multiple write-ups of the ringi process — including Inventure Japan’s overview — describe the formal ringisho circulation taking anywhere from days to roughly a month, because the process values thoroughness and shared ownership over speed.

A crucial distinction for anyone stuck in silence: that “days to a month” figure is the ringi circulation — the paperwork phase, which only starts after consensus already exists. The nemawashi phase before it has no fixed clock. For a multi-department enterprise deal it can run from a few weeks to several months, stretching with every added stakeholder. So if you are two months past a good meeting with no ringisho in sight, you are almost certainly still in nemawashi — which is normal, not a verdict.

The trade-off is real and cuts both ways:

• Slower to decide. Consensus takes time, and for a vendor that is genuinely costly — longer sales cycles and a pipeline you struggle to forecast into.
• Faster and more durable to execute. Once the decision is made, everyone has already bought in — little of the post-decision second-guessing that plagues top-down mandates.
• Diffuse accountability. Because the decision is collective, there is rarely a single “owner” you can lean on to accelerate it.

Western top-down vs Japanese consensus: a side-by-side

For teams used to a single decision-maker, the contrast is stark. Neither model is superior — but treating a consensus organization like a top-down one is the fastest way to stall.

What this means if you are selling into Japan

If you are an overseas company selling to a Japanese enterprise, the practical implication is uncomfortable but clarifying: you are almost never the one who closes the deal. Your internal champion does — inside their own organization, using nemawashi and ringi you will never see.

That reframes your entire job:

• Find and arm the champion, don’t pressure the buyer. Your champion is the person asking internal-logistics questions (“how would we roll this out?”), introducing you to colleagues, and requesting materials they personally do not need — because they need them to sell you internally. Give that person clean, documentation-grade materials they can attach to a ringisho.
• Read silence correctly. A long quiet stretch after a good meeting often means nemawashi is underway, not rejection. Pushing hard for a “close” during this phase can actively damage the internal case your champion is building.
• Reduce perceived risk, not just present features. Because the process is built to surface risk, the proposals that move are the ones that are easy to defend. Anticipate the concerns of finance, legal, and operations — not just the enthusiasm of your immediate contact.
• Respect the pace without going silent yourself. Stay useful and responsive; provide what is asked promptly. But do not manufacture false urgency — it reads as pressure and rarely works.

How to tell a live nemawashi from a polite no

Silence “often” means nemawashi — but you should not have to guess. The direction of the deal usually leaks through observable signals. Watch which list your prospect is on:

Signs it is alive:

• New stakeholders or departments appear, often unprompted (a security lead, a finance contact you had not met).
• Your champion asks for internal-facing or “defensive” materials — security-review documents, total-cost-of-ownership breakdowns, references, competitor comparisons.
• The questions shift from “why you?” to “how would we actually deploy and run this?”

Signs it is concerning:

• Total non-response, with no new names ever entering the thread.
• The only questions left are about price and discounts.
• No one asks for anything they would use internally — a sign no one is doing groundwork on your behalf.

The most useful diagnostic is the last one. If no one inside is quietly doing the groundwork for you, the deal is probably not in nemawashi at all — and that absence is itself your answer.

What a “ringi-ready” document actually looks like

The advice to hand your champion documentation-grade materials is easy to nod at and hard to execute, because a Western pitch deck is the wrong shape for the job. A deck excites one enthusiast; a ringisho attachment has to survive being defended department by department, in a room you are not in. The difference in practice:

And here is the blind spot that stops many overseas teams: the ringisho itself is internal and written in Japanese. A polished English one-pager cannot simply be dropped into it. Your champion needs Japanese-language, culturally framed materials — not just your deck — to socialize the proposal at all. Underestimating this is one of the quietest deal-killers there is.

We go deeper on the buyer psychology behind this in How Japanese B2B Buyers Make Decisions (that piece covers evaluation and trust; this one, the nemawashi/ringi mechanics), and on the broader entry in our Japan Market Entry guide.

A note for SaaS and subscription models

Subscription and SaaS deals feel the friction of ringi acutely, because a recurring commitment triggers more internal scrutiny than a one-off purchase — procurement, security, and finance all want their seal on it. If that is your model, the internal-approval burden is worth planning for explicitly; we cover it in Selling SaaS in Japan.

You do not need to master Japanese business vocabulary. You do need to recognize that the culture behind terms like hanko rewards preparation, patience, and giving your counterpart the tools to build agreement internally.

The LOads perspective

In our work with overseas teams, the most common and most expensive mistake we see is treating the Japanese buyer like a Western decision-maker — pushing for a fast close, targeting a single “economic buyer,” and reading post-meeting silence as a loss. A pattern we have seen more than once: a vendor gets a strong first meeting, hits weeks of silence, concludes the deal is dead, and starts to disengage — right at the moment the champion inside is quietly walking the proposal from department to department. When we help that vendor stop pushing and instead supply the Japanese-language, risk-framed materials the champion can attach to a ringisho, the “dead” deal frequently turns out to have been progressing the whole time.

The teams that succeed tend to do the opposite of their instincts. They slow down exactly when those instincts scream to accelerate, and they invest in making their champion look good internally rather than in “closing” anyone. Qualitatively, that shift — from persuading a person to equipping a process — is the single biggest predictor we see of whether an overseas company gets traction in Japan.

Where LOads fits

This is precisely the gap LOads exists to close: helping overseas teams navigate the consensus timeline and build the Japanese-language, documentation-grade materials a champion needs to move a proposal through nemawashi and into a ringisho. LOads is a bilingual Japan marketing partner, founded in 2018 in Fukuoka, and we have supported more than 100 companies entering or growing in the Japanese market. Our CEO, Kosuke Tsunawaki, has over 14 years of experience in digital marketing.

Our model keeps you in control: a fixed monthly fee, with your ad budget paid from your own accounts, so you retain full ownership of your data and platforms. Before any engagement, we offer a free consultation with a read on your specific Japan opportunity and one strategy call, so you can gauge the fit before committing.

If you are also evaluating how to run acquisition on the ground, our guides on B2B Marketing in Japan and choosing a digital marketing agency in Japan are useful next reads.

For the official procedural side of establishing and operating a business in Japan, JETRO’s Invest Japan portal is the authoritative government reference.

Frequently asked questions

What is nemawashi in simple terms?

Nemawashi is the informal groundwork done before a decision is formally proposed. It means talking to each affected stakeholder privately, one at a time, to surface concerns and build agreement in advance. By the time the idea reaches a formal meeting, everyone has already been consulted and no one is surprised.

How is nemawashi different from the ringi system?

Nemawashi is the informal, behind-the-scenes consensus-building; ringi is the formal, documented approval process that follows it. Nemawashi happens in conversations; ringi happens on paper, through a circulating document called a ringisho. The two work together — nemawashi builds the agreement, and ringi records and authorizes it.

What is a ringisho?

A ringisho is the written proposal at the heart of the ringi process. It typically states the proposal, its background and purpose, and supporting data, then circulates through the organization from lower levels upward. Each relevant party reviews it and marks their approval before it advances. It is an internal document, written in Japanese.

What is a hanko and why does it matter for decisions?

A hanko (also called inkan) is a personal or corporate seal used in place of a signature to authorize documents in Japan, including the ringisho. On an approval document, the seal is a visible, individual record that a specific person has signed off. Even as digital workflows spread, the seal remains a recognizable symbol of formal approval.

How does nemawashi relate to Toyota and lean?

In The Toyota Way, Jeffrey Liker describes a principle of deciding slowly and by consensus, then executing rapidly. Nemawashi is the consensus-building mechanism behind the “decide slowly” half — the groundwork that makes fast implementation possible afterward. Readers from a lean or Agile background usually first meet the term here.

How long is normal to wait after a meeting with a Japanese company?

Longer than most overseas teams expect. The informal nemawashi phase — before any ringisho begins circulating — can run from a few weeks to several months for a multi-department enterprise deal, and it lengthens with each additional stakeholder. That is separate from the ringi circulation itself, which typically takes days to about a month once consensus already exists. Two months of quiet after a good meeting is often normal, not a rejection.

If a Japanese client goes silent after a meeting, have I lost the deal?

Not necessarily — and often not. A long quiet period after a positive meeting frequently means nemawashi is underway internally. Look for signals: if new stakeholders keep appearing and your champion asks for internal-facing materials, the deal is likely alive; if there is total silence with no new names and only price questions, be concerned. Pushing hard for a close during nemawashi can undermine the champion building your case.

Do these customs still apply now that business is going digital?

Yes. Digital tools have changed the medium — hanko seals become electronic approvals, and ringisho circulate through software — but the underlying logic of consensus-building and shared ownership remains firmly in place. The pace and the emphasis on preparing stakeholders in advance persist regardless of the tooling.