Chapter 8: Advanced Techniques | Standups

Beyond the Basics

You've mastered the foundations. Now it's time to level up.

This chapter contains advanced techniques used by high-performing teams to make standups exceptional.

These aren't necessary for every team. Use what fits your context.

The Pre-Standup Prep

Rockstars don't wing it. They prepare.

The 60-Second Prep Ritual

Every morning before standup:

Look at yesterday's commit/work (10 seconds)
- What did I actually complete?
Check today's tasks (10 seconds)
- What am I committing to?
Scan for blockers (20 seconds)
- What might stop me?
- What do I need from others?
Identify collaboration opportunities (20 seconds)
- Who might need my help?
- Who can help me?

Write a one-sentence update. Practice saying it.

The Team Board Review

2 minutes before standup:

Scan the work board (Jira, etc.)
Note bottlenecks or pileups
Identify risks
Prepare questions

Come to standup informed about the team's work, not just your own.

Advanced Facilitation

The Energy Opener

Start with energy to set the tone.

Standard opening:

"Good morning. Let's start standup."

Energy opening:

"Morning team! Quick wins before we start: We shipped the login feature
yesterday and it's gotten great feedback. Nice work! Okay, let's dive in."

30 seconds of positivity sets the mood for the whole standup.

The Pattern Interrupt

When standup gets stale, shake it up.

Change the order:

Random person starts (roll dice, spin wheel)
Reverse alphabetical
Birthday order
Who's had the most coffee

Change the questions:

"What's your biggest win yesterday?"
"What's your biggest risk today?"
"Who needs help from the team?"

Change the format:

Walk the board instead of round-robin
Blockers first, then updates
Accomplishments only, skip plans

The Facilitation Hot Potato

Rotate who facilitates daily.

Benefits:

Shared ownership
Everyone learns facilitation
Fresh perspective
Prevents facilitator burnout

How:

"Alice, you're facilitating today. Bob, you're up tomorrow."

New facilitator script:

"Morning everyone, I'm facilitating today. Let's keep it to 10 minutes.
Sarah, want to start?"

The Feedback Loop

End every Friday standup with:

"Quick pulse check: How valuable was our standup this week? 1-10."

[Everyone holds up fingers or types in chat]

"Thanks. I see mostly 7s and 8s. What would make it a 9 or 10?"

Continuous improvement through feedback.

Advanced Communication

The Hook

Start your update with something that grabs attention.

Boring:

"I worked on the API yesterday."

Hook:

"I found a security vulnerability in our authentication system yesterday."

Boring:

"I'm finishing the feature today."

Hook:

"We're launching the feature today. Cross your fingers."

Make people want to listen.

The Story Arc

Structure your update like a mini-story.

Problem → Action → Resolution (or current state)

"The API was returning inconsistent data [PROBLEM]. I spent yesterday
debugging and found it was a caching issue [ACTION]. Fixed and deployed.
Data is now consistent [RESOLUTION]."

Or:

"Need to improve search performance [PROBLEM]. Yesterday I benchmarked
different approaches [ACTION]. Elasticsearch looks promising, starting
implementation today [CURRENT STATE]."

The Handoff

Explicitly enable the next person's work.

Weak:

"API is done."

Strong:

"API is done and deployed to staging. Sarah, you can start the UI
integration. I've documented the endpoints in Confluence and I'm
available for questions this afternoon."

Make it effortless for others to build on your work.

The Ask

Request help in a way that makes it easy to say yes.

Weak:

"I might need some help with this."

Strong:

"I need a 30-minute pairing session on WebSocket architecture. Who's
got experience with that and has time this afternoon?"

Specific, time-bounded, easy to commit to.

The Teach

Share learnings that help the team.

"I discovered a better way to handle API errors yesterday. It reduces
code by 50%. I'll share it in our tech talk next week, but ping me if
you want to see it earlier."

Knowledge sharing builds team capability.

Advanced Blocker Handling

The Pre-Blocker

Surface risks before they become blockers.

"Not blocked yet, but the third-party API has been flaky. If it goes
down, I'll be blocked on integration testing. Flagging it now."

Better to flag early than surprise the team later.

The Escalation Path

Be explicit about escalation.

