The team's working language: fluency is not the same as a sound idea
A shared language does not guarantee equal ease of participation. Prepare materials, pace and ways to confirm meaning in everyday cooperation between Poland and Asia.
Article language: English

In this article
Imagine a meeting where the most persuasive idea comes from the person who speaks most fluently. They are concise, joke at the right moments and answer objections quickly. Someone else is still forming a sentence when the conversation moves on. After the meeting, they send a comment that changes how the solution is assessed. They did not lack knowledge of the task. They lacked room to contribute it in the language being used.
A shared working language makes collaboration easier, but its name alone does not establish the conditions for participation. Materials, pace, opportunities to ask questions and ways to confirm meaning matter too. This applies even when everyone on the team knows English. Speaking comfortably in conversation and explaining a technical exception precisely are not necessarily the same skill.
An agreed language does not describe the whole conversation
Rakuten's official company history identifies July 2012 as the point when English became its official corporate language after a two-year transition. This describes a particular company decision. It does not show that everyone could then participate with equal ease or that the same approach suits every company.
In cooperation between Poland and Asia, the language of meetings, documents, brief exchanges and approval of important decisions can be agreed separately. They do not always have to be the same. If the choice is to make work easier, participants need to know where the authoritative material is and how they can clarify an uncertain meaning.
Imagine a team preparing an offer for audiences in Poland and Korea. People work in different places and hold daily meetings in English. One person knows how the local customer channel works but takes longer to explain a complex point. Another presents the project exceptionally well but knows less about that particular channel. These are fictional roles; we are not assigning these characteristics to nationalities.
Decide what the meeting needs from its participants. Are they receiving an update, commenting on material or making a decision? Information can be prepared in advance. A decision needs a way to bring concerns into view. If all these activities are compressed into a short live presentation, language fluency may have too much influence on whose contribution is noticed.
Fluent speech is no substitute for the basis of an argument
Tsedal Neeley's study of language and status in an organisation examined one French technology company using English as a common language through qualitative research. The author describes experiences of status loss among people for whom English was not a first language. This is a finding in a particular context, not a basis for diagnosing every group of employees.
In preparing our example offer, consider how people can present what they know. Assess an argument by its basis, relevance to the task and whether it can be checked. Hesitation or a slow response does not settle its quality. Equally, a polished presentation does not prove that someone knows how a particular channel works or what its audience needs.
A useful question is: which case illustrates the difference? The person who knows the contact channel could show an example of a customer question, a screen or an actual sequence of events. The team can then compare evidence instead of judging a confident tone. A service map connecting customer contact with the work behind it (in Polish) helps place that observation in a specific part of the collaboration.
Do not turn a person's lower ease in a language into a permanent label. The same person may discuss a familiar subject fluently and need more time for a new concept. Look at the task, material and form of participation. Judging professional competence by the speed of a single response would be a step too far.
Distinguish the need for a linguistic explanation from the need for data. Someone may understand a question but not yet have evidence for an answer. They may also know the fact but need to check the right term in another language. In both cases, record what is missing. A general instruction to "improve your English" describes neither the task nor the next useful form of support.
For a complex exception, you might ask for a short written explanation or drawing. This should not become a penalty for speaking less fluently. The same format can help everyone see the scope. Choose the medium to improve understanding, rather than demand one presentation style regardless of the kind of knowledge involved.
Materials sent before a meeting give people time to prepare their contribution
Send the problem description, options and a specific question before the meeting. In our example, the team could receive an excerpt from the offer and a proposed way to contact the Korean market. Participants can find an example, check a term and write down a point. They do not have to learn the problem, translate it for themselves and respond live all at once.
Make clear what needs to be read. A large folder without guidance does not offer the same conditions as a short document with a question. If the decision concerns a name or a service approach, include the relevant excerpt. The rest can remain an attachment for later work. The team should know which material forms the shared basis for discussion.
For a progress update, a useful status update without another meeting (in Polish) can help. A written record lets people read at their own pace and return to the meaning. It does not replace every conversation, but it can free meeting time for questions that need genuine joint discussion. The meeting then need not begin with an account some participants could have read beforehand.
Check timing as well. Material sent five minutes before a meeting does not give comparable preparation time to someone who is just starting their day in another time zone. Poland and Asia cooperation across time zones (in Polish) should reflect real availability, not merely an empty slot in the organiser's calendar.
A shared document can allow comments before the discussion. The facilitator then sees a question before the options are discussed. If it concerns a fact, someone can prepare the evidence. If it concerns interpretation, the team can choose an example to clarify together. The important thing is not to leave comments somewhere no one will look again.

