Chapter 8: Advanced Techniques

The techniques high-performing teams use to make standups exceptional, once the basics are in place.

Beyond the Basics

You have the foundations. Now it is time to go further.

This chapter contains advanced techniques used by high-performing teams. They are not necessary for every team. Use what fits your context.

The Pre-Standup Prep

The best contributors do not wing it. They prepare.

The 60-Second Prep Ritual

Every morning before standup:

1. Look at yesterday's commit or work (10 seconds)

   • What did I actually complete?

2. Check today's tasks (10 seconds)

   • What am I committing to?

3. Scan for blockers (20 seconds)

   • What might stop me?
   • What do I need from others?

4. Identify collaboration opportunities (20 seconds)

   • Who might need my help?
   • Who can help me?

Write a one-sentence update. Practise saying it.

The Team Board Review

2 minutes before standup:

• Scan the work board (Jira, etc.)
• Note bottlenecks or pile-ups
• 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. Standup time."

Energy opening:

"Morning team. Quick wins before we start: we shipped the login
feature yesterday and it has gotten good feedback. Nice work.
Okay, into it."

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 a wheel)
• Reverse alphabetical
• Birthday order
• Who has had the most coffee

Change the questions:

• "What is your biggest win yesterday?"
• "What is 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 are facilitating today. Bob, you are up tomorrow."

New facilitator script:

"Morning everyone, I am facilitating today. 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 to
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 am finishing the feature today."

Hook:

"We are 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 have documented the endpoints in Confluence and I
am 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 has 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 will 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 will 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 do not get it by
EOD today, I am escalating to the design director tomorrow. Just
giving everyone a heads up."

A clear escalation path prevents lingering blockers.

The Workaround

Do not just accept blockers. Find workarounds.

"Blocked on production database access. Workaround: I am 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 am blocked on backend API. Want to swap? I will 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 optimisation."
You:   "I just did something similar last week. Pair after standup."

Do not wait to be asked. Offer help.

The Question

Ask questions that create value.

Surface dependencies:

"John is working on the API, Sarah is 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 is
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

Recognise 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 to-do).

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

Script:

"What was completed? [Celebrate]
What is in review? When will it be done?
What is in progress? Any risks?
What is blocked? 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 judgement, 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 or design).

Standup becomes:

"What is our shared goal today?"
"What is our approach?"
"Any blockers to mob effectiveness?"
"Who is 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 is blocked? [None]

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 to 10, how are you doing?"

[Everyone shows fingers or types a number]

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

[Quick discussion]

"Knowing that, 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 to 2 minutes)

Tools:

• Loom
• Slack clips
• Teams video messages

The Threaded Async

Use threading to organise 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: "Sync at 2pm?"
  ↳ Carol: thumbs-up

Keeps discussions organised 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 an executive summary.

The Symbol System

Use a small set of symbols (or emojis if your team uses them) for quick visual parsing. Keep it consistent.

DONE    Done
TODAY   Today's focus
BLOCK   Blocker
RISK    Risk or warning
IDEA    Idea or suggestion
HELP    Need help
WIN     Win or 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 is 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 a 24-hour review SLA?"

Blocker Resolution Time

Track: time from "I am blocked" to "I am 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 this 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 am working on the API."

Do:

Bob: "Alice is working on the API. She is 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

Do not mix audiences.

Crisis Mode Standups

The Incident Standup

During production incidents:

Format:

• Every 2 to 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  [What we did]
Actions next        [What we are doing]
ETA to resolution   [Best guess]
Who is 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 is left]
Post-mortem         [When we will 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 am struggling with
prioritisation. I have too many things and I am dropping balls.
I need to get better at saying no. If I am slow to respond to you,
that is on me, not you."

Models psychological safety.

The Learning Share

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 is
        10x faster than individual inserts. I added it to our
        docs."

Builds a learning culture.

The Gratitude Practice

End the 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 we should
learn. John, what happened and what can we do to prevent it?"

John: "I did not test the edge case. Going forward, I will add
       that scenario to our test checklist."

Team: "Makes sense. We should all use that checklist."

Learning, not blaming.

Continuous Improvement

The Bi-Weekly Standup Retro

Every 2 weeks:

"Standup retro. 5 minutes.

What is working well?
What is 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:

Use data to guide improvements.

Mastery Checklist

You are a strong standup contributor when you can:

As a Participant

• [ ] Prepare your update in advance (60-second prep)
• [ ] Deliver update in under 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
• [ ] Make sure everyone speaks (or explicitly passes)
• [ ] Park discussions that do not 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 under 15 minutes
• [ ] Attendance is above 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 have the practice down.

If no: keep working through this guide.

Key Takeaways

1. Prepare for standup. 60 seconds of prep makes you 10x more effective
2. Lead with energy. Set the tone for the whole standup
3. Rotate facilitation. Shared ownership builds buy-in
4. Experiment with formats. Find what works for your team
5. Surface pre-blockers. Risks before they become blockers
6. Proactively help teammates. Be the assist
7. Connect people. Bridge gaps in the team
8. Share learnings. Build team capability
9. Celebrate wins and gratitude. Builds positive culture
10. Continuously improve. Measure, feedback, iterate
11. Use advanced formats when ready. Do not force them prematurely
12. 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 do not work:

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

Go make your standups exceptional.

Recommended Next Steps

1. Assess your current standup using the health scorecard
2. Identify 1 to 2 improvements to try this week
3. Get team buy-in by sharing this guide
4. Experiment with new techniques
5. 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"

Tools:

• Geekbot (async standups)
• Standuply (Slack standup bot)
• Range (team check-ins)
• Miro / Mural (visual collaboration)

Where to Go From Here

You have completed the standups course. The next step is practice. Pick one technique from this chapter and try it in your next standup. Get feedback at the end of the week. Pick another the week after.

If you want deeper reading, the books and articles above are the canonical sources. If you want to compare practices, observe a friend's standup at a different company. The shape of the meeting will probably surprise you.