Standups Tutorial
A practical tutorial on running daily standups that teams actually find useful. Covers formats, communication, team culture, blockers, remote and async setups, anti-patterns, and advanced techniques.
Chapters
About this tutorial
A practical guide to running daily standups that the team actually finds useful, instead of the meeting everyone dreads.
Who This Is For
- Team members tired of standups that feel like status reporting
- Team leads running standups for the first time (or the hundredth)
- Managers wondering why their standups feel flat
- Anyone introducing standups to a team from scratch
Why Standups Matter
When run well, standups:
- Keep everyone aligned and moving forward
- Surface problems before they become crises
- Build trust and psychological safety
- Create accountability without micromanagement
- Save hours of meetings and Slack pings
- Strengthen team cohesion
When run badly, they are:
- A waste of everyone's time
- Status theatre for managers
- A source of low-grade dread
- An obstacle to actual work
Contents
| Chapter | Topic | Description |
|---|---|---|
| 01 | Foundations | What standups are, their purpose, and core principles |
| 02 | Structure | Formats, timing, and organising effective standups |
| 03 | Communication | How to speak and listen well in standups |
| 04 | Team Culture | Psychological safety and high-performing teams |
| 05 | Handling Problems | Blockers, escalations, and difficult situations |
| 06 | Remote and Distributed | Async and remote standups that work |
| 07 | Anti-Patterns | Common mistakes and how to avoid them |
| 08 | Advanced Techniques | Techniques used by high-performing teams |
How to Use This Tutorial
- Read sequentially for the full picture
- Try one change at a time. Don't overhaul everything on Monday
- Get team feedback before and after changes
Prerequisites
None. This guide works whether you are:
- A team member attending standups
- A team lead running standups
- A manager observing standups
- Someone starting standups from scratch
Quick Start
If you need to improve standups today:
1. Keep it short (15 minutes max, 5 to 10 is better)
2. Stand up if you can. It keeps the energy honest
3. Talk about work, not people
4. Take detailed conversations offline
5. End with a clear plan everyone agrees on
A Four-Week Path
Week 1 Master the basics
Read chapters 1 to 3, keep your update under 2 minutes,
help others stay on track.
Week 2 Build culture
Read chapter 4, support struggling teammates,
celebrate small wins.
Week 3 Handle challenges
Read chapters 5 and 6, surface blockers earlier,
practise escalating well.
Week 4 Level up
Read chapters 7 and 8, name anti-patterns in your standup,
try one advanced technique.
Core Principles
1. Respect Everyone's Time
The standup is one of your team's most expensive meetings. Every minute costs N salaries.
2. Trust Through Transparency
Standups only work when people feel safe being honest about problems.
3. Collaboration, Not Reporting
If you are only reporting status, send an email instead.
4. Keep Momentum
The standup should energise the team, not drain it.
5. Adapt to Your Context
What works for a 5-person co-located team is not what works for a 50-person distributed org.
Quick Reference
Signs Your Standups Are Working
- Team members arrive on time and engaged
- Blockers surface early and get resolved
- People ask for help without fear
- Cross-team collaboration happens naturably
- New team members get up to speed quickly
- Everyone leaves knowing what to do next
- The standup rarely runs over time
Signs Your Standups Are Broken
- People arrive late or multitask through standup
- It is just status reporting to a manager
- Blockers are hidden or minimised
- People talk for 5+ minutes
- Side conversations and interruptions are constant
- Nothing actionable comes from it
- People openly resent the standup
The 3 Questions Framework
The classic format still works:
1. What did I accomplish yesterday?
2. What will I do today?
3. What is blocking me?
The magic is in how you answer them (covered in Chapter 3).
Beyond Software Engineering
Standups originated in agile software development, but they work for:
- Marketing teams planning campaigns
- Sales teams tracking deals
- Support teams managing tickets
- Operations teams handling incidents
- Any team doing collaborative work
Time Investment
- Reading this guide: 2 to 3 hours
- Becoming good at standups: 4 to 6 weeks of practice
- Return: Hours saved every week and better team performance
Additional Resources
Books
- Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland
- The Five Dysfunctions of a Team by Patrick Lencioni
- Radical Candor by Kim Scott
- Team Topologies by Matthew Skelton and Manuel Pais
Online
- Atlassian's Guide to Standups
- Martin Fowler's "It's Not Just Standing Up"
- Jason Yip's "Patterns for Daily Standup Meetings"
A note on tone: this guide is opinionated. Where an experienced practitioner has a strong default, you get the default and the reasoning. Where teams genuinely vary, you get options. Take what fits, ignore what does not.
Start with Chapter 1: Foundations.