Integrating with a Japanese Organisation: A Guide for the European Half

You know your deal better than we do. The rationale, the structure, the case that was made for it and the integration plan are all yours, and none of them are what this is about.

This is about the twenty or thirty people who now have to work with counterparts in another country, and about one specific thing that goes wrong between them: the European side keeps aiming at the wrong level, at the wrong moment, in the wrong forum, and reads the resulting silence as resistance.

The reader here is the European half of a shared structure, sitting mostly in Europe, newly reporting into or jointly running something with a Japanese organisation.

One scope note before anything else, because it governs everything that follows. The consensus machinery described here is a large-organisation practice. In Japanese small and medium enterprises the person who speaks in the meeting is often the person who decides. If your counterpart is a company of eighty people, most of this applies weakly or not at all, and the first thing to establish is which of the two you are dealing with.

Authority is not where the chart puts it

The instinct on the European side is to find the counterpart with the matching title and work through them. That instinct is close to useless.

The layer worth influencing sits below the top of each headquarters function, because that is the level at which the decision process actually starts. In the case this comes from, the European company simply did not know who those people were, which meant every attempt to move a decision was aimed above the point where it would have been formed.

The claim here concerns sequence rather than power. By the time a proposal reaches the top of a function, the substantive work has been done somewhere below it, and an intervention at that level arrives after the moment when it could have changed anything.

The practical response is unglamorous and takes weeks. Map that layer. Find out who prepares the material, who is consulted before it circulates, and who has been asked for an opinion. Then invest there.

A meeting is for confirming, not deciding

Business meetings in Japan are more about decision confirmation than decision making.

That sentence explains most of the frustration on both sides, and the frustration genuinely does run both ways. European managers leave meetings complaining nothing was decided. Japanese managers working in Europe complain about European meetings too, for the opposite reason: too much gets decided in the room, without the preparation that would have made the decision sound.

There is a striking piece of evidence about what "preparation" means. When more than a hundred Japanese managers working in Europe were asked how to improve meeting efficiency, eighty-five per cent gave more or less the same three words: jizen-junbi, jizen-tsuchi, jizen-rikai. Preparation beforehand, notification beforehand, understanding beforehand. Not a better agenda, not tighter chairing, not shorter meetings. Everything they named happens before anyone sits down.

That is a practitioner survey rather than a controlled study, and it should be read as such. But eighty-five per cent converging on the same answer is a strong signal about where the work is thought to belong.

For an integration team the implication is concrete. If your steering committee is the place where things get resolved, you have built the governance around the European assumption, and your Japanese counterparts will experience every session as a series of decisions taken without proper groundwork.

Consensus is not agreement

The formal instrument is the ringi, a document that circulates for approval. The informal phase that precedes it is the one that matters. The ringi is less about finding a decision than about confirming it.

What the seal on that document means is more precise than most European readings of it. Sealing the ringisho is closer to a declaration that the individual acknowledges their opinion was sufficiently heard, and that even where they do not fully agree, they will give the decision their full support.

Hold both halves of that. Counting seals as enthusiastic endorsements will mislead you about how much support a plan really has. Treating every sealed document as a room full of private objectors misleads you just as badly in the other direction. What the seal records is a commitment to back an outcome you were properly consulted on, and no clean European equivalent exists, which is why it keeps getting mistranslated both ways.

Slow to commit, then changed by a different route

The other side of a long decision process is one that European teams consistently under-plan for, and the research does not agree on what happens after a decision is taken.

A study of Dutch and Japanese managers, from fieldwork around 1999 and 2000, found that once the Japanese side had decided there was no turning back; one Dutch respondent called it the no-escape aspect of Japanese consensus. The EU-Japan Centre's 2019 report on Japanese-European acquisitions, by Martin Glisby and Nigel J. Holden, records the opposite about individual decisions. A Japanese top executive in one of its case companies described up to twelve rounds before a final decision and added that "decisions can always change after input from lower levels". Another stakeholder put it as "Everything (i.e. agreements, contracts, decisions) can change, but a partnership cannot".

