Your ninety seconds in the daily stand-up
Your first project team at Kalvi Analytics runs a stand-up at 9:45 every morning. Nine people, ninety seconds each, and yours is next. You are behind on one task because you have been stuck on something since yesterday afternoon, and you have not told anyone yet. This is the smallest professional speaking task there is, and it is the one freshers are judged on daily.
A beginner-level session of about 5 minutes.
An update with one thing left out sounds exactly like a complete one. Nobody notices today. The cost turns up later, when the delay is bigger and it has had your name on it all week. That is what makes ninety seconds harder than it sounds: the speaking is short, but you are deciding, in front of eight other people, whether to admit something you have been sitting on since yesterday afternoon. The scrum lead is moving briskly and asks a follow-up when an update is vague, so an unclear answer costs you more time than a clear one would have. What you want is a version you can say at speed, in the same order, every morning, without rehearsing it the night before.
Angles worth taking
- Put the blocked item early in your ninety seconds; buried at the end, it sounds like something you hoped nobody would reach.
- A follow-up question from the lead is a signal your opening was too vague; answer it in one sentence, not five.
- Skip the debugging narrative, because the team needs the shape of the problem rather than the sequence of things you tried.
- Address the person who can unblock you by name, so the request lands on someone instead of dissolving into the group.
- When an earlier update runs long and your turn gets squeezed, cut the finished work and keep the blocker.
- One apology is fine; the second and third eat the seconds you needed for the actual problem.
Who is in the room
You play
A fresher giving their daily stand-up update
You speak with
A scrum lead running the stand-up briskly, who thanks each person, moves on quickly, and asks one follow-up if an update is vague
Phrases to reach for
These are shown to you before the session starts. They are what you are asked to use, not a list the scorer is checking off.
Ready to speak?
Free to start. You need a TalkDrill account to speak — reading this page does not.
Browse all roleplay scenariosThe format
Modes
Learn (guided) · Mock (exam-real)
How a roleplay session works
Read your brief
Your role, the situation, and what a good outcome looks like. The counterpart has their own brief, and you do not get to read it.
Open the conversation
You speak first in most scenarios. How you open sets what you can ask for later, which is most of the exercise.
Handle the turn
Somewhere in the middle it stops going your way — a refusal, a counter-offer, a rebuttal you did not prepare for. That moment is the scenario.
Read the report
Outcome, the phrases you used and the ones you missed, fluency and clarity, and the specific line worth rewriting.
What you're scored on
Across every roleplay, the report looks at the same four things — because they are what makes a real conversation work or fail.
Give a clean three-part update — done, doing, blocked — say what you are stuck on without apologising for four sentences, and ask one specific person for help by name.
Task outcome
Whether you got what the brief asked for: the refund, the extension, the concession, the point conceded.
Appropriacy
Whether the register fits. A complaint that is too soft gets nothing; the same complaint too hard gets a manager and no refund.
Recovery
What you do with the unexpected turn — repair, rephrase, push back, or stall. This is where most of the marks move.
Delivery
Fluency, pronunciation and pace, judged in conversation rather than in a prepared monologue.
More roleplay scenarios
All roleplay scenarios · Placement scenarios · All speaking practice