Webinar ·

Why the Five Whys stop short

  • Ben McBratney

    Head of Incident Strategy at Rootly

  • Steve Mynett

    Guest · Built incident response teams in fintech

This webinar has ended. The recording is coming soon.

About this webinar

In 1912, the Titanic hit an iceberg. Ask why five times and you land on a single root cause, inadequate procedures for ice warnings. Fix that, and you’ve learned almost nothing about why the ship sank, why lifeboats launched half-empty, or why more than 1,500 people died.

Software engineering borrowed Root Cause Analysis and the Five Whys from the factory floor. They hand you a clean answer fast. They also give you a reason to stop looking.

Steve Mynett spent six years building incident response teams in fintech. He joins Ben McBratney to retell the Titanic disaster as an incident investigation and show what a contributing-factors approach finds that root cause misses.

Bring your questions. We’re saving time for Q&A.

Read the blog postThe Titanic didn't sink for just one reason

Next live webinar

Run better retros without automating away the learnings

Tuesday, November 24, 2026 · 2:00 – 2:30 PM EST

Ben McBratney and Kayla Thomson show where AI earns its place in an incident retrospective and where a person still has to do the thinking, so the learning survives the automation.

Register

Your privacy choices

Rootly uses cookies from advertising partners to measure our ads and to show ads for Rootly on other sites. Some US state laws call that selling or sharing personal information. You can opt out of it for this browser here.

Analytics we use to improve this site stay on. Read Rootly's Privacy policy for more information.