Read together, the two findings describe where change happens rather than whether it does. A decision is hard to reopen at the meeting where a European team expects to reopen it, because it was not made there. It can move later, through the same consultation below the top of each function that produced it. European project governance assumes revisability at the next gate; on the Japanese side, revision travels by a different route.

The related habit is front-loading. Projects are vetted for risk in detail, with preparation and feasibility work completed before a decision is taken, and execution then runs to the plan. A European team that expects to iterate its way to a specification will be asking for changes at exactly the point where change is most expensive socially.

The trust finding that reverses the cliché

The standard story is that Japan is a collectivist high-trust society. The research says something more interesting.

Laboratory and survey work finds that Americans are more likely than Japanese to trust strangers, which runs against what the collectivism framing predicts. A second paper records the same finding and describes it as running dramatically counter to conventional wisdom.

Both of those are secondary sources reporting earlier surveys, and the underlying studies were not available to read, so this is offered with attribution rather than with a number attached. It is not a claim that Japanese people are untrusting.

The resolution is the useful part. The degree of trust a firm extends depends on the nature of its relationship with the party in question and the context of the transaction, rather than on a national disposition. Trust is built inside one specific relationship.

For an integration that has a direct consequence. Your merger agreement transferred assets, contracts and reporting lines. It transferred no trust whatsoever. That has to be constructed relationship by relationship, and the people who have to construct it are the ones in your project team, not the ones who signed.

One belief to drop: that a Japanese counterpart will tell you how things really are once there has been a drink. The research identifies it as a misleading assumption. A dinner is a different context, worth planning in its own right, and in the Glisby and Holden report a Japanese manager describes two to three days of lodging together, dinner and drinking producing "a different kind of dialogue and depth". It is not a shortcut around the formal channel.

They think you are the hierarchical one

One finding is worth carrying into every integration workshop, because it punctures the assumption underneath most of them.

When Dutch and Japanese managers were asked, large majorities on both sides believed hierarchy played a bigger role in the other group's consensus process, and that the other side's process was therefore more vertical than their own.

That measures perception rather than actual hierarchy, and it comes from the same period as the study above. What it tells you is that your Japanese counterparts are not sitting there thinking of themselves as the formal ones. They are looking at your reporting lines, your escalation habits and your sign-off requirements, and reaching the same conclusion about you that you have reached about them.

An integration that treats cultural adaptation as something the Japanese side needs to do is missing half the problem, and the half it is missing is visible to everyone on the other side of the table.

Why this is worth staffing

One number, offered with its provenance rather than as a market statistic.

In the Glisby and Holden report for the EU-Japan Centre, only eleven per cent of Japanese companies said their post-acquisition process had been successful, and cross-cultural difference was the most frequently cited cause of failure.

Read it carefully. It is a self-report about success, so it cannot be turned round into a failure rate, and the report cites no underlying survey for it. What it establishes is narrower and still useful: when acquirers themselves are asked what went wrong, culture is the cause they name most often. They are not describing a soft problem they encountered on the way to a hard one.

The limits of what is known here

Two limits apply to everything above.

No published source sets Japan's power-distance score beside a European country's, so the pattern is described here without a figure. Scores get quoted freely in this field, often without their source or their year.

The second is that the evidence base for cross-border integration with Japanese firms specifically is thin. What exists is largely practitioner reporting, and the material above leans on a small number of sources rather than on a settled literature. The decision-making research is much stronger than the integration research. Anyone who presents you with a confident, quantified model of Japanese post-merger integration is working from a literature that does not exist.

Where this sits

The pattern most integration teams need is not more reading. It is someone working through your actual structure, your actual counterparts and your actual milestone plan, which is what our cross-cultural training for Japan does.

For the layer underneath this piece, on hierarchy, nemawashi and how decisions form, our guide to Japanese business culture is the place to start. If the integration involves building a shared team rather than only a shared governance structure, cross-cultural communication training for HR buyers covers what that costs and what it does. And because a newly merged organisation is exactly where national generalisations get applied to individuals, the difference between a tendency and a truth is worth reading before the first workshop.