Roleplay Scenario
Scenario Overview
You're running a daily standup meeting, but the team seems a bit quiet and isn't bringing up any blockers. This could mean potential issues are flying under the radar. Your goal is to encourage an open environment where team members feel comfortable discussing any blockers, fostering a proactive approach to solving problems together.
Roles & Setup
Role A – Standup Facilitator (You)
You're leading the standup and notice the lack of sharing.
Your goal: Encourage openness, uncover any hidden blockers, and promote teamwork in finding solutions.
Role B – Team Member 1
You have a blocker but are a little hesitant to bring it up, worried about being judged.
Your goal: Decide whether to share your blocker based on the facilitator's encouragement.
Role C – Team Member 2
You’re progressing well but notice a potential issue with a dependency that could affect others.
Your goal: Share updates and consider raising the dependency issue if prompted.
Role D – Team Member 3 (Optional)
You’re not facing any issues but are ready to support others.
Your goal: Offer help or suggestions if blockers come up.
Suggested Openers
Standup Facilitator:
- “Hey everyone! Let’s do a quick round of updates. If anything’s slowing you down, feel free to mention it so we can tackle it together.”
- “Blockers are just part of the process—don’t hesitate to share if something’s up. We’re all here to help each other out.”
Team Member 1:
- “I’m making progress, but I’m hitting a wall with [Task]. It’s tricky, and I might need some advice.”
- “No major blockers, but I’m curious if anyone else is having issues with [Feature].”
Team Member 2:
- “Things are going well, but I noticed something strange with our build pipeline. It’s not a problem yet, but it might become one.”
- “I’m moving forward. Just keeping an eye on [Dependency] since it could impact us down the line.”
Team Member 3:
- “No blockers on my end. I’m here to help if anyone needs it.”
- “All good here, but let me know if you need a hand with anything.”
Sample Roleplay in Action
Standup Facilitator:
“Hey team! Let’s get started with updates. If you’re running into any issues, now’s a great time to bring them up so we can deal with them early.”
Team Member 1:
“Well, I’m moving forward, but [Task] is proving a bit tough. Not sure what to do next.”
Standup Facilitator:
“Thanks for sharing. Let’s see if someone has some experience with this or if we can brainstorm a solution together right after this.”
Team Member 2:
“I’m on track, but I spotted something odd with our build pipeline. It hasn’t caused problems yet, but it could.”
Standup Facilitator:
“Good catch. Let’s check it out after the standup. Better to be safe than sorry. Thanks for flagging it.”
Team Member 3:
“All good on my side. Happy to help out with [Task] or look into the pipeline issue.”
Standup Facilitator:
“Awesome. Appreciate everyone being open. Let’s keep this going. If any new blockers pop up, just shout out.”
Post-Scenario Tools
Curveball Mode (Optional)
Introduce one of these mid-roleplay to see how participants adapt:
- A team member reveals a blocker right before the meeting ends.
- A critical dependency suddenly becomes unavailable.
- Another team member expresses concern about workload.
Reflection Checklist
As the Facilitator:
- Did you create an open, supportive environment?
- Did you actively encourage sharing without pressure?
- Did you offer constructive solutions or follow-ups?
As a Team Member:
- Did you feel comfortable sharing updates?
- Did you express any concerns or blockers honestly?
- Did you support colleagues in addressing their challenges?
Common Mistakes to Avoid
- Rushing through updates without encouraging dialogue
- Ignoring subtle cues that indicate hesitance
- Overlooking hints that may suggest larger issues
Pro Tip
Creating a safe space for communication during standups can prevent small issues from escalating. Encouraging transparency and support fosters a more cohesive and effective team.