How to Run Daily Standups with a Multilingual Team

Daily standups are a cornerstone of agile teamwork, meant to be a quick sync to align the team and clear roadblocks. But when your team is distributed across countries and speaks different native languages, this simple 15-minute meeting can become a source of confusion and anxiety. The goal is to create a predictable, inclusive routine that fosters clarity, not just to go through the motions.

This guide offers a structured approach to running daily standups that work for multilingual teams. We will cover preparation, facilitation techniques, and follow-up actions that ensure everyone is heard and understood, regardless of their native language.

Before the Standup: Set the Stage for Clarity

Consistency is the foundation of a successful multilingual meeting. When team members know exactly what to expect, they can prepare their thoughts and feel more confident contributing. A few simple setup steps can make a significant difference.

Establish a Clear, Consistent Agenda

The classic standup format of answering three questions is a good starting point:

1. What did I accomplish yesterday?
2. What will I work on today?
3. What is blocking my progress?

Post this agenda in your team's shared channel and in the calendar invitation for the meeting. Sticking to the same structure every day reduces cognitive load. Team members can prepare their updates using this framework, which is especially helpful when formulating thoughts in a non-native language.

Define a Common Language and Stick to It

For most international teams, English serves as the lingua franca. It is important to formally establish this as the language for the standup. This isn't about excluding other languages but about creating a single, predictable channel for communication during this specific meeting.

When you establish this, also acknowledge that fluency levels will vary. Reassure the team that perfect grammar is not the goal; clear communication is. Create a psychologically safe environment where it is okay to speak slowly, ask for clarification, or correct a misunderstanding.

Share Key Vocabulary and Acronyms

Every project has its own jargon, acronyms, and technical terms. A new feature named "Project Hydra" or an acronym like "QMS" might be obvious to some but opaque to others.

Create a simple, shared glossary in a tool like Confluence, Notion, or even a pinned document in your team channel. For each term, provide a simple definition in the team's common language. This document becomes a valuable resource that helps level the playing field for all team members, especially those who are new to the project or the company.

During the Standup: Facilitate Understanding

As the facilitator, your role is to guide the conversation and ensure information flows clearly between all participants. This requires more active moderation than with a monolingual, co-located team.

Speak Clearly and at a Moderate Pace

This is the most critical and simplest practice. As a native or fluent speaker of the common language, you must set the pace. Avoid speaking too quickly. Enunciate your words clearly and use simpler sentence structures.

Be mindful of cultural idioms or slang that do not translate well. Phrases like "let's hit a home run" or "it's a slam dunk" can cause unnecessary confusion. Stick to direct, literal language.

Use Visual Aids

Our brains process visual information much faster than auditory information. Whenever possible, share your screen to anchor the conversation. Display the team's project management board (like Jira, Trello, or Asana).

When a team member discusses a specific task, the facilitator can highlight that task on the board. This provides immediate visual context, connecting the spoken words to a specific work item. It helps everyone follow along, even if they miss a word or two.

Encourage Written Updates in Chat

Ask each team member to post a one-sentence summary of their update in the video call's chat as they speak. This practice serves several purposes:

• Reinforcement: It provides a written record of what was said, which is helpful for those who are more comfortable reading than listening.
• Clarity: It forces the speaker to distill their update to its most important point.
• Reference: It gives others a chance to read and process the update at their own pace.

The Power of Pausing

Silence can feel uncomfortable in a fast-paced meeting, but in a multilingual context, it is a tool for inclusion. After each person provides their update, pause for three to five seconds before moving to the next person. This brief window gives listeners time to process what was said and formulate any questions they might have.

How to Handle Questions and Blockers

The primary purpose of identifying blockers is to get them resolved, but the standup itself is not the place for deep problem-solving. This is a common trap that causes standups to run long and lose focus.

When a blocker is raised:

