The Meeting Is in English. The Decision May Not Be

You ran the meeting in English, it went well, and everyone was polite and engaged. Then the deal moved slower than the room suggested it would, or a decision came back that did not match the tone of the conversation you remember. One useful explanation is that the English-language meeting may have been only one layer of a larger decision process. For a Japanese buyer whose internal working language is primarily Japanese, a good deal of the detailed technical and internal discussion can continue in Japanese, before the meeting and after it, in a register you never hear. This article is about that gap: why the meeting you attended may not represent the whole decision, why fluency in the room is not the same as influence over the outcome, what an interpreter can and cannot fix, and what a foreign supplier can do about it.

Two things to hold on to before we start. This is a tendency in some Japanese organisations, not a law that applies to all of them; companies that operate in English, global teams, trading houses, and firms with internationally experienced leadership fit this pattern far less. And the mechanism here is language load and meeting structure, not national character. Nothing in this piece rests on the tired idea of “Japanese indirectness,” and nothing here treats a discussion continuing in Japanese as concealment. It is not hidden from you. It is simply outside your view because it happens in a language you do not share.

This is a structural gap, not bad faith

It is easiest to read the pattern correctly if we start here, because the wrong reading leads to the wrong response. The buyer is not hiding the real conversation from you, and the most fluent English speaker in the room is not managing you. Both sides are doing something entirely reasonable: holding the courtesy meeting in the foreign side’s language, and doing the detailed technical and internal work in the language where it is fastest and most precise for them. Reading that as evasion, and responding with suspicion or pressure, mistakes a structural feature of cross-language business for a character flaw in your counterpart. It is neither their failing nor yours. It is the shape of a deal that runs across two languages and an internal process that predates your involvement.

The meeting may be one layer, not the whole

Working in a second language is real cognitive work. Research on second-language processing links it to demands on working memory and other cognitive resources, and studies of bilingual business meetings, such as Du-Babcock’s comparisons of decision-making meetings conducted in a first versus a second language, find that how people take turns, manage topics, and exchange information can shift with the language being used. A meeting conducted in English for the benefit of the foreign side is, for much of the Japanese side, a second-language exchange, and what you experience as “the meeting” may be one layer of the buyer’s process rather than the whole of it.

How much of the discussion English can carry

It helps to be specific about where language load bites. General discussion, logistics and relationship-building travel fine in workable English. The strain shows on the technical detail that decides an industrial purchase: tolerances, test conditions, failure modes, material grades and certification. That vocabulary and the reasoning around it need advanced, specialist English, not conversational fluency, and the person who commands it in your product area may not be the person representing the buyer in English. A study of organisational English ability in Japanese corporations, reported by the Information Processing Society of Japan, illustrates the spread: a large share of respondents rated their organisation’s ability to conduct discussions in English at the level of “simple discussion” (around a third) or only “prepared questions” (around a third), with a smaller share (under a fifth) rating it equal to or better than their native language. Treat that as one study rather than a current census, but it makes the core point: being able to work in English is not the same as being able to conduct high-stakes technical argument in it at native depth.

Where the detailed discussion can continue

For buyers whose working language is Japanese, the substantive technical and internal discussion can continue in Japanese, before or after the meeting. In some organisations the formal meeting confirms alignment that has already been built through prior internal discussion, rather than being the place where the matter is settled. That is not a universal rule: some companies decide in the meeting, some align before it, some confirm in it, and some circulate an internal proposal afterward, and it can differ by department within one firm. The practical point is narrower and safer: a point made only in the English portion of the exchange may never get made, or answered, in the Japanese-language discussion where a Japanese-speaking buyer works through the detail. That is our characterisation of the pattern, not a measured finding, but it is a consistent one.

The objection you did not hear

