Joining and Leading Short Singapore-Style Meetings.
Singlish for Living and Working in Singapore. Lesson 6.
Many Singapore meetings are short, fast and packed with acronyms, yet disagreement is often expressed very gently. In this lesson, you sit in a weekly team meeting where people switch between formal and informal styles. You learn phrases for starting and closing a meeting, giving a quick update, asking targeted questions and checking action points. You hear how colleagues show cautious disagreement with expressions like maybe we can consider another way and I’m not so sure about this part, and you practise using them yourself. You also work with short written agenda items and minutes so you can link spoken comments to written summaries. By the end, you can join discussions without staying silent, express small doubts without sounding aggressive and, when needed, briefly lead part of a meeting in a way that feels natural in a Singapore context.
1. Sitting in your first weekly team meeting.
Today you are going to sit quietly inside a very typical Singapore weekly team meeting. Imagine it is Monday morning, 9.30 a.m. You have just joined a product team based in Singapore, and this is your first time joining their regular online catch up. The team lead, Mei Lin, is Singaporean. Raj is the project manager, Anika handles data, and Jason looks after design. You are dialling in on Teams or Zoom and just observing how they talk. In this first part, I want you to notice three things. First, how quickly they start the meeting and move into the agenda, without a long warm-up. Second, how they give short, focused updates, rather than long speeches. And third, how they use gentle, indirect language when they have concerns. You will read a short transcript on the screen, then listen to the same extract as audio. After that, I will ask you some questions to check that you caught the main purpose of the meeting and the key action point.
The scene: Monday stand-up for the Phoenix App.
You have just joined the Phoenix App team in a Singapore tech company. Every Monday, the team has a fast 15-minute stand-up meeting.
Here is a short transcript from the start of the meeting. Read it once. Do not worry about every word; focus on the flow.
---
Mei Lin (Team Lead): Morning, everyone. Shall we start the meeting?
All: Morning.
Mei Lin: Today we align on the project timeline first, then look at the design changes. Raj, can you give a quick update on the timeline?
Raj (PM): Sure. So, development for Phase 1 is about eighty percent done already. We are still waiting for final API specs from the vendor. If we get by Wednesday, we can still hit next Friday’s target.
Mei Lin: Ok, thanks. Any risk we might slip?
Raj: If the vendor delays again, then a bit difficult. Maybe need to push by two, three days.
Mei Lin: Alright. Let’s keep next Friday for now, but we monitor closely. Action item for you is to chase the vendor and update us by Thursday, can?
Raj: Can.
---
What to notice.
Fast, clear opening
Mei Lin does not give a long speech. She simply says, “Shall we start the meeting?” and then sets the agenda: “Today we align on the project timeline first, then look at the design changes.”
Short, focused update
Raj’s update is only a few sentences: status now, what is blocking, and what happens next.
Soft worries and action points
Mei Lin asks, “Any risk we might slip?” instead of “Will we miss the deadline?”. Then she ends with a very typical Singapore line: “Action item for you is to chase the vendor and update us by Thursday, can?”
Keep this mini-scene in your mind. In the activity below, you will listen to the same extract and show that you understood the key points.
Practice & Feedback
You are going to listen to the short meeting extract you just read. Try this sequence:
First, listen once without looking back at the transcript, if possible. Just relax and notice the rhythm and key words like timeline, target, risk and action item.
Then, if you need, listen a second time while glancing at the transcript above to confirm details.
After listening, answer these three questions in full sentences in one paragraph:
What is the main purpose of this meeting?
What is Mei Lin worried about?
What is Raj’s main action item after the meeting?
Write 3–5 sentences. Imagine you are explaining the meeting to a colleague who could not join. Focus on clear, simple English rather than very long or fancy sentences.
2. Opening and structuring a short meeting.
Now that you have seen and heard how this team actually starts their meeting, let us zoom in on that opening. In Singapore offices, people usually prefer meetings that are efficient and to the point. That means the opening is quite quick, but still polite and clear. As a newcomer, you might feel pressure to sound very formal, but often that makes you sound a bit distant or slow for a short weekly catch up. In this block, we will look at some common phrases that team leads and project managers use to open and structure a fifteen to thirty minute meeting. We will also notice how they signal the order of topics and the time frame, without giving a long speech. After that, you will practise writing your own opening for a short meeting with your team. Even if you are not a manager, it is useful to be able to host a call or stand in for your boss confidently when needed.
How Singapore teams open short meetings.
In the audio, Mei Lin opened the meeting very simply:
> "Morning, everyone. Shall we start the meeting? Today we align on the project timeline first, then look at the design changes."
This style is friendly but efficient. She greets the team, clearly starts the meeting, then tells everyone the purpose and order of topics.
Useful phrases for starting.
Here are some common ways to open a short Singapore-style team meeting.
Greeting and starting
Morning, everyone.
Hi all, thanks for joining.
Shall we start the meeting?
Ok, let’s get started.
Stating purpose
Today we align on the project timeline first.
The main purpose today is to review progress on…
This is just a quick check-in on…
Signalling agenda and order
First we’ll look at… then we’ll move to…
We’ll cover three items today: timeline, budget and risks.
Let’s start with updates from product, then design.
Time frame
This will be a short one, about fifteen minutes.
I’ll try to keep this within half an hour.
Notice that these are mostly simple sentences. You do not need very complex grammar to sound professional. What matters is that people know:
Has the meeting really started?
Why are we here?
In what order will we discuss things?
Roughly how long will it take?
In the activity below, you will write a short opening for a weekly meeting in your own context, using some of these phrases.
Practice & Feedback
Imagine you are hosting a 15‑minute weekly check-in for your team next Monday. There are four people on the call. You want to sound clear, friendly and efficient, like Mei Lin in the Phoenix App meeting.
Write 3–6 short sentences that you would say at the very start of the meeting. Your opening should:
greet everyone,
clearly start the meeting,
state the main purpose,
briefly show the order of topics, and
if you like, mention the time frame.
Use at least two phrases from the list on the screen (for example, Shall we start the meeting?, First we’ll look at…).
Type your sentences as if you are speaking aloud. You can use your real job context, or continue with the Phoenix App team idea. Focus on clarity and natural flow rather than perfection.
Example opening.
> Morning, everyone. Shall we start the meeting? This is just a quick check-in on the Phoenix App launch. First we’ll look at the development timeline, then we’ll move to marketing and support. I’ll try to keep this within fifteen minutes.
Use this example as a model, but adapt it to your own work situation.
3. Giving concise updates in the meeting.
You have seen how Mei Lin opens the meeting. Now let us focus on what most people actually do in these sessions: they give quick updates. In many Singapore teams, the expectation is that your update is around thirty to sixty seconds, not a five minute monologue. Colleagues want to know three main things. First, what is the status now. Second, if there are any blocks or risks. And third, what will happen next, and by when. In Singapore English, people often use words like already, still and yet to show status, and they like very concrete next steps, for example, "I will send the deck by Thursday". In this block, you will see two model updates from Raj and Anika in the Phoenix App meeting. I will show you a simple structure you can reuse in any project. Then you will write a short update for your own work, following that structure.
What makes a good short update?.
Listen again in your head to Raj’s update from Block 1:
> "Development for Phase 1 is about eighty percent done already. We are still waiting for final API specs from the vendor. If we get by Wednesday, we can still hit next Friday’s target."
In just three sentences, he covers:
Status now – eighty percent done already
Block / risk – still waiting for final API specs
Next step and condition – If we get by Wednesday, we can still hit next Friday’s target.
Here is another example from the same meeting.
---
Anika (Data): For analytics tracking, the basic events are already set up in the test environment. We are still missing two events from product. Once I receive those, I can finalise the dashboard by early next week.
---
Again, she follows the same pattern.
A simple structure you can reuse.
You can build your update using this frame:
Big picture + topic
"For the website redesign, …"
"Quick update on the client workshop, …"
Status now
Use words like already, still, yet to show progress.
"The draft deck is already with the client."
"We still have not confirmed the venue yet."
Block or risk (if any)
"We are still waiting for finance approval."
"Main risk is the vendor’s delivery date."
Next step + timeline
"I will send the final version by Thursday."
"If legal clears it this week, we can launch by end May."
When you keep to this structure, your update feels confident and professional, not too long, and very clear for colleagues in a fast Singapore meeting.
Practice & Feedback
Now it is your turn to give a short project update.
Choose one real project from your work, or continue with the Phoenix App example. Imagine Mei Lin has just said, "Can we hear a quick update from your side?"
Write 4–6 sentences following the structure on the screen:
Start with the big picture and topic.
Give the current status, using at least one of these words: already, still, yet.
Mention any block or risk, even if it is small.
End with a clear next step and a realistic time reference.
Write it as if you are speaking in the meeting, not as an email. Keep sentences short and concrete. Imagine your colleagues in Singapore are listening and need to understand you quickly.
Mini frame for your update.
> Quick update on [project name]. [Status now, with already / still / yet.] [Block or risk, if any.] [Next step + by when.]
You can adapt this frame to fit your own work context.
4. Showing gentle disagreement in the meeting.
Meetings in Singapore can be fast, but open conflict is usually avoided. People often have doubts or concerns, but they express them in a gentle way. Instead of saying, "No, that will not work", you are more likely to hear, "I’m not so sure about this part" or "Maybe we can consider another option". The message is still clear, but the style protects harmony and face. In our Phoenix App meeting, imagine that a regional manager suddenly suggests launching one week earlier than planned. You feel the deadline is too aggressive, but you also do not want to sound negative in front of everyone. In this block, we will look at some typical Singapore-style phrases for soft disagreement. Then you will practise a short chat-style exchange where you share your concern while still sounding constructive and respectful.
A typical disagreement moment.
Imagine this happens halfway through the Phoenix App meeting.
---
Tom (Regional Manager): If possible, I’d like to launch one week earlier, before the conference. Can?
Mei Lin (Team Lead): Hmm, I’m not so sure about this part. The team is already quite stretched, and vendor timeline is still uncertain.
Tom: Ok, but maybe we try? Marketing really prefers earlier.
Mei Lin: Maybe we can consider another option. We keep the current launch date, but do a soft launch for key users before the conference.
---
Notice how Mei Lin disagrees. She never says "No" directly. Instead, she uses softening phrases before she shares her concern.
Useful softening phrases.
Here are some common patterns you will hear in Singapore meetings:
"I’m not so sure about this part."
"I’m a bit concerned about the timeline."
"Maybe we can consider another option."
"From my side, I feel the risk is quite high."
"One thing we might want to think about is…"
"Maybe we keep this for Phase 2 instead?"
We can think of them as two layers:
Softening layer
Clear message
I’m a bit concerned…
This may be a problem.
I’m not so sure…
I disagree.
Maybe we can consider…
I suggest a different way.
Using the softening layer does not hide your opinion. It just makes it easier for others to accept.
In the activity, you will write a few short lines as if you are chatting with your boss or a senior colleague during or just after the meeting.
Practice & Feedback
Imagine Tom has just said in the meeting, "If possible, I’d like to launch one week earlier." You think this is too risky, but he is more senior than you.
Write a short chat-style exchange as if you are messaging him on Teams just after the meeting to share your concern. Use 3–6 short messages.
Format it like this:
You: …
Tom: …
You: …
Your messages should:
use at least two softening phrases from the list above (for example, I’m a bit concerned…, Maybe we can consider another option…),
clearly explain why the earlier date is difficult, and
offer one alternative or compromise.
Write in a natural, polite tone, like a real internal chat in a Singapore office.
Example soft disagreement line.
> You: Hi Tom, thanks for the suggestion just now. I’m a bit concerned about the earlier launch date because the vendor timeline is still not confirmed. Maybe we can consider keeping the current date, but highlight the app in a different way during the conference?
5. Checking action points and reading minutes.
So far, you have opened the meeting, given an update, and practised gentle disagreement. The last key skill for short Singapore meetings is to be very clear about action points. Often, people feel shy to ask questions in the moment, then later they are not sure what they agreed to do. Singapore teams usually solve this in two ways. First, someone will summarise actions at the end of the meeting. Second, a colleague will send short written minutes or notes afterwards. In this block, I will show you a small extract from the Phoenix App meeting minutes. You will see how spoken comments are turned into short, efficient action lines. Then you will practise reading those minutes and asking one or two clear confirmation questions, using typical local phrases like "Just to confirm…" and "So my action item is…".
From meeting talk to written minutes.
After the Phoenix App stand-up, Mei Lin sends a short email with the key action points. Here is an extract.
Phoenix App Weekly Stand-up – Key Action Items.
Timeline
Raj to follow up with vendor on API specs and update team by Thu 5 pm.
Analytics
Anika to finalise tracking dashboard once remaining events are received from product team (target early next week).
Launch plan
Mei Lin to discuss launch date options with Tom and revert to team by next Monday.
Compare this to what you saw or imagined in the meeting:
In the meeting, Mei Lin said: "Action item for you is to chase the vendor and update us by Thursday, can?"
In the minutes, it becomes: "Raj to follow up with vendor… by Thu 5 pm."
The style is:
short,
no full sentence subject like "He will",
clear who, what and by when.
Phrases for confirming action points.
In the meeting, if you are not completely sure, it is polite and normal to ask for confirmation. Useful phrases include:
"Just to confirm, my action item is to…"
"So I’ll check with [department] and revert by [day], right?"
"Can I clarify the deadline for this task? Is it…?"
"So timeline is still next Friday, is it?"
Using these questions shows that you are responsible and careful, not that you are weak.
In the activity, you will read the same action items again and then write what you would say to double-check your own tasks.
Practice & Feedback
Read the three action items in the Phoenix App minutes carefully. Imagine you are Raj in this meeting. You want to make sure you understood correctly, so you ask Mei Lin to confirm.
Write 2–4 short sentences as if you are speaking near the end of the meeting. Your sentences should:
use at least one confirmation phrase such as "Just to confirm…" or "So I’ll… right?",
clearly state what you will do and by when, based on the minutes, and
sound polite and natural, not like an interrogation.
After that, add one more sentence where you check if there is any other action item for you.
So in total, you should have 3–5 sentences. Imagine Mei Lin is busy and you want to be clear but very efficient.
Key Action Item for Raj (from the minutes).
Raj to follow up with vendor on API specs and update team by Thu 5 pm.
Use this line to build your confirmation questions and statements.
6. Leading a short segment of the next meeting.
You have now practised all the key pieces of a Singapore-style team meeting: opening, giving updates, soft disagreement and confirming action points, plus reading short minutes. In this final block, you will put everything together. Imagine it is next week, and Mei Lin has asked you to lead a short segment of the Phoenix App stand-up because she has to join five minutes late. Your role is to start the call, get one quick update, respond with a small concern, and then summarise the action clearly before Mei Lin arrives. This is a realistic situation in Singapore offices, especially if you are a senior individual contributor or manager. On the screen, you will see a simple checklist and a short model script. Then you will write your own mini script for this meeting segment, using the language we have explored. Treat it like a rehearsal so that next time, when your boss suddenly says, "Can you help host first?", you feel ready.
Your role: temporary meeting lead.
Scenario: Next Monday, Mei Lin messages you five minutes before the stand-up.
> "I’ll be a bit late, traffic jam. Can you help start the meeting first and get an update from Anika? I’ll join halfway."
You agree. Now you are the temporary meeting lead.
Checklist for your mini segment.
In your 5–7 minute segment, you should:
Open the meeting
Greet everyone.
Clearly start the meeting.
Briefly state purpose.
Invite an update
Ask Anika for a quick update on analytics.
Let her speak.
Respond with a gentle concern
If there is a risk, use a soft disagreement or concern phrase.
Ask one short follow-up question if needed.
Summarise action point(s)
End with one or two clear actions and timelines.
Close your segment politely.
Mini model script.
> You: Morning, everyone. Shall we start the meeting? Today is just a quick check-in while we wait for Mei Lin. Let’s hear a short update from Anika on analytics first.
>
> Anika: Sure. The dashboard is almost done already. I’m still waiting for two events from product. If I get them by Wednesday, I can finalise by early next week.
>
> You: Thanks, Anika. I’m a bit concerned we might not get the events on time. Have you already checked with the product team this week?
>
> Anika: Not yet, I’ll ping them after this.
>
> You: Ok, just to confirm, your action item is to follow up with product on the two events and update us by Thursday. If all good, we can say the dashboard is ready next Monday. Alright, we’ll pause here until Mei Lin joins.
In the activity, you will write a similar script, but adapt it to your own style and work reality.
Practice & Feedback
Now write your own mini meeting script for this situation, or for a similar weekly meeting in your real job.
Your script should be 8–10 lines and follow this pattern:
You open the meeting and state the purpose.
You invite one colleague to give a short update.
The colleague gives a brief update, including status and maybe a small risk.
You respond with a gentle concern or question, using at least one softening phrase from earlier (for example, I’m a bit concerned…, Maybe we can consider…).
You summarise the action point(s) and close your segment.
Format it like a script:
> You: …
> Colleague: …
> You: …
Use simple, natural English, and imagine real people in your team are speaking. This is your chance to rehearse leading part of a Singapore-style meeting.
