What Our Outage Taught Us

Conference talk deck

A nine slide conference talk deck for a thirty minute reliability engineering slot, titled with the claim that the team deleted its own database on purpose. It follows the shape most good talks use: one incident, what the postmortem really found, nine months of deliberate failure drills, a before and after table, then six rules the room can take home.

Every slide, in order

The whole deck as it renders, one slide after another. Read it the way the audience would.

SRE Summit 2026, Track B

We deleted our own database

on purpose

Nine months of failure drills, what broke, and the six rules we kept.

Jonah Petrides

Platform reliability, Cadence Health

22 August 2026

Slide 1 · Cover: the talk title as a provocative claim, the track, the speaker and the date.

1

The outage that started it

Slide 2 · Chapter one divider: an oversized number and a five word title.

The number that got our attention

One Tuesday in November, and the reason this talk exists.

11h 40m

Time to restore

A routine migration dropped a table on the primary. The backup was fine. The restore runbook had never been run by anyone currently employed, and finding that out took eleven hours.

03

Slide 3 · The number that started the talk, 11 hours 40 minutes to restore, and why.

What the postmortem found

The outage was not the database

What we reported

A bad migration

One statement, one missing guard, one table gone. Easy to write up, easy to fix.

What actually cost us eleven hours

1
An untested runbook

Written in 2022, never executed. Three of its steps referenced a tool we had decommissioned.

2
Nobody owned the decision

Four engineers each waited for someone more senior to authorise a restore that any of them could have run.

3
No practice under stress

Everyone knew the theory. Nobody had done it with an incident channel filling up behind them.

04

Slide 4 · What the postmortem found: the reported cause against the three things that actually cost the time.

2

Nine months of deliberate breakage

Slide 5 · Chapter two divider, marking the shift from the outage to the fix.

How we ran the drills

One drill a fortnight, in production hours, with real paging.

1

Pick a failure nobody has practised

Drawn from a list the team writes, not from a vendor catalogue of tidy scenarios.

2

Name one decision maker

Rotates every drill, deliberately including the newest person on the roster.

3

Break it for real

In production, inside a blast radius agreed in advance, during business hours.

4

Measure time to decision

Not time to recovery. The gap before someone acts is where outages actually live.

5

Rewrite the runbook that day

While it still hurts. A drill that does not change a document was a fire drill, not a test.

06

Slide 6 · How the drills ran: five numbered steps, one drill a fortnight, in production hours.

What nine months changed

Same team, same systems, measured on real incidents.

Measure

Before drills

After drills

Change

Time to first action

46 min

7 min

-85%

Median restore time

4h 10m

38 min

-85%

Runbooks executed

2

19

+17

Engineers who can restore

3

14

+11

Paging escalations

61%

18%

-43pt

Postmortem actions closed

44%

92%

+48pt

Twelve months to November 2025
Nine months to August 2026

07

Slide 7 · Before and after: six measures with the change in a third column.

Take these home

Six rules that survived every drill

1

Practise in production

2

Name one decider

3

Time the decision

4

Rewrite it that day

5

Rotate the newest in

6

Never drill silently

08

Slide 8 · Take these home: six rules as short chips, sized to photograph from the back row.

Break something on purpose this month

Our drill templates and the rewritten runbooks are public. Take them, they cost us eleven hours.

Speaker

Jonah Petrides

Email

jonah@cadence.example

Slides

cadence.example/drills

09

Slide 9 · Close: the call to action, the public drill templates and the speaker's details.

What makes this deck work

The hook is the title

The cover says the team deleted its own database on purpose, which is more alarming and more specific than a session called lessons from an outage. Chris Anderson of TED advises opening with the story that earns attention, and this deck puts that story on the first slide.

Dividers give the talk shape

Two chapter slides split the talk into the outage and the fix, each just a huge number and a short title. The audience always knows how far through they are, and the speaker gets a natural pause before the drill slides.

Takeaways fit on one screen

Slide seven shows time to first action falling from 46 minutes to 7 and median restore from over four hours to 38 minutes. The six chips on slide eight only get photographed because the evidence has already been shown, and slide four models the blameless postmortem from Google's SRE book by looking past the bad migration to the untested runbook.

Questions people ask

How many slides for a 30 minute talk?

Eight to twelve if the slides carry big ideas rather than notes. This example uses nine for a thirty minute slot: two of them are chapter dividers, one is a single number, and the rest hold the postmortem, the drill method, the results table and the takeaways. That works out at three or four minutes a slide, with the speaker, not the screen, doing the explaining.

Should conference slides have lots of text?

No. Each slide here makes one point that can be read from the back of the room: 11h 40m on slide three, five drill steps on slide six, six rules of three or four words on slide eight. The story of the outage, including why four engineers waited for permission, belongs in what the speaker says, not on the screen.

Do I need section dividers?

For anything over fifteen minutes they help. This talk has two, one before the outage and one before the fix, each just a large number and a short title. They mark the turn from problem to method, give the audience a sense of how far through they are, and give the speaker a natural pause for water before the drill slides.

Can I export this to PowerPoint for the venue?

Yes, on a paid plan: the deck exports as PowerPoint or as editable PPTX with native text boxes. PDF export costs about 1 credit per 10 slides, but it places each slide as an image, so the text is not selectable. Bring the PDF as a backup on a USB stick, and check the venue's screen ratio, because the slides are built at 1920 by 1080.

How should a conference talk open?

With the claim, not the agenda. The cover here is the assertion that the team deleted its own database on purpose, then a chapter divider, then the single number the talk is built on, eleven hours and forty minutes to restore. Three slides in, the room knows what is being argued and why it should stay.

What should a before and after table in a talk compare?

Measures the audience already tracks, with the change in its own column. This deck compares six of them across the nine months of drills, so the claim in the title can be checked rather than believed. Tables in the builder hold up to twenty rows and eight columns, which is far more than a talk slide should ever use.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other presentation examples

Want the steps in the builder? Read Make a pitch presentation with AI, then Export a presentation to PowerPoint or PDF. For everything this generator can do, see the presentation maker.

Sources

Written and checked by the OneCraft team. Last checked .