The Daily Standup When You Stutter
How to handle daily standup meetings when you stutter. The three-sentence formula and why going first reduces anticipatory tension.
By Stuttering Recovery · | Part of situations.

Every other difficult speaking moment in your career is an occasional event.
A job interview happens once every three years. A boardroom presentation happens once a quarter. A salary negotiation happens once a year. Because those events are rare, they arrive with intense unfamiliarity: new faces, new rooms, and unpracticed sentences.
The daily standup is the exact opposite. It is an appointment that repeats every single morning at 9:30 AM with the exact same seven people. It follows the exact same three questions: what you did yesterday, what you are doing today, and what is blocking your progress.
Because it happens every twenty-four hours, the daily standup is often the source of chronic daily dread for an adult who stutters. But that same daily frequency makes it the single most valuable rehearsal opportunity in your working life: you can prepare the exact same three sentences daily, and the preparation compounds.
This guide covers practical preparation for the daily standup: how to structure your update, why speaking order matters, how to manage recurring technical terms, and when to request reasonable adjustments. It does not replace speech therapy with a licensed speech-language pathologist, who can help tailor individual techniques to your speech pattern.
A fixed turn, at a fixed time, every day: why that is both worse and better
The psychological pressure of a standup comes from its rigid predictability.
At 9:28 AM, you open the calendar invite. You know that within the next fifteen minutes, your name will be called. You know that the entire team will look at your video tile or turn toward you in the circle, waiting for sound.
This waiting period builds predictable physical and mental tension:
- Elevated heart rate: As each teammate speaks, your turn approaches, and your breathing speeds up.
- Physical tension: Tension builds while you wait. Your neck, jaw, and throat tighten as your turn draws nearer, making it harder to initiate speech smoothly.
- Mental scanning: You rehearse your update silently, scanning every word for difficult sounds. Every word substitution alters the sentence, making what you plan to say less stable.
Yet this predictability is also your greatest asset. In an ordinary meeting, you never know when a gap will appear to interject. In a standup, your speaking slot is built into the agenda. You do not have to compete for the floor; the floor is handed to you.
The three sentences, written the night before

The most common mistake engineers, designers, and project managers make is inventing their standup update while listening to other people talk.
Trying to compose thoughts while monitoring physical tension splits your attention. The result is rushed phrasing and hurried initiation.
On its workplace accommodation resource for stuttering, the Job Accommodation Network notes that preparing what needs to be said beforehand, using a script when applicable, and keeping spoken updates concise and focused are practical strategies for managing job-related speech demands.
The practical antidote is writing down three concise sentences at the end of the previous working day:
| Standup Question | Structured Sentence Formula |
|---|---|
| 1. What did you finish yesterday? | “Yesterday I wrapped up the database schema migration.” |
| 2. What are you working on today? | “Today I’m writing the unit tests for the auth flow.” |
| 3. Are there any blockers? | “No blockers on my end, ready for review.” |
Notice the structure of these sentences:
- You can choose the first word deliberately. If a specific opening sound feels challenging, choose a word that starts more easily, or add a short lead-in word (such as “So” or “And”) to help establish airflow before the phrase begins. When starting on a vowel or gentle sound, an easy onset helps ease into vocal initiation rather than pushing against a hard block.
- The sentences are short: six to ten words each.
- The content is concrete and technical.
Once written, say these three sentences out loud at your desk before logging off for the evening. When you join the call the next morning, your motor system is executing a known pattern rather than improvising under pressure. For broader remote meeting strategies, see our guide on video calls when you stutter.
Going first, and why the order matters more than the words

