Roleplay Scenario
Scenario Overview
There's a major outage, and things are hectic. Multiple services are down because of a failed database migration. Everyone's scrambling, and it's a bit chaotic. Your job is to jump in, assign clear roles, and get everyone working together using tools like Slack and Zoom.
Roles & Setup
Role A – Incident Commander (You)
You're in charge of coordinating the response.
Your goal: Quickly assign roles and keep everyone on track.
Role B – Operations Engineer
You're keeping an eye on system health and alerts.
Your goal: Provide accurate info to guide the response.
Role C – Development Lead
You're focused on the components hit hardest by the migration.
Your goal: Figure out what's wrong and suggest immediate fixes.
Role D – Communications Lead (Optional)
You're handling inquiries from stakeholders and users.
Your goal: Keep everyone informed with clear, concise updates.
Suggested Openers
Incident Commander:
- “Thanks for jumping in. Let’s make sure we know who’s doing what so we don’t step on each other's toes.”
- “Okay, quick regroup. I’ll coordinate, and I need someone on ops, dev, and comms. Let’s use Slack to keep it all organized.”
Operations Engineer:
- “I’m seeing some error spikes. I’ll keep you posted on Slack as I dig in.”
- “Got system health under control. Let me know if you need specific data.”
Development Lead:
- “I’ll check the error logs for [Service X] and see if it’s the migration causing this.”
- “We’re on it. Focusing on recent changes that might be causing issues.”
Communications Lead:
- “I’ll draft a quick update for stakeholders. Let me know when we have more details.”
- “Ready to update once we have clear info. Let’s make sure the message is consistent.”
Sample Roleplay in Action
Incident Commander:
“Thanks for coming together on this. We need clear roles. [Operations Engineer], keep an eye on system health and update us on new alerts in Slack. [Development Lead], focus on the logs for [Service X] and see if the migration is the problem. [Communications Lead], draft a statement for stakeholders, but wait until we know more.”
Operations Engineer:
“Got it. Errors are spiking on the login service and a few others. I’ll keep updates coming in Slack.”
Development Lead:
“Understood. We’ll start with the last deployment to the login service and see what might be causing the issue. Updates will be in the channel.”
Communications Lead:
“Okay, I’ll get a draft ready but won’t send it until we confirm what’s happening. Let’s make sure our updates align with what’s happening.”
Incident Commander:
“Great, let’s check in every 10 minutes. If something urgent comes up, bring it to me. Stay focused, and remember, take a breather if you’re feeling stressed.”
Post-Scenario Tools
Curveball Mode (Optional)
Throw in one of these twists to see how the team adapts:
- Another issue pops up, pulling resources away.
- A stakeholder demands immediate answers, adding pressure.
- Conflicting data reports cause confusion.
Reflection Checklist
As the Incident Commander:
- Did you set clear roles quickly?
- Did you keep communication open and effective?
- Did you manage stress and stay in control?
As a Participant:
- Did you understand and perform your role well?
- Did you communicate clearly and constructively?
- Did you adapt to any new information or challenges?
Common Mistakes to Avoid
- Failing to set clear roles, leading to chaos.
- Overloading team members with too many tasks.
- Letting updates become confusing or disorganized.
Pro Tip
Setting clear roles right from the start helps prevent confusion and keeps the team working efficiently. As things change, be ready to adjust roles to keep everything on track. Also, watch out for stress levels and help keep morale up.