1. Acknowledge and Clarify: Make sure you understand the issue. Use clarifying phrases like, "Thank you for raising that. So, if I understand correctly, the login API is returning a 500 error?"
2. Assign Ownership: Identify who is needed to solve the problem.
3. Take it Offline: Immediately state that the discussion will happen after the standup. For example: "Okay, let's have you, Maria, and Chen stay on this call for 10 minutes after the standup to investigate. For everyone else, let's move on to the next update."

This approach respects everyone's time while ensuring that blockers are addressed promptly.

Using Live Captions and Translation

Most video conferencing platforms offer built-in live captions, which can be a great help. However, they are typically limited to one language and may not be accurate with varied accents. For teams with multiple native languages, live transcription with parallel translation can be far more effective.

Tools like Subtl run on your computer and can display a real-time transcript of the conversation alongside a translation into a team member's native language. This allows them to read along in the language they are most comfortable with, significantly improving comprehension. When using any transcription or recording tool, be sure to inform all participants and get their consent, as required in many jurisdictions. For more information on your responsibilities, see our guide on legal compliance.

After the Standup: Reinforce and Follow Up

The meeting ends, but the communication shouldn't. What happens after the standup is just as important for ensuring alignment, especially when language barriers are a factor.

Send a Written Summary Immediately

This is non-negotiable for any remote team, but it is absolutely critical for a multilingual one. The summary should be concise, structured, and posted within minutes of the meeting's conclusion.

Keep the format consistent every day:

• Date: YYYY-MM-DD
• Attendees: List of participants.
• Blockers & Next Steps: This is the most important section. For each blocker, clearly state the issue, who is responsible for the next action (the "owner"), and what that action is.

Example:

• Blocker: User profile images are not loading in the staging environment.
• Owner: David
• Action: David will investigate the CDN configuration and provide an update in the team channel by 12:00 PM UTC.

Automated tools that generate meeting notes can help capture these action items accurately, saving the facilitator time and reducing the chance of manual error.

Use a Shared Channel

Post this summary in a public team channel (e.g., in Slack or Microsoft Teams), not via email. This creates a searchable, centralized record of all discussions and decisions. It also allows team members who could not attend to catch up quickly.

Encourage Asynchronous Follow-up

Explicitly tell your team that it is perfectly fine to ask clarifying questions in the channel after reading the summary. Some people may not feel comfortable asking a question in front of the whole group during the live call. Creating a space for asynchronous questions ensures that all doubts are cleared up.

Common Mistakes to Avoid

• Making it a status report for the manager. The standup is for the team to synchronize with each other. The manager or team lead is a facilitator, not an audience. The conversation should be between team members.
• Letting it run long. A 15-minute standup that regularly lasts 25 minutes is a sign that problem-solving is happening during the call. Be disciplined about taking longer discussions offline.
• Ignoring non-verbal cues. On a video call, pay attention to facial expressions. A look of confusion or hesitation can indicate that someone is lost. Gently check in: "Ana, did that last point make sense?"
• Assuming silence means agreement. In many cultures, it can be considered impolite to interrupt or publicly disagree, especially with a senior colleague. Don't mistake silence for understanding. Actively solicit questions by saying, "What questions do you have?" instead of the less effective "Any questions?"

A Quick Checklist for Your Next Standup

Phase	Action
Before	Circulate a fixed agenda in advance.
	Maintain a shared glossary of project terms.
During	Speak slowly and clearly; avoid idioms.
	Share your screen to show the project board.
	Pause between speakers to allow for processing.
	Defer all problem-solving to a separate meeting.
After	Post a written summary with clear action items immediately.
	Encourage follow-up questions in a public channel.

Running a daily standup with a multilingual, distributed team requires more intention and structure than a typical meeting. By focusing on consistency, clarity, and creating multiple ways for people to understand and contribute—both spoken and written—you can turn this daily ritual into a powerful tool for team alignment and inclusion.

For teams working across language barriers, having the right support is key. Subtl provides live translation and transcription for your video calls, along with AI-powered notes to capture key decisions and action items. It helps ensure every team member can follow the conversation and contribute with confidence. Learn more about building better communication habits for your distributed team.