# Running Effective Standups — Beyond Status Reports

<!-- hint:slides topic="Effective standups: purpose (coordination vs status), format options, timeboxing, async alternatives, and anti-patterns" slides="5" -->

## The Purpose of Standups

A daily standup (or daily scrum) is **not a status report to your manager**. Its purpose is **coordination**: help the team align on the day, surface blockers, and decide who needs to talk to whom afterward. When standups become status reports, people disengage and the meeting loses value.

**Scrum defines three questions** (what did I do, what will I do, any impediments?), but many teams find these lead to monologues. The key is to design the standup so it **enables coordination**, not reporting.

## The Three Questions — and Why They Often Fail

The classic format:

1. What did I do yesterday?
2. What will I do today?
3. Any blockers?

**Why it fails:** People recite lists. No one listens. Blockers get buried at the end. Managers use it to "check in," turning it into a status meeting. The antidote: refocus on **blockers and coordination**—what needs to happen *next*, and who needs to talk to whom.

## Alternative Formats

### Walk the Board

Go column by column on your Kanban/Scrum board instead of person by person. For each in-progress or "ready" item: Who's working on it? Blocked? Needs help? This keeps focus on **work**, not people.

**Example:** "The API integration story—Sarah, still in progress? Anyone blocked on it?"

### Focus on Blockers

Start with: "Anyone blocked or need help today?" Resolve those first. Then optionally do a quick round of "what's your focus today?" This flips the script: coordination first, status second.

### Round-Robin vs Topic-Based

- **Round-robin:** Each person speaks in turn. Predictable, but can feel like a checklist.
- **Topic-based:** Organize by work item or theme. "Let's go through the payment migration—who's involved, what's the status?" Better for cross-cutting work.

## Timeboxing — 15 Minutes Max

Standups should be **short**. 15 minutes is the upper bound; many effective teams do 10 or less. If you're running over:

- Take detailed discussions **offline**—"Let's sync on that after standup."
- Use a timer. When someone drones, gently: "Can we pick this up in a breakout?"
- Consider reducing frequency (e.g., three times a week instead of daily).

## Async Standups

**When they work:** Distributed teams, flexible schedules, or teams that don't need real-time coordination.

**Tools:** Slack (threaded updates), Loom (short video updates), Geekbot, Standuply, or a shared doc (Notion, Google Doc) where everyone posts by a deadline.

**Template example:**
```
Yesterday: [1–2 bullets]
Today: [1–2 bullets]
Blockers: [none / describe]
```

**Trade-offs:** Async saves meeting time but loses real-time discussion. Best when most work is independent; less ideal when lots of coordination is needed.

## Sync vs Async Standup Flow

```mermaid
flowchart TD
  subgraph Sync["Sync Standup"]
    A[Team gathers same time] --> B[Quick round or walk the board]
    B --> C[Blockers surfaced]
    C --> D[Breakouts scheduled]
  end

  subgraph Async["Async Standup"]
    E[Each person posts by deadline] --> F[Team reads updates]
    F --> G[Blockers flagged in thread]
    G --> H[Follow-up DMs or ad-hoc sync]
  end

  Sync -->|Real-time coordination| D
  Async -->|Flexibility, no meeting| H
```

## Common Anti-Patterns

| Anti-Pattern | Better Practice |
|--------------|-----------------|
| Status report to manager | Facilitate for the team; manager observes or doesn't attend |
| Problem-solving in standup | "Let's grab 2–3 people and discuss after" |
| Running long | Timebox 15 min; take discussions offline |
| Low energy / no one listening | Change format (walk the board, focus on blockers); make it interactive |
| Same person always talks longest | Use a timer or pass-the-ball; "One thing you're focused on today" |

## Tips for Remote Standups

1. **Cameras on** — Improves engagement and signals presence.
2. **Stable video and audio** — Invest in good mics; lag kills flow.
3. **Screen share the board** — So everyone sees the same view when walking the board.
4. **Use chat for follow-ups** — "We'll sync in a thread / DM after."
5. **Rotate facilitators** — Spread ownership; avoid one person dominating.

## When to Skip Standup Altogether

Consider skipping or reducing frequency when:

- Work is highly independent and low-coordination
- Team is very small (2–3 people) and already in constant contact
- You've tried multiple formats and no one finds value
- You're between sprints or in a light work period

Standup is a **tool**, not a religion. If it doesn't serve coordination, change it or drop it.

## Quick Format Comparison

| Format | Best For | Risk |
|--------|----------|------|
| Three questions | Traditional Scrum teams | Becomes status report |
| Walk the board | Kanban, visual teams | Requires up-to-date board |
| Blockers first | Teams with many dependencies | Might skip "what I'm doing" context |
| Async | Distributed, flex schedules | No real-time discussion |

Choose based on your team's coordination needs and culture.