3 exercises — practise the high-stakes verbal phrases used during live P1 incident calls.
0 / 3 completed
1 / 3
Your team has just joined the incident bridge call. The Incident Commander has not been declared yet. Which statement correctly assigns the role?
Option B establishes control clearly and immediately. An effective IC declaration:
• Announces the assumption of the IC role — no ambiguity about who is driving • Assigns the Comms Lead — one person owns external/internal status updates • Addresses SMEs — sets expectations without micromanaging • Manages the call — asks non-essential listeners to mute
Standard bridge roles: • IC (Incident Commander) — drives the call, makes decisions, is the single source of authority • Comms Lead — posts status updates (Slack, status page, email), talks to customers • SME (Subject Matter Expert) — database, infra, app layer experts who answer technical questions • Scribe — logs the timeline in real-time
Ambiguous starts waste critical minutes. The IC must be declared before any technical discussion begins.
2 / 3
During a bridge call, the database load is still climbing and nothing is working. Which statement correctly calls a rollback?
Option C is the professional standard for declaring a rollback on a bridge call. It contains every required element:
• "I'm calling a rollback" — explicit, unambiguous decision (not a suggestion, not a question) • Target build specified — "to build 2024.01.10a" — everyone knows the target state • ETA given — "8 minutes to stable" — sets expectations for the call and for the Comms Lead • Scribe instruction — timestamp the event for the incident timeline • Comms instruction — update the status page/Slack immediately
A rollback on a P1 bridge call is a high-stakes, time-sensitive decision. The IC calls it — not asks for consensus. Phrases like "maybe we should think about" or "what does everyone think" waste time and dilute authority. Saying "someone roll it back" without a target build or ETA creates confusion.
3 / 3
After 47 minutes of P1 incident work, all services are responding normally. Which message correctly declares resolution on the bridge call?
Option C is the complete all-clear. A proper resolution declaration on the bridge includes:
• Evidence of recovery — "monitoring is green, error rate back to baseline at 0.04%" — not just "looks good" • Explicit resolution declaration — "I am declaring this incident resolved" — unambiguous close • UTC timestamp — "at 16:19 UTC" — logged for MTTR calculation and the post-mortem • Comms Lead instruction — update the status page and Slack officially • Scribe instruction — close the incident timeline • Acknowledgement — thank the team (important for morale) • Post-mortem commitment — schedule it immediately while details are fresh
The incident is not "resolved" until the IC declares it resolved with evidence. Fuzzy language ("we're probably fine", "I think it's up") leaves the team in a grey zone and makes MTTR calculation and the post-mortem harder.