In most agile teams, the order of updates is informal: either the scrum master calls on people at random, or team members volunteer.
Waiting to be picked is the most exhausting way to experience a standup. If eight people speak before you, you endure eight separate waves of anticipation. By the time your name is called, tension has been building while you wait for ten minutes.
(Nobody in the circle actually wants to speak first, which makes volunteering oddly easy.)
The solution is volunteering to speak first or second:
“Morning everyone. I can kick things off today.”
Guidance from STAMMA on stammering at work recommends volunteering to speak first in meetings where possible to get your turn over with early, rather than waiting while tension accumulates.
Speaking early gives you three clear advantages:
- Zero anticipation time: You speak before physical tension has time to accumulate.
- Fresh auditory environment: The meeting has just begun; attendees are still settling in, and conversational pacing is relaxed.
- Total relief for the remainder of the call: Once your update is complete, you can relax, listen to your colleagues, and participate without internal tension.
If your team follows a set board order where the facilitator moves from top to bottom, you can ask your manager or scrum master for a fixed slot in the sequence as a reasonable adjustment. STAMMA’s guidance on reasonable adjustments offers general guidance on how to ask your employer for adjustments; see our guide to job interviews when you stutter for what equality laws in the UK and US require of employers, or read official GOV.UK guidance on workplace reasonable adjustments.
Blockers, dependencies, and the words that repeat every day
Technical standups feature recurring vocabulary that carries high phonetic demand: pull request, deployment, blocking, Kubernetes, dependencies, stakeholder.
Because these words repeat every day, a speaker can develop conditioned dread around them. If you blocked on the phrase “pull request” on Tuesday, you will dread saying it on Wednesday.
To manage recurring difficult words:
1. Lighten articulatory contact
When saying words that start with plosives (like /b/ in blocker or /p/ in pull request), bring your lips or tongue together with minimal physical pressure. Touch articulators as lightly as possible to keep airflow moving. Read our guide on light contact to practice this specific adjustment.
2. Connect words into continuous airflow
Do not isolate the difficult technical term by stopping completely before it. Keep airflow moving steadily through the phrase: link the sounds naturally, as in “submitting a PR this afternoon,” rather than bracing for the acronym in isolation.
3. Have a precise script for blockers
Admitting a blocker in front of colleagues can feel vulnerable, which amplifies speech tension. Standardize your phrase: “I’m waiting on API access from DevOps. I’ve pinged Sarah in Slack.”
If you are joining a new company and handling introductions alongside daily standups, review our framework for introducing yourself at work.
What to do when you block in front of the same eight people every morning
Because you see your standup team every day, blocking in front of them carries a unique emotional weight: you worry that they are keeping a running tally of your speech.
In reality, software teams are focused entirely on their own tickets, their upcoming deadlines, and what they need to accomplish before noon. (The running tally exists only in your own head; the person next to you is usually busy rehearsing their own ticket.) When a block happens:
- Do not fight the closure: If your throat locks on a word, stop pushing. Pushing harder turns a brief pause into a prolonged physical struggle.
- Release the breath and reset: Let the air drop, allow your jaw to release downward, and restart the phrase using gentle vocal initiation. For step-by-step guidance on this process, review stuttering blocks and how to release one.
- Finish the update calmly: Do not rush the remaining words to compensate for the silence. Maintaining an unhurried tempo demonstrates that you are in control of your communication.
The advantage of meeting the same group daily is familiarity. Many people who stutter find that consistent, predictable contact with a fixed team removes the mystery around speech blocks. Over time, teammates become accustomed to your speaking rhythm, the unfamiliarity disappears, and the standup becomes an ordinary routine. If you want to tell the team, read our guide on saying something about your stutter in week one.
Asynchronous standups: when writing it is the right call, and when it is avoidance
Many modern tech organizations support asynchronous standups, where team members post their daily
updates in a Slack or Microsoft Teams channel (#dev-standup) rather than meeting on video.
Writing your update is a legitimate professional tool, but it requires honest discernment:
When async is the right call:
- Distributed time zones: When team members are spread across multiple continents, synchronous video standups are inefficient for everyone.
- Acute vocal fatigue or illness: If you are experiencing laryngitis or severe physical exhaustion, posting written bullet points preserves energy.
- Complex technical detail: When your update contains specific commit hashes, error codes, or log links that teammates need to read and click.
When async is an avoidance trap:
If your entire team meets on video every morning at 9:30 AM, and you request written exemption solely to escape the sensation of blocking, the accommodation can backfire. Async updates protect your morning from immediate tension, but they do not make the next live meeting any easier.
Avoidance strengthens fear. Removing yourself from the circle keeps the fear of speaking alive, and withdrawing from daily interaction reduces your informal visibility with teammates and leadership.
This week, try one change: write your three sentences before you log off on Thursday evening, and volunteer to go first on Friday morning. If speaking on camera continues to feel overwhelming, a licensed speech-language pathologist can help you practice individual strategies in a low-pressure setting.
Questions people ask
How do I get through a daily standup if I stutter?
Draft your three core updates the evening before, speak them out loud once before joining the call, and volunteer to speak early in the circle. Going first removes the compounding anticipatory tension of waiting while colleagues give their updates.
Should I do async standups instead?
Written updates in Slack or Teams are an effective accommodation when team schedules or time zones warrant it, or during periods of extreme vocal fatigue. However, using async updates solely to evade speaking can reinforce avoidance patterns, whereas the daily standup provides a structured, low-stakes routine for speaking practice.