Why your Japanese counterparts ask so many detailed questions

Then the questions begin

Head office sends an instruction to the Japan organisation. Clear scope, clear deadline, nothing controversial.

Then the questions begin.

Not one email with twenty questions — that you could handle in an afternoon. Instead: one question on Tuesday. Two more on Friday, from a name you do not recognise. The following week, a request to confirm something you thought was already settled. Then a question so granular you have to look up the answer yourself.

Weeks pass. The instruction has not moved — as far as you can tell — and the questions keep coming.

At some point, a thought forms that you would not say out loud: can they not decide anything themselves? Do they not trust us?

If you sit on the other side of the relationship — selling to a Japanese company rather than working inside one — you will recognise the same film from a different seat. You submitted the proposal, the meeting went well, and then the trickle began.

Four interpretations, all understandable, usually wrong

They are incompetent. They do not trust us. They are stalling. It is bureaucracy for its own sake.

Each of these reads the questions as a verdict — on you, or on them. But in many Japanese organisations, the questions are not a verdict at all. They are the sound of a process running.

Align first, commit later

Many Japanese organisations do more internal alignment before commitment than their European counterparts expect. Sometimes this takes the formal shape of ringi — a process in which a proposal document travels through the organisation, collecting approval from the functions it affects. Sometimes it happens informally, through consultation with the people who would carry the consequences, before anyone is willing to commit. Ringi is one formal expression of a broader pattern: align first, commit later.

What is being aligned depends on which side of the relationship you sit. An external proposal is examined for approval: legal, finance, procurement and other functions each review it from their own angle. An instruction from head office is examined for implementation: local compliance, operational risk, affected stakeholders, who will carry responsibility — and, quite often, what an ambiguous instruction actually means in practice.

Either way, here is the part that explains your inbox: the questions land on the person carrying the matter internally — very likely your counterpart — and as it reaches different reviewers, different questions emerge, because each function is looking at a different set of risks.

This is one reason questions tend to arrive sequentially rather than as one complete list. Nobody can batch questions that have not been asked yet. The sequence is the process.

Underneath it sit two structural differences I return to often in this series: how widely consultation is distributed before commitment, and how organisations weigh speed now against risk downstream. The questions are where those differences become visible in your inbox.

What the questions actually tell you

Once you see the mechanism, the questions change meaning.

A slow trickle of detailed questions — especially when new names begin appearing in the thread — often means your proposal is moving. It is being examined, translated, and rebuilt into something the organisation can approve. In many cases, the person asking is not even the person who wants to know: your counterpart is relaying questions from reviewers you will never meet, and assembling a case they can defend internally.

Read this way, your counterpart is not an obstacle. They are the person carrying your proposal through the building.

The familiar head-office complaint — “why can't our country manager just decide?” — often lands on the very person who is spending their week walking your instruction past legal, finance and operations.

Silence is not proof that the proposal is dead — but unlike active questions, it gives you little evidence that it is moving. Questions are evidence; their absence is simply the absence of evidence.

What you can actually do

Answer quickly, and completely. Your answer is what restarts the internal machine. Every day your reply sits in your outbox is a day your proposal sits parked at one approval gate. If your organisation's habit is to let non-urgent emails wait a week — a habit that works perfectly well in many European settings — this is the moment to make an exception.

Answer for the reader you will never meet. Assume your reply will be forwarded, translated, or pasted into an internal document. Make it self-contained: full context, precise figures, no irony, no “as discussed”. Where you can, attach something your counterpart can circulate as-is. You are not writing an email; you are writing evidence for a review you will not attend.

Help your counterpart carry it. A simple question — “Would it help if I prepared a short document for your internal review?” — signals that you understand what they are doing on your behalf. It tends to be remembered.

What looks like a bug is the process doing its work

The volume of questions is not a judgement of your competence, and it is not proof of theirs. It is the visible surface of a structural choice: some organisations decide quickly and align during execution; others align first and decide later. This is also why, once commitment lands, execution in Japanese organisations can move faster than outsiders expect — much of the alignment that might happen during execution elsewhere has already happened before commitment.

That does not make the process painless. It is slower than most global timelines assume, and it demands patience at exactly the stage where head-office processes expect speed. And not every question is progress — the honest test stays behavioural.

But irritation misreads it. What looks like a bug from the outside is, more often, the process doing its work.

The questions are not noise. They are the process — and once you learn to answer the process, rather than react to the volume, it starts working for you.

Don't count the questions. Read the process behind them.

Keep reading

Why “we will consider it” rarely means what you think — the companion pattern, at the moment the meeting ends. Or go deeper into the approval terrain with the free field guide Getting a Yes from Tokyo.