Friday Night Wiki
TopicsAbout
Buy me a coffee
Standups

Chapter 1: Foundations

What Is a Standup?

A standup (or daily standup, daily scrum, daily sync) is a short, time-boxed meeting where a team synchronizes their work, surfaces blockers, and commits to the day ahead.

Key Characteristics

  • Time-boxed: 5-15 minutes, never longer
  • Daily: Same time, same place (physical or virtual)
  • Team-focused: About the work and collaboration, not status reporting
  • Action-oriented: Ends with clear next steps
  • Standing: Traditionally done standing to keep energy high and duration short

The Real Purpose of Standups

❌ What Standups Are NOT For

  • Status reports for managers
  • Detailed problem-solving sessions
  • Sprint planning or retrospectives
  • Individual performance reviews
  • Showing how busy you are
  • Social hour and small talk

✅ What Standups ARE For

  1. Synchronize work: Ensure everyone knows what's happening
  2. Surface blockers: Catch problems early
  3. Enable collaboration: "I need help with X" meets "I can help with X"
  4. Build team cohesion: Daily face time builds trust
  5. Maintain momentum: Keep the team moving forward
  6. Create accountability: Public commitment to daily goals

The History: Where Standups Come From

Origins in Agile/Scrum (1990s-2000s)

  • Born from the Scrum framework
  • Designed to replace long status meetings
  • "Inspect and adapt" philosophy applied daily
  • Originally for co-located software teams

Evolution

Early 2000s: Standups spread beyond Scrum
2010s: Adapted for remote teams
2020s: Async standups become common

The core principles remain, but implementation varies wildly.

Core Principles

1. Self-Organization Over Command-and-Control

The team runs the standup, not a manager dictating orders.

Bad:

Manager: "John, what did you do yesterday?"
John: "I worked on the login feature."
Manager: "Good. Next."

Good:

John: "I finished the login API. Sarah, I'm ready for you to 
start the frontend whenever you want."
Sarah: "Perfect timing! I'll start this afternoon."

2. Collaboration Over Reporting

If information only flows one direction (team → manager), it's a report, not a standup.

Reporting mindset:

  • "I need to tell my boss what I did"
  • One person at a time, no interaction
  • Focus on justifying time spent

Collaboration mindset:

  • "How can I help my teammates succeed?"
  • Natural conversation and questions
  • Focus on moving work forward

3. Problems Over Progress

A standup where everything is "fine" and "on track" is a missed opportunity.

