# Running Effective Standups Walkthrough — Learn by Doing ## Before We Begin **Diagnostic:** What is a standup *for*? If the goal were only "share status," would a Slack thread be enough? What does a standup do that async updates can't? **Checkpoint:** You can name at least one purpose beyond status—e.g., unblocking, alignment, coordination—and why it might need to be *live*. --- ## Step 1: Diagnose Your Current Standup **Task:** Reflect on your team's current standup (or one you've observed). List 2–3 things that work and 2–3 things that don't. Is it coordination-focused or status-report-focused? **Question:** What would "success" look like for your standup? How would you know if it's working? **Checkpoint:** You've identified at least one concrete problem (e.g., "runs 25 minutes," "no one listens," "manager uses it for status"). --- ## Step 2: Choose an Alternative Format **Task:** Pick one alternative format (walk the board, blockers first, or topic-based). Write a 1-paragraph "standup script" explaining how your team would run it: who speaks when, what questions are asked, how long each part takes. **Question:** What would need to change for this format to work? (Board? Facilitator? Team habits?) **Checkpoint:** Script is clear enough that someone could run the standup from it. --- ## Step 3: Design a 10-Minute Timebox **Task:** Design a 10-minute standup agenda. Allocate time per section (e.g., blockers 3 min, walk the board 5 min, wrap 2 min). What's your rule for "we need to discuss this in detail"? **Question:** What typically causes standups to run over? How does your design prevent that? **Checkpoint:** Agenda fits in 10 minutes; you have a clear "take it offline" rule. --- ## Step 4: Create an Async Standup Template **Task:** Create an async standup template (Slack, doc, or tool of choice). Include: what each person posts, deadline, how blockers are escalated. Write 2–3 sentences on when async would work for your team and when it wouldn't. **Question:** What would you lose by going async? What would you gain? **Checkpoint:** Template is complete; trade-offs are articulated. --- ## Step 5: List Anti-Patterns and Fixes **Task:** List 3 standup anti-patterns you've seen (in your team or elsewhere). For each, write one concrete fix you could try. **Question:** Why do these anti-patterns persist? What would make the fix stick? **Checkpoint:** Anti-patterns are specific; fixes are actionable. --- ## Step 6: Redesign Your Standup **Task:** Produce a one-page "Standup Redesign" for your team. Include: format, timebox, roles (who facilitates, who attends), and one experiment to try for the next 2 weeks (e.g., "walk the board instead of round-robin"). **Question:** How will you know if the redesign worked? What would cause you to revert? **Checkpoint:** Redesign is practical and includes a testable experiment.