WEBVTT

1.1
00:00:00.000 --> 00:00:10.000
<v Speaker 1>Welcome to our major incident drill. Think of it as a fire drill for IT—everyone needs to know their part before the real emergency hits.

1.2
00:00:10.000 --> 00:00:20.400
<v Speaker 2>We'll walk through a simulated outage so you can practice the motions without the adrenaline spike. The goal is to stay calm and restore service swiftly.

2.1
00:00:20.400 --> 00:00:32.800
<v Speaker 2>A major incident is more than a glitch. It affects core services and usually drags multiple teams into the fight. Picture the checkout system rejecting every payment during a sale—that's major.

2.2
00:00:32.800 --> 00:00:40.800
<v Speaker 1>When you see widespread impact or a breached SLA on the horizon, escalate it and rally the right experts immediately.

3.1
00:00:40.800 --> 00:00:52.000
<v Speaker 1>Example scenario focuses attention on a concrete part of the work. Checkout system fails across all regions, Users can't complete purchases, and Mobilize database, network and app teams.

3.2
00:00:52.000 --> 00:01:05.600
<v Speaker 2>In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Users can't complete purchases; Mobilize database, network and app teams.

4.1
00:01:05.600 --> 00:01:26.000
<v Speaker 1>Let's map the checkout flow so everyone knows where problems can start. The web front end hits an API gateway, which then fans out to microservices for payments, inventory, and orders. Those services talk to a clustered database and ping the payment provider over the internet. Monitoring agents watch each step.

5.1
00:01:26.000 --> 00:01:52.800
<v Speaker 2>A failure anywhere in that chain kicks off a big response. The incident commander coordinates efforts and sets priorities. A communications lead keeps executives and customers in the loop. Front-end and backend engineers dig into code issues. Database admins check queries and replication. Network ops verify connectivity and DNS. A liaison talks to the payment provider. Finally, the service desk fields user reports and keeps them updated.

6.1
00:01:52.800 --> 00:02:02.400
<v Speaker 1>During the drill, assign each role quickly and follow the runbook. The incident commander leads, comms handles updates, and a scribe logs every step.

6.2
00:02:02.400 --> 00:02:10.400
<v Speaker 2>Treat it as the real thing—no shortcuts. The more accurately you rehearse, the smoother an actual outage will play out.

7.1
00:02:10.400 --> 00:02:17.200
<v Speaker 2>Once the dust settles, gather the team to review what happened. Share successes, missteps, and any surprises.

7.2
00:02:17.200 --> 00:02:24.000
<v Speaker 1>Update the playbook based on those lessons and book another drill. Practice turns panic into muscle memory.