How to give a short update in a meeting

It is your turn in the team meeting. You have done a lot and want to mention the messages, fixes and yesterday’s checks. Your colleagues need something else: where are we now, and what happens next?

Choose a result, not a list of tasks

“I discussed the form with the designer” describes activity. “We agreed on the fields, so development can start” describes progress. If there is no result yet, say so: “Testing is still under way; today we are checking why emails do not arrive.” Do not present a partial check as launch readiness.

Before the meeting, write three lines: result, blocker, next step. Keep each to one sentence. If there is no blocker, do not invent one: say you are on track and name the next check.

Dialogue 1: a developer reports a delay

All dialogues here are fictional. In the first, a team is building a request form but has not tested email delivery yet.

Facilitator: “Can we show the form?” Developer: “It saves requests on the test server. We have not tested emails because we lack access to the email service. I need an administrator’s help by 2 pm today; after testing I can confirm whether it is ready to show.” Facilitator: “Can we show the form itself?” Developer: “Yes, as work in progress. We cannot promise email delivery yet.”

The completed part and its limits are clear. The history of the messages can wait until someone asks why access is still missing. The request says who is needed and by when.

Dialogue 2: a colleague sums up a project

Manager: “How did the new starter guide turn out?” Irina: “We put the common questions in one document. Two new colleagues used it for setup; both got stuck at access permissions. I suggest adding the contact person there and testing the wording with the next new starter.” Manager: “So the guide is finished?” Irina: “The main text is. I will revise the access section tomorrow, then send the team the link.”

Irina does not claim the guide solved every problem. She names a small test, an observation and the next edit. That is more useful in an update than “we did a lot of work.”

How to join in and answer a question

Wait for a pause and connect your point to the topic: “One thing about the form’s readiness: there is a limit.” If the discussion has moved on, ask for a short slot: “Could I have half a minute on the guide? We need an answer about access.” Let the person running the meeting decide when to return to it.

Answer the question first: “Yes, we can show the form, but cannot promise email delivery.” If you lack the information: “I do not know yet; I will check and write by 4 pm.” Offer a time only if you can commit to it. Do not restart the whole story.

A 30-second rehearsal

Choose one real task. Spend a minute filling in the three lines in the diagram. Set a 30-second timer and give the update at your normal pace. If it runs long, remove the backstory and the second example. Try again, then answer: “What exactly do you need from us?”

• Is it clear what is done and what is still being checked?
• Did you name one next step and who will take it?
• If you need help, did you give a specific request and time?
• Did you stop and leave room for a question?

If the issue is the delivery date, use the deadline article below. If you were suddenly asked about an unfamiliar topic, the article on answering without preparation is a better fit. Here, the task is known: report its current state briefly.

Now try the Speech structure demo: switch to the project recap or use the general prompt shown. The website provides a timer and self-check questions, without recording or AI feedback. The Telegram link opens Ritora; in Practice, choose speech preparation. You can continue working on the structure of your speech there. Check access and limits in the app before starting; its interface is in Russian.