"Blocked on design approval for 3 days now. If I don't get it by EOD
today, I'm escalating to the design director tomorrow. Just giving
everyone a heads up."

Clear escalation path prevents lingering blockers.

The Workaround

Don't just accept blockers. Find workarounds.

"Blocked on production database access. Workaround: I'm using staging
data to continue development. Not ideal but keeps me moving while ops
sorts out access."

Show agency and problem-solving.

The Blocker Swap

Trade blockers when it makes sense.

You:  "Blocked on frontend work, waiting for designs."
Alice: "I'm blocked on backend API. Want to swap? I'll work on your
       backend task if you help me with frontend work I can do."

Creative unblocking through collaboration.

Advanced Team Dynamics

The Assist

Proactively unblock teammates.

Sarah: "Stuck on this database query optimization."
You:   "I just did something similar last week. Let's pair after standup."

Don't wait to be asked. Offer help.

The Question

Ask questions that create value.

Surface dependencies:

"John's working on the API, Sarah's working on the frontend. Have you
two synced on the data format?"

Identify risks:

"We have three people working on the same file. Should we coordinate
to avoid merge conflicts?"

Clarify priorities:

"We have two P0 bugs and three new features in progress. What's the
actual priority?"

The Bridge

Connect people who should talk.

"Alice, you mentioned needing auth help. Bob just finished the OAuth
implementation. You two should sync."

Be the connector.

The Celebrate

Recognize teammates' work.

"Before we move on, I want to call out Carol. She stayed late yesterday
to fix a production bug that was blocking me. Really appreciate it."

Public recognition builds morale and culture.

Advanced Formats

The Kanban Walk

Walk the board from right to left (done → to-do).

DONE → IN REVIEW → IN PROGRESS → BLOCKED → READY → BACKLOG
  ↓        ↓            ↓           ↓        ↓        ↓
Celebrate  Push?      Who's on?   Unblock  Pull?   (skip)

Script:

"What was completed? [Celebrate]
What's in review? When will it be done?
What's in progress? Any risks?
What's blocked? Let's assign owners.
What should we pull next?"

Focus on flow, not people.

The Yesterday's Commitments Review

High accountability format.

Monday:

Each person: "Today I commit to [specific outcome]."

Tuesday:

"Did I do what I committed to? [Yes/No]
If no, why not? (no judgment, just facts)
Today I commit to [specific outcome]."

Builds discipline and realistic estimation.

The Mob Standup

Entire team works on one thing together (mob programming/design).

Standup becomes:

"What's our shared goal today?"
"What's our approach?"
"Any blockers to mob effectiveness?"
"Who's driving first?"

Rare, but powerful for complex problems.

The Goal-Oriented Standup

Focus on goals, not tasks.

"Sprint goal: Launch user dashboard.

Current status: 70% complete
Biggest risk: Design approval
Today's focus: Frontend integration and testing
Who's blocked? [None]

Let's go."

5-minute standup focused on the goal.

The Pulse Check Standup

For teams in crisis or high stress.

"Before updates, energy check. Scale 1-10, how are you doing?"

[Everyone shows fingers or types number]

"Okay, I see a lot of 4s and 5s. That's rough. What's draining you?"

[Quick discussion]

"Alright, knowing that, let's do quick updates and protect each other's
time today."

Acknowledges the human reality.

Advanced Async Techniques

The Video Standup

Record your standup update as a video.

Benefits:

Async but still personal
See facial expressions and tone
More connection than text
Quick to record (1-2 minutes)

Tools:

Loom
Slack clips
Teams video messages

The Threaded Async

Use threading to organize discussions.

In Slack:

#standup channel:

Alice posts standup update
  ↳ Bob: "Can you share that config file?"
  ↳ Alice: [shares file]
  ↳ Bob: "Got it, thanks!"
  
Sarah posts standup update
  ↳ Carol: "I can help with that blocker."
  ↳ Sarah: "Great! Let's sync at 2pm?"
  ↳ Carol: "👍"

Keeps discussions organized and followable.

The TL;DR

For longer async updates, lead with a summary.

**TL;DR:** API done, starting frontend, no blockers