Consider a supplier of a precision component presenting to a Japanese manufacturer. The call runs in English, led on the buyer’s side by a personable sales-engineering contact whose English is excellent. The supplier explains the product, fields a few questions, and leaves confident. Afterward, the buyer’s quality manager, who barely spoke during the call, raises a specific concern in Japanese: the component’s performance at the edge of the stated tolerance band, under the buyer’s actual test conditions, was not clearly evidenced. That point can become the objection that stalls the internal proposal. Nobody was being evasive. The concern simply belonged to a person and a language that the English meeting did not reach, and the supplier never got the chance to answer it because they never knew it was raised. Weeks later a narrow technical question arrives, seemingly from nowhere. Read correctly, it is the visible edge of a discussion that happened in Japanese, and it deserves your fullest, fastest answer, ideally in writing and in Japanese.

Fluent is not the same as decisive

There is a second, quieter point. The person who speaks the most English in a mixed meeting is not reliably the person who matters most to the decision, and treating fluency as a proxy for authority can point your attention at the wrong seat.

Business-level English, deep technical command of a narrow product category, and decision authority are three different things, and they do not often live in one person. The most fluent English speaker may be a sales or business-development colleague whose job includes handling foreign counterparts. The person who understands your product at the level that will shape the purchase, the engineer or the quality manager, may say very little in English and then discuss the substance at length in Japanese once the call ends, and may not be the decisive technical stakeholder either. If you calibrate the whole meeting to the fluent speaker, you can spend an hour persuading someone with limited influence over the technical verdict while the people who will weigh it stay quiet. Making sure your technical case reaches those people in a form they can use matters more than winning the English exchange.

Reading who carries weight in the room

You can often pick up useful cues without a word of Japanese, by watching the room rather than the conversation. Note who the fluent speaker glances at or defers to before answering a technical question, who takes detailed notes while others do not, and whose title on the exchanged business cards sits in quality, engineering or procurement rather than sales. When a hard question lands, watch where the discussion turns. These cues can help you identify who is likely to carry technical or decision-making influence, though they are hints, not proof. Once you have a sense of it, make sure that person receives your full technical case in written Japanese, because they are the one most likely to be carrying it into the internal discussion later. You are not trying to bypass your main contact; you are trying to equip the colleague they will have to convince.

What an interpreter does, and what it cannot fix

For anything technically load-bearing, an interpreter is worth using, and it helps to be precise about what interpretation solves and what it does not.

Brief the interpreter properly

For technically complex meetings, using a professional interpreter and briefing them properly can materially reduce the risk of terminology and context errors. The value is in the preparation. Guidance from the Japan Association of Conference Interpreters (JACI) stresses that interpreters should receive the meeting materials in advance, confirm the speakers and their roles, understand the purpose of the meeting, research the specialist vocabulary, build a glossary, and be briefed beforehand. An interpreter who knows that “tolerance” in your sentence means a numeric engineering band, not a general allowance, protects the one clause that carries the deal. The cost of that preparation is small against the cost of a load-bearing technical point being rendered vaguely at the moment it needed to be exact.

Where the shortcuts fall short

The common shortcut, leaning on a colleague “who speaks English” or “who speaks Japanese,” tends to work for greetings, logistics and general discussion and then lose precision on the technical specifics, where a single misused term changes the meaning. Machine translation can be genuinely useful for routine communication, but technically sensitive material should still be reviewed by someone who understands both the language and the subject matter, because that is exactly where an automated rendering can be confidently imprecise on the clause that carries the weight.

The channel widens; the decision still moves in Japanese

Here is the limit worth internalising. Professional interpretation can improve the quality of the live exchange, but it cannot replace the buyer’s internal decision-making process. An interpreter widens the channel during your meeting; it does not move the decision into your meeting. If the buyer’s substantive discussion continues in Japanese, before and after the call, then a perfect interpretation of the call still leaves you outside the conversation that carries the most weight. Interpretation solves a communication problem. It does not solve the internal approval process. The lever that changes the outcome is getting your technical case into that Japanese-language discussion, not only improving the quality of the on-meeting exchange.

The language layers of a Japanese decision

It helps to picture the whole path your proposal travels, because the English meeting is only the first visible step. A useful way to see it is as a series of layers. The first is the external meeting, the English-language exchange between you and the buyer. The second is the internal discussion on the buyer’s side, where technical, quality, procurement and management colleagues work through the detail, often in Japanese. The third is internal documentation, the Japanese-language meeting notes, evaluation material and, for a formal purchase, the internal approval proposal. The fourth is the decision itself, the approval or sign-off.

