English meetings for Tokyo global teams: joining the conversation

01

Find out how your team actually communicates

An international company address does not tell you how a particular meeting will run. A Tokyo team may discuss a project in English, use Japanese for some preparation, or circulate bilingual summaries. Ask the organizer which language the meeting uses, whether materials arrive in advance and how decisions are recorded. This is more practical than assuming that all global teams follow the same pattern.

Two published company examples illustrate the variation. Rakuten's corporate culture page describes its Englishnization program and English as the official internal language. Mercari's language page describes an approach in which speakers adjust to help each other understand Japanese and English. These are company descriptions, not claims that either arrangement applies to your employer.

Write a personal meeting brief: who attends, what decision is needed, what you know that others need, and what you need from them. If you only prepare a polished status update, you may still struggle when the discussion turns to a decision. Separate the facts you will report from the question you want answered.

02

Prepare a contribution with an entry point

Choose one short opening that makes the purpose of your turn clear. 'I have an update on the customer feedback' signals information. 'Could we clarify the approval step?' signals a question. 'I see one risk with that date' signals a concern. Practise the sentence together with the actual point, so the opening does not become an empty formula.

Use a three-part contribution: point, reason, request. In an invented project example: 'I suggest moving the review to Thursday. Two people need the draft before they can comment. Could we confirm who will send it?' The example is deliberately ordinary. Useful participation often consists of making a dependency visible rather than delivering a long presentation.

If you cannot find a gap, use the meeting's agreed hand-raising or chat process. Ask the organizer about that process before an important call. Do not assume that speaking faster or interrupting more often proves confidence. A meeting practice session should include turn-taking, not just uninterrupted speeches.

03

Give updates that help another person act

Structure a short update around current state, change and next step. Begin with what the listener needs now, then explain the relevant background. In a practice exercise, replace 'There are various issues and we are discussing them' with 'The draft is complete, but legal review is pending. We need the review result before we confirm the release date.' The second version gives the group something to resolve.

Practise saying dates with the month in words and naming the relevant time zone when colleagues work outside Japan. A phrase such as tomorrow morning can mean different working periods to different participants. Use the actual calendar invitation to confirm the meeting time rather than relying on a memorized time difference, especially where daylight-saving changes apply.

Create a one-minute recording and ask a partner to write down the current state and the next action. If they cannot identify both, revise the organization before polishing individual sounds. Keep abbreviations that the whole group knows; explain a team-specific abbreviation the first time it appears.

04

Make clarification and disagreement specific

A request to repeat everything can be necessary, but it may not solve a particular ambiguity. Practise identifying the missing element: the owner, the date, the definition or the reason. 'Could you repeat the deadline?' is easier to answer than a general expression of confusion. If the question concerns meaning, offer your interpretation and invite correction.

To disagree, state the part you understand and then the evidence or condition behind your concern. In a fictional scheduling discussion: 'I understand why Friday is useful for sales. My concern is that the test results will arrive on Friday afternoon. Could we make the date conditional on those results?' This keeps the discussion on the decision rather than another person's language or motives.

If the group changes language and you lose access to the discussion, ask for a short summary of the decision and rationale. Equally, when you are the stronger speaker, reduce unnecessary idioms and pause after an important point. Mercari's published approach offers a concrete local example of shared responsibility for understanding; it should not be read as a universal requirement at other companies.

05

Match a Tokyo course to your meeting problem

The British Council Japan business English page lists Business Speaking and Business English Professional, with the course currently offered at Iidabashi. At the September 2026 check, Business Speaking is described as a B1–C1 group with a three-hour weekly class. This may suit a learner who wants group interaction, subject to placement, schedule and available places.

A course's location matters alongside its curriculum. Test the journey from your actual office or home, including the return trip after a full working day. Iidabashi and your company's Tokyo office may be on very different routes. If regular attendance is unlikely, compare live online options and ask whether the teacher can rehearse your specific meeting tasks using fictional materials.

Bring your one-minute update to a consultation and explain the actual problem: losing the turn, answering unexpected questions, or writing a decision summary. Ask how the course will practise that problem and how feedback is recorded. A general business label does not show whether you will practise the skill you need.

Flalingo is the publisher of this guide and provides English-learning services. The options discussed here are examples to investigate, not an independent ranking. Verify the current total price, class size, cancellation terms and exact format with each provider before deciding.

06

Try a small decision meeting with conflicting information

Use three fictional roles: a project owner, a customer-support lead and a designer. The group must decide whether to publish a new help page this week. The owner knows the target date, support has three unresolved questions, and the designer knows that one diagram is still a draft. Give each person only their own information so that questions are necessary.

Set an eight-minute limit. During the first two minutes, each person gives a short update. During the next four, ask questions and compare options. Use the final two minutes to confirm the decision, any unresolved condition and the next owner. There is no single correct business answer; the language task is to make the information and decision explicit.

Afterward, ask each participant to write a two-sentence summary without consulting the others. Compare the summaries. If one person thinks publication is approved and another thinks it is conditional, repeat the final part of the meeting. This reveals a consequential misunderstanding that a simple fluency score might miss.

Change one detail on the second attempt: the deadline moves, an approval is missing or a colleague cannot attend. Keep the language accessible while making the interaction less predictable. Avoid uploading actual customer data or internal plans when using an external teacher or tool.

07

Build a four-week participation routine

Week one is a baseline. Choose one recurring meeting and note where participation becomes difficult. Practise a short update outside the meeting, then aim to make one relevant contribution during the real discussion when appropriate. Record what happened in a private learning note; recording the meeting itself requires the team's permission and policies.

In week two, concentrate on clarification. Prepare two specific questions and use them when the information is genuinely unclear. In week three, practise comparing options and giving a reason. In week four, work on closing the loop: summarize a decision and confirm an action with the person responsible. These are practice targets, not a requirement to speak merely to meet a quota.

Review whether your contribution helped the group understand or decide something. Track one example of a clearer update, one useful question and one accurate summary. If the same problem remains, take that example back to a teacher or colleague and repeat the task with a simpler structure. Progress can be visible in fewer misunderstandings even before speaking feels effortless.