**Details:**
✅ Yesterday: Completed API endpoints (login, logout, refresh token)
🎯 Today: Start frontend integration, wire up login form
🚫 Blockers: None
💭 Notes: Available for pairing after 2pm

Respect people's time with executive summary.

The Emoji System

Use emojis for quick visual parsing.

✅ = Done
🎯 = Today's focus
🚫 = Blocker
⚠️ = Risk/Warning
💡 = Idea/Suggestion
🙏 = Need help
🎉 = Win/Celebration

Quick visual scanning of updates.

Advanced Metrics

Flow Efficiency

Track: Time working vs. time waiting

Story completion time: 10 days
Actual work time: 3 days
Wait time: 7 days
Flow efficiency: 30%

Surface in standup:

"This story has been in progress for 10 days but only 3 days of actual
work. Where's the wait time coming from?"

Cycle Time by Stage

Track: How long items spend in each stage

To Do → In Progress: avg 1 day (good)
In Progress → In Review: avg 0.5 days (good)
In Review → Done: avg 3 days (bad!)

Surface in standup:

"We have 5 items stuck in review for 3+ days. We need faster code reviews.
Can we commit to 24-hour review SLA?"

Blocker Resolution Time

Track: Time from "I'm blocked" to "I'm unblocked"

Target: < 24 hours
Current: avg 2.5 days

This is a measure of team collaboration effectiveness.

Commitment Accuracy

Track: Do people complete what they commit to?

Commitments made this week: 25
Commitments kept: 18
Accuracy: 72%

Use to improve estimation, not to punish people.

Scaling Techniques

The Tech Lead Sync

For teams too large for one standup.

Team-level standups:

Team A: 5 people, 9:00am
Team B: 5 people, 9:15am
Team C: 6 people, 9:30am

Tech lead sync:

3 tech leads, 10:00am
Cross-team dependencies
Shared blockers
Architecture decisions

The Bus Factor Standup

Rotate who presents each work item.

Instead of:

Alice: "I'm working on the API."

Do:

Bob: "Alice is working on the API. She's 60% done and needs code
     review tomorrow. I can review if needed."

Forces knowledge sharing and reduces key-person dependencies.

The Stakeholder Standup

Separate internal team standup from stakeholder updates.

9:00am - Team standup (team only)

Real collaboration
Honest blockers
Technical details

9:45am - Stakeholder update (once per week)

High-level progress
Risks and mitigations
Strategic direction

Don't mix audiences.

Crisis Mode Standups

The Incident Standup

During production incidents:

Format:

Every 2-4 hours while incident is active
5 minutes max
Only people on incident response

Script:

"Incident status update:

