During an Outage, Clear Roles Save Time

Environment and inputs: A tabletop outage scenario, named response roles, a shared timeline and a test alternate communication channel.

When everyone troubleshoots and nobody coordinates, an outage becomes harder to manage. Google’s incident-response framework emphasises coordination, communication, and control. Even a small team benefits from knowing who leads the response, who works on mitigation, and who keeps affected people informed.

What matters

• Name an incident lead to organise work and maintain priorities.
• Keep a shared timeline of observations, changes, and their results.
• Provide updates through a clear communication owner instead of interrupting every responder.

Practical example: During an application outage, one person coordinates recovery while another checks the database and a third updates staff.

One action today: Write down the first response roles and contact method for your most important service.