Set out that way, the connection to the rest of the Japanese buyer’s process is clear. The internal discussion and documentation are where consensus is built and where the internal proposal, the ringisho, gets written, which we cover in what happens after your Japanese inquiry goes quiet. If your technical argument only exists in spoken English from one meeting, you are leaving your counterpart to reconstruct it in Japanese as it moves through those layers, from memory and from whatever you left behind. Every point that lived only in the English conversation is a point at risk of being softened or lost on the way into the documents that decide the purchase.

What a supplier can actually do

You cannot attend the Japanese-language discussion, and you cannot force the decision into your meeting. What you can do is make sure the detail that matters is present, in Japanese, at the point where the internal discussion takes place.

Put the important technical detail into Japanese

For the technical information that matters most, prepare material that your counterpart can reference in Japanese and lift into their internal discussion: the specifications that matter, the evidence behind your claims, and clear answers to the questions you can predict. For a technical manufacturer that can mean Japanese-ready versions of your technical specifications, test results, certifications, quality standards, installation requirements, warranty and maintenance terms, and relevant case studies. You do not need to translate everything; you need the two or three things the decisive people need, in the form that costs them the least to use. A short document already in Japanese, structured around the buyer’s likely questions, removes a translation step and lowers the effort your counterpart spends advocating for you. This connects directly to the evidence a Japanese buyer expects on paper, which we cover in what Japanese buyers want in your technical documentation.

Own the record after the meeting

Do not let the only record of the meeting be your side’s English memory of it. Send concise minutes, ideally with a Japanese version, that state what was agreed, what remains open, and what you will provide next. Name a single follow-up owner on your side who responds quickly and completely, because when your counterpart needs one specific answer to move the internal discussion, a slow or partial reply can cost a full cycle. And when the substance is load-bearing, use a briefed professional interpreter rather than an ad-hoc bilingual colleague, so the precision survives the language boundary.

None of this closes the gap entirely. Part of the discussion will still happen in a language and a setting you are not part of. But it changes what reaches that discussion. Instead of a summary and a memory, your counterpart is working from your actual technical case, in their language, ready to be used in the documents that decide the deal.

The English meeting is not fake

One point the headline can obscure deserves the final word. The English meeting is not fake or unimportant, and the fluent speaker is not a decoy. The meeting is a real and necessary part of the relationship. It is simply one layer of a larger communication and decision process, and the risk for a foreign supplier is not that Japanese is being spoken behind a curtain. The risk is that the content of the English conversation may not travel cleanly to the Japanese-speaking colleagues who weigh it. The problem to solve is not your inability to speak Japanese. It is making sure your case reaches the people who will decide, in the form and language they will actually use.

Key takeaways

• The English meeting may be one layer, not the whole. For a buyer whose working language is Japanese, detailed technical and internal discussion can continue in Japanese before and after the call. This is a tendency in some organisations, not a rule for all.
• It is structure, not bad faith. The discussion continuing in Japanese is outside your view because of language, not because anything is being hidden. The mechanism is language load and meeting structure, not national character.
• Fluency is not authority. The best English speaker in the room may not be the decisive technical stakeholder, who may say little in English and weigh the detail later in Japanese.
• Being able to work in English is not the same as arguing in it at depth. One study of organisational English ability in Japanese corporations found most respondents rated their firm at “simple discussion” or “prepared questions” level, not native-equivalent.
• An interpreter widens the channel but does not move the decision into your meeting. Brief a professional interpreter with materials and a glossary; have technically sensitive machine-translated material checked by someone who knows both the language and the subject.
• Put the detail into Japanese, and own the record. Japanese-ready technical material, a Japanese meeting record, and one fast follow-up owner get your case into the internal discussion you cannot attend.

What to read next

• Nemawashi: what happens after your Japanese inquiry goes quiet
• The ringi system: how Japanese companies approve your deal
• What Japanese buyers want in your technical documentation
• Japan market entry consulting for technical manufacturers