When some participants speak in their own language between meeting items, preserve shared access to any outcome relevant to everyone else. Not every side conversation needs a word-for-word translation. But if an agreement has been made or the basis for assessment has changed, others need to understand its meaning before the next decision.
The pace should leave room to check meaning
During the discussion, address one condition at a time. Point to the document and passage when referring to material. A joke, an abbreviation or a long sentence with three exceptions may sound good but make agreement harder. When the meaning affects execution, take time to clarify it. If some people are in the room and others remote, also check conditions for participation in a hybrid meeting (in Polish) so distance does not add another obstacle to the language challenge.
Ask about a concrete example rather than requesting only general confirmation. "Is everything clear?" is easily answered with a nod. "What does the customer receive after the first contact in this option?" lets the team compare interpretations. It need not be a test of one person. Different roles can describe the step relevant to them.
If interpreting is needed, agree its scope in line with preparing an interpreter for a business meeting (in Polish). Keep language work and substantive decisions distinct. The interpreter helps preserve the meaning of what is said, but should not supply conditions the team has not yet agreed.
Record recurring differences in a company glossary (in Polish). A term needs an example and a boundary. Choosing one English word will not, on its own, make everyone understand the scope of "support" or "approval" in the same way. Such apparently familiar terms can produce two different plans after one meeting.
When a tool translates working notes, pay particular attention to names, conditions and the degree of certainty. "Possible after confirmation" must not become simply "possible" in the final note. The recipient needs that qualification because the next action may depend on it. Even a fluent translation needs an appropriate check of the important meaning.
This does not mean correcting every minor language mistake during the substantive discussion. If the meaning is clear, constant correction can pull the conversation away from the task. When an error changes a parameter or condition, clarify it. The team should distinguish these cases so precision does not turn into an unnecessary speaking exam.
A local observation needs a route to the decision
In our example, someone points out that a customer using KakaoTalk needs a different transition from the website to the conversation. Instead of deciding on personal certainty, the team can examine the specific contact path through KakaoTalk Channel (in Polish). It needs evidence about use and handling, not a broad statement about how "people speak in Korea".
If a local participant cannot change an important part of the offer, they should know how to take an argument to the right person. The division of discretion between headquarters and a local market (in Polish) matters in practice here. Being able to speak does little if the point has no onward route and no one responds to its basis.
Aeneia Oriens helps organisations understand the context of cooperation between Poland and Korea, Japan and China, and prepare language and materials for a specific conversation. The starting point may be part of an offer, a local channel or a term participants understand differently. The work concerns meaning and the realities of collaboration, rather than judging people by fluency.
Aeneia Oriens
Organise the material and the meaning of terms for a specific conversation between Poland and Asia. Start where local knowledge or a condition of the offer gets lost between languages. Prepare a shared basis for the conversation
Assess the support on one agreement from a recent conversation. Do participants describe the offer's scope in the same way? Can they identify an unknown and the person who will check it? If the difference remains, see whether it comes from language, missing material or a decision that has not actually been agreed. Not every disagreement calls for the same kind of language work.
When confirming an agreement, distinguish having no comments on the wording from agreeing to carry it out. Someone may say they understand the text but still need to check whether it can be delivered. In our example, a clear description of the contact route does not confirm that a team is available to respond. The note should preserve what the participant actually assessed and what remains open.
For important names, also show the original spelling when they refer to a specific product or channel. This makes it easier to identify the subject together without guessing from pronunciation or a working translation. A second language is not needed in every sentence. Keep it where it helps identification and checking meaning.
Agree how an important point can be added later
After the meeting, leave a clear route to correct meaning or report missing information. Not every decision needs to be reopened indefinitely. People do need to know when the record will be confirmed and what to do if they notice a significant misunderstanding. The deadline should account for participants' actual availability.
If an important point comes after the meeting, connect it to a specific entry. Does it correct a fact, clarify meaning or propose a new choice? Each needs a different next step. This keeps the route for additions from becoming either an unanswered mailbox or an endless reopening of everything already agreed.
At the next meeting, try one change: earlier materials, a slower discussion of conditions or a shared example. Ask participants whether they could contribute the information needed and can identify the next step. Do not judge the trial solely by the number of comments. A useful point can be brief and need no impressive presentation. The team benefits from hearing it before the subject becomes an elegantly worded mistake.