Surface these:

  • Blockers (can't proceed without X)
  • Risks (might become blockers soon)
  • Confusion (not sure how to approach Y)
  • Dependencies (waiting on another team)

The best standups have problems. That's the point.

4. Team Over Individual

Talk about the work, not yourself.

Bad: "I worked on tickets, had meetings, reviewed PRs."
Good: "Ticket 456 is ready for QA. Ticket 789 is blocked on the API team."

5. Continuous Improvement

If your standups aren't evolving, they're dying.

  • Try new formats
  • Ask for feedback
  • Drop what doesn't work
  • Keep what does

The Standup Triangle

Every standup balances three forces:

        EFFICIENCY
            △
           ╱ ╲
          ╱   ╲
         ╱     ╲
        ╱       ╲
  DEPTH ◁━━━━━━━▷ CONNECTION
  • Efficiency: Keeping it short and focused
  • Depth: Understanding problems fully
  • Connection: Building team relationships

You can't maximize all three. Choose based on context:

  • New team? Prioritize connection and depth
  • Crisis mode? Prioritize efficiency
  • Mature team? Balance all three

Types of Standups

1. Classic Round-Robin

Each person answers the three questions in turn.

Pros: Simple, predictable, everyone speaks
Cons: Can feel mechanical, people tune out until their turn
Best for: New teams, small teams (3-7 people)

2. Walk the Board

Go through work items on the board (Kanban, Jira, etc.) from right to left (done → to-do).

Pros: Focus on work not people, surfaces bottlenecks
Cons: Requires visual board, people-based blockers less visible
Best for: Kanban teams, visual thinkers

3. Yesterday's Commitments

Review what was committed to yesterday, then commit to today.

Pros: Strong accountability, clear progress tracking
Cons: Can feel judgmental, doesn't work well with uncertainty
Best for: Teams with predictable work

4. Blockers First

Start with "Who's blocked?" and address those first.

Pros: Most urgent items get attention, super fast when nothing's blocked
Cons: Can skip important updates, harder to track overall progress
Best for: Mature teams, crisis situations

5. Async/Written

Everyone posts updates in Slack/Notion before standup time.

Pros: Flexible timing, written record, works across timezones
Cons: Less connection, easy to skip, harder to have dialogue
Best for: Distributed teams, maker-schedule teams

We'll cover each format in detail in Chapter 2.

When Standups Make Sense

✅ Good Fit

  • Team working on interdependent tasks
  • Fast-changing priorities or context
  • Need for daily coordination
  • Complex problem-solving work
  • Remote teams that need connection
  • Multiple parallel workstreams

❌ Poor Fit

  • Independent work with no collaboration
  • Unchanging, predictable work
  • Team meets naturally throughout the day
  • Already have too many meetings
  • No shared goals or outcomes

If your team doesn't need daily sync, don't do it. Try weekly check-ins instead.

The Standup Mindset

As a Participant

Your job is to:

  • Help the team succeed
  • Surface problems early
  • Be honest about challenges
  • Ask for help when needed
  • Offer help to others
  • Keep it concise

Your job is NOT to:

  • Impress your manager
  • Justify every hour worked
  • Solve problems in the standup
  • Dominate the conversation
  • Hide struggles or blockers

As a Facilitator

Your job is to:

  • Keep time and energy
  • Ensure everyone speaks
  • Park deep discussions
  • Follow up on action items
  • Protect psychological safety

Your job is NOT to:

  • Give status reports to management
  • Solve every problem raised
  • Judge people's productivity
  • Assign work
  • Make all decisions

Common Misconceptions

Myth 1: "Standups are for managers to track work"

Reality: If managers need status updates, there are better tools (dashboards, written updates). Standups are for the team.

Myth 2: "Standing up makes it better"

Reality: Standing helps keep it short, but sitting is fine if you stay focused. Remote teams can't stand together anyway.

Myth 3: "Everyone must speak every day"

Reality: If someone has nothing to add, "Nothing from me today" is perfectly valid. Forced participation wastes time.

Myth 4: "We must use the three questions"

Reality: The three questions are training wheels. Mature teams often evolve beyond them.

Myth 5: "15 minutes is the rule"

Reality: 15 minutes is a maximum. Many teams do 5-7 minute standups effectively. Shorter is often better.

Myth 6: "Standups must be synchronous"

Reality: Async standups work great for distributed teams across time zones.

The Standup Maturity Model

Level 1: Status Theatre

  • Manager asks each person for updates
  • Team members report activities
  • No interaction between team members
  • Focus on looking busy
  • Outcome: Waste of time

Level 2: Mechanical Ritual

  • Team follows format religiously
  • Everyone answers three questions
  • Minimal interaction or questions
  • Gets information out there
  • Outcome: Mildly useful

Level 3: Team Sync

  • Team discusses work collaboratively
  • Problems are surfaced and assigned
  • Natural conversation within structure
  • People help each other
  • Outcome: Actually valuable

Level 4: Self-Optimizing

  • Team adapts format to needs
  • Psychological safety enables honesty
  • Proactive problem-solving
  • Continuous improvement
  • Outcome: Force multiplier

Most teams get stuck at Level 2. This guide will get you to Level 4.

Red Flags

Watch out for these warning signs:

🚩 People arrive late regularly: Standup isn't valuable enough
🚩 It takes longer than 15 minutes: No focus or facilitation
🚩 Only managers ask questions: Team isn't engaged
🚩 Same blockers every day: Nothing gets resolved
🚩 People multitask during standup: Not worth their attention
🚩 Detailed technical discussions: Not parking conversations
🚩 Team members don't know what others are doing: Not listening
🚩 No one ever asks for help: No psychological safety

Measuring Success

How do you know if your standup is working?

Quantitative Signals

  • Standup duration (shorter is often better)
  • Attendance rate (should be >90%)
  • Blockers surfaced per week
  • Time to resolve blockers
  • Number of follow-up conversations

Qualitative Signals

  • Team members arrive prepared and on time
  • Energy level during standup
  • Quality of collaboration after standup
  • Team's ability to self-organize
  • Psychological safety (people share struggles)

The Ultimate Test

If your standup was cancelled tomorrow, would the team miss it?

If the answer is "No" or "We'd be relieved," your standup needs work.

Key Takeaways

  1. Standups exist to help the team collaborate, not to report to managers
  2. The best standups surface problems early so they can be solved
  3. Different teams need different standup formats
  4. Shorter is almost always better than longer
  5. Psychological safety is essential for effective standups
  6. If you don't need daily sync, don't do daily standups
  7. Standups should evolve as your team matures

What's Next

Now that you understand the foundations, let's dive into the practical details:

→ Chapter 2: Structure: Learn the formats, timing, and organization of effective standups