Introduction: What You’ll Learn
Not every standup is smooth. Sometimes a teammate questions a decision, disagrees with a priority, or raises a concern that could derail the meeting. Your job is to acknowledge the issue without turning the standup into a debate or a status meeting.
You’ll practice:
- Handling pushback calmly and constructively
- Acknowledging concerns without escalating
- Keeping the standup focused
- Deferring deeper discussion to follow-ups
Step-by-Step Simulation
Scene 1: Opening the Standup
Facilitator: "Good morning. Let’s keep it short — just updates, today’s plans, and blockers. I’ll go first."
Facilitator (as a developer): "Yesterday I wrapped up the error logging improvements. Today I’m pairing with Priya on the signup bug. No blockers."
Facilitator: "Thanks. Sara, you’re up."
Scene 2: Teammate Updates with Pushback
Sara: "Still on the export performance work. I’m a little confused why we’re prioritizing this before we fix the auth issues — I thought those were more urgent."
Facilitator: "Thanks, Sara — sounds like there’s some priority confusion. Let’s note that and follow up with Product after this. Anything else for today?"
Sara: "Nope, just heads-down on that."
Facilitator: "Cool, thanks. Alex?"
Alex: "Yesterday I refactored the layout for mobile. Today I’ll do a quick demo for Design. Still waiting on final specs, though."
Facilitator: "Thanks — let’s flag that so we can nudge Design today. Priya, your turn."
Priya: "Actually, I wanted to raise something — we’ve been saying this bug is high priority, but I’ve brought it up in three standups and nothing’s moved."
Facilitator: "Appreciate you bringing it up, Priya. Let’s make sure it gets the attention it deserves — we can sync right after this to clarify what’s blocking it. Anything else for today?"
Priya: "That’s it."
Facilitator: "Thanks. Leo?"
Leo: "Finished the reporting endpoint tests. Starting load tests today. All good here."
Facilitator: "Awesome — thank you."
Scene 3: Wrapping Up and Recap
Facilitator: "Quick recap: Sara raised a priority concern — we’ll follow up with Product. Priya flagged lack of movement on a recurring bug — we’ll sync right after this to dig in. Design specs for Alex are still pending — I’ll check on that today. Great updates, everyone. Appreciate the honesty and clarity."
Mini Roleplay Challenges
Challenge 1: Sara continues pressing about priorities.
- Best Response: “Totally fair concern — let’s set up time to discuss after this so we don’t derail the standup.”
Challenge 2: Priya sounds frustrated.
- Best Response: “Thanks for raising it. Let’s make sure it gets the attention it needs — we’ll talk after this.”
Challenge 3: Another teammate tries to jump in and debate.
- Best Response: “Good discussion — let’s continue after standup so we stay on track.”
Optional Curveball Mode
Try these twists:
- Two teammates start debating what’s more important.
- A teammate questions the team’s overall direction.
- One person refuses to move on until a decision is made.
How do you de-escalate without dismissing?
Reflection Checklist
Standup Flow
- Did I prevent the meeting from becoming a debate?
- Did I redirect without shutting people down?
- Did I take notes and assign follow-ups?
Conflict Navigation
- Did I stay calm under pressure?
- Did I validate concerns appropriately?
- Did I encourage further discussion outside the standup?
Leadership & Tone
- Did I maintain psychological safety?
- Was I steady, fair, and clear?
- Did I help the team stay focused?
Common Mistakes to Avoid
- Dismissing concerns too quickly
- Letting debates hijack the standup
- Ignoring visible frustration or tension
- Not following up on escalated concerns