Current status: [Mitigating | Investigating | Monitoring]
Impact: [X users affected, Y revenue lost]
Actions since last update: [What we did]
Actions next: [What we're doing]
ETA to resolution: [Best guess]
Who's doing what: [Assignments]
Blockers: [Escalations needed]

Next standup in 2 hours."

Crisp, tactical, frequent.

The Recovery Standup

After incident is resolved:

"Post-incident standup:

What happened: [Brief summary]
Root cause: [If known]
Immediate actions: [What we did to fix]
Outstanding work: [What's left]
Post-mortem: [When we'll do blameless retro]

Back to normal standups tomorrow. Thanks everyone for the response."

Cultural Techniques

The Vulnerability Moment

Leader shares a struggle.

"Before we start, I want to be honest. I'm struggling with prioritization.
I have too many things and I'm dropping balls. I need to get better at
saying no. If I'm slow to respond to you, that's on me, not you."

Models psychological safety.

Weekly: One person shares something they learned.

Friday standup:
"Before we wrap the week, learning share. Alice, what did you learn
this week?"

Alice: "I learned that our ORM has a batch insert method. It's 10x
       faster than individual inserts. I added it to our docs."

Builds learning culture.

The Gratitude Practice

End week with gratitude.

Friday standup:
"Before we go, quick gratitude round. Name one person who helped you
this week."

[Each person names someone and why]

Builds positive culture and recognition.

The Failure Retrospective

When someone makes a mistake, do a mini-retro in standup.

"John deployed a bug yesterday. Not to shame him, but let's learn.
John, what happened and what can we do to prevent it?"

John: "I didn't test the edge case. Going forward, I'll add that
      scenario to our test checklist."

Team: "Makes sense. Let's all use that checklist."

Learning, not blaming.

Continuous Improvement

The Bi-Weekly Standup Retro

Every 2 weeks:

"Standup retro. 5 minutes.

What's working well?
What's not working?
What should we try?

Vote on one thing to experiment with."

Iterate on your standup format.

The Format Rotation

Try a new format each sprint.

Sprint 1: Round-robin three questions
Sprint 2: Walk the board
Sprint 3: Blockers first
Sprint 4: Yesterday's commitments

After each sprint: "What did we like? What should we keep?"

Find what works for your team through experimentation.

The Standup Health Scorecard

Monthly assessment:

Metric	Target	Actual	Trend
Duration	<10 min	8 min	✅
Attendance	>95%	92%	⚠️
Blockers surfaced/week	>3	2	❌
Blockers resolved <24h	>80%	65%	⚠️
Team value rating	>7/10	8.2/10	✅

Use data to guide improvements.

Mastery Checklist

You're a standup rockstar when you can:

As a Participant

[ ] Prepare your update in advance (60-second prep)
[ ] Deliver update in <2 minutes, bottom-line first
[ ] Surface blockers explicitly and early
[ ] Offer help to teammates proactively
[ ] Ask questions that create value
[ ] Listen actively to all updates
[ ] Follow through on commitments made
[ ] Connect teammates who should talk
[ ] Celebrate others' wins
[ ] Model vulnerability when struggling

As a Facilitator

[ ] Start exactly on time, every time
[ ] Keep energy high throughout
[ ] Enforce time limits without being rude
[ ] Ensure everyone speaks (or explicitly passes)
[ ] Park discussions that don't belong
[ ] Assign owners to every blocker
[ ] End with clear action items
[ ] Track blocker resolution
[ ] Gather and act on feedback
[ ] Adapt format to team's needs

As a Team

[ ] Standup is consistently <15 minutes
[ ] Attendance is >95%
[ ] Multiple blockers surfaced per week
[ ] Blockers resolved within 24 hours
[ ] Natural collaboration happens
[ ] Questions and offers to help are common
[ ] Psychological safety is high
[ ] Team finds it genuinely valuable
[ ] Format evolves with team maturity
[ ] New members integrate quickly

The Ultimate Test

If your standup disappeared tomorrow, would your team recreate it?

If yes: You've mastered standups.

If no: Keep working through this guide.

Key Takeaways

Prepare for standup: 60 seconds of prep makes you 10x more effective
Lead with energy: set the tone for the whole standup
Rotate facilitation: shared ownership builds buy-in
Experiment with formats: find what works for your team
Surface pre-blockers: risks before they become blockers
Proactively help teammates: be the assist
Connect people: bridge gaps in the team
Share learnings: build team capability
Celebrate wins and gratitude: builds positive culture
Continuously improve: measure, feedback, iterate
Use advanced formats when ready: don't force them prematurely
Scale thoughtfully: split large teams, sync leads

Your Path Forward

Week 1-2: Master the Basics

Consistent attendance
2-minute updates
Surface blockers clearly

Week 3-4: Build Habits

60-second prep ritual
Active listening
Offer help proactively

Week 5-8: Advance Communication

Bottom-line first
The handoff
The ask

Week 9-12: Team Dynamics

The assist
The bridge
The celebrate

Month 4+: Continuous Improvement

Experiment with formats
Track metrics
Iterate based on feedback

Final Words

Standups are a tool, not a ritual.

They exist to help your team collaborate, align, and move fast.

When they work:

Problems surface early
Help flows naturally
Trust builds daily
Team performs at its best

When they don't work:

Change them or stop doing them
Process serves people, not the reverse

You now have everything you need to be a fucking rockstar in standups.

Go make your standups exceptional.

Recommended Next Steps

Assess your current standup using the health scorecard
Identify 1-2 improvements to try this week
Get team buy-in by sharing this guide
Experiment with new techniques
Measure results and iterate

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

Articles:

Martin Fowler: "It's Not Just Standing Up"
Jason Yip: "Patterns for Daily Standup Meetings"
Atlassian: "Stand-up Meetings Guide"