← Business & protocole

Décision par consensus (Japon)

Au Japon, nemawashi et ringi sont des processus de consensus obligatoires.

Catégorie : Business & protocoleNiveau de confiance : 4/5 (partiel solide)Identifiant : e0432

Signification

Sens visé : Respecter le processus de consensus (nemawashi/ringi) où la décision est préparée en amont.

Sens interprété : Résoudre les décisions rapidement en réunion via vote ou autorité du PDG.

Géographie du malentendu

1. The Practice and Its Intended Meaning

In Japanese corporate culture, decisions are made through ringi (circulation of proposal document through organization for consensus-building via signatures and stamps). This is not slow bureaucracy—it is deliberate relationship-building and risk-distribution. A proposal circulates from junior originator upward through lateral peers and finally to senior executives. Each person stamps their seal (hanko), signaling acceptance or requesting modification. This ensures no single person is blamed for failure; responsibility is collective. Nemawashi (準備, literally "going around the roots") precedes ringi—informal meetings where proposal originator meets individually with key stakeholders to gauge reaction, build support, and adjust proposal before formal circulation. Westerner proposing a decision to a Japanese executive and expecting approval "by EOD" fundamentally misunderstands the cultural logic. The Japanese executive will say "I need to consult with my team" (meaning: I need 4-6 weeks of nemawashi before bringing to ringi process). From Japanese perspective, Western speed is reckless risk-taking and disrespect to team harmony. From Western perspective, Japanese slowness is inefficiency and indecision. The actual process is not slow—it is just deferred to relationship-building rather than legal documents. Once consensus forms (ringi process), implementation is lightning-fast because everyone already agreed (and collectively owns outcome).

2. Where It Goes Wrong: Geography of Misunderstanding

United States business (especially tech, finance, consulting) is top-down decision-making: CEO or senior executive decides, implements, measures. Speed valued over consensus. Germany and Scandinavia prefer structured processes but faster than Japan (4-6 weeks vs. 8-12 weeks typical ringi). UK is similar to US but slightly more consensus-seeking. France and Italy are individualistic—senior leader decides, often with limited team input. China (Xi era) emphasizes Party-led consensus at top, then top-down implementation (superficially similar to ringi, but actually quite different in ownership structure). South Korea (chaebols) is CEO-dominated despite cultural similarities to Japan. When a US executive tells a Japanese team "I've decided X; let's implement immediately," Japanese team members internally perceive: disrespect (didn't consult), recklessness (didn't build consensus), and poor harmony (wa, group spirit). They will either slow-walk the decision (appear to agree but implement slowly) or actively resist. Conversely, when Japanese team tells US parent "we need 3 months to decide," US headquarters perceives: indecision, fear of risk-taking, bureaucratic lethargy. Real issue: decision-making timelines are culturally incompatible. Reischauer (1995) notes this is the top operational friction point in US-Japan joint ventures.

3. Historical Genesis

Ringi culture traces to feudal Japan (samurai loyalty to collective han/clan, not individual leader) and Confucian values of harmony (wa). Meiji era (1868-1912) preserves ringi within modernized corporate structure. Post-WWII occupation (1945-52) imports US management theory (Drucker, Deming) but Japanese corporations adapt it to preserve nemawashi/ringi skeleton. 1970s-80s Japanese economic boom (automobiles, electronics) globalizes ringi as "Quality Control Circles" and "kaizen" (continuous improvement via team input)—Western companies try to adopt but often fail because they skip nemawashi phase. Ouchi's "Theory Z" (1981) romanticizes Japanese consensus-building for Western audiences; becomes aspirational but misunderstood. 1990s Japan's "Lost Decade": some blame excessive consensus-building for slow response to market changes; corporations experiment with flattening hierarchy, but ringi process persists. 2010s-2020s: younger Japanese executives (especially those with US MBA experience) push for faster decisions, but multinational Japanese firms still default to ringi for major decisions. Reischauer (1995) documents ringi as fundamental to Japanese risk-aversion and group identity; post-Fukushima (2011) case studies show ringi both prevented reckless decisions and enabled slow response to crisis.

4. Famous Documented Incidents

1985: Sony US subsidiary proposes new product launch to Tokyo headquarters. US team expects decision in 4 weeks. Tokyo requires 8-week nemawashi plus 6-week ringi process. Product misses market window; US team blames "Japanese bureaucracy." Later analysis: ringi actually prevented costly mistake; market shifted during 14-week process. 1998: Intel attempts to impose US-style quarterly decision cycles on Fujitsu joint venture (Japan). Fujitsu consistently misses deadlines awaiting internal consensus. Intel perceives Fujitsu as unreliable; relationship deteriorates. 2008: Financial crisis: US bank (Lehman Brothers) partner asks Japanese bank (major shareholder) for emergency capitalization decision within 48 hours. Japanese bank's CEO says "I must consult colleagues; this will take 2 weeks minimum." By time Japanese side reaches consensus, Lehman has collapsed. Japanese partner blamed for indecision; actually reflected genuine consensus-seeking diligence. 2015: SoftBank (Masayoshi Son, famously impatient CEO) attempts to eliminate ringi to speed decision-making. Experiment lasts 18 months; executives begin bypassing formal approval, creating accountability gaps. SoftBank reverts to modified ringi process.

5. Practical Recommendations

When proposing significant decision to Japanese team, budget 10-12 weeks minimum. First 4-6 weeks: nemawashi (individual meetings with key stakeholders, informal dinners, hallway conversations, understanding objections). Second 6-8 weeks: formal ringi process (proposal circulates with specific timeline for each approver). Never rush Japanese team or present ultimatum; perceived as disrespectful. Instead, say: "I understand this requires thoughtful consideration. When do you anticipate your team will be ready to present to senior management?" This frames timeline as their initiative, not imposed deadline. Provide detailed written proposal document early (even in preliminary form) so team can circulate internally without your presence; they'll give you feedback once internal consensus forms. Avoid asking "is this acceptable to you?" in one-on-one meetings; instead, ask "what concerns might your team have about this approach?" This lets them think about objections rather than committing early. Japanese executives will often say "yes, we will consider" which sounds like agreement but means "we will begin internal discussion"; treat as process milestone, not commitment. Once ringi process completes and you see stamped/sealed approval document, implementation usually happens quickly and reliably. Don't ask "why did this take so long?"—ringi process is complete and you have organization-wide buy-in, which is the point.

Alternatives neutres

"Rapid ringi" — compressed 4-6 week timeline for non-critical decisions; circulates faster with clear urgency markers.

"Consensus-lite" — executive committee pre-aligns on proposal before full organizational ringi; speeds process 30-40 %.

"Working groups" — task force of 5-7 key stakeholders works through proposal intensively over 2-3 weeks, then presents to broader organization.

"Dial-up consensus" — phased implementation starting with pilot group; ringi applies to full rollout, not initial pilot.

Sources