In this episode of The Debrief, we chat with Dennis Henry of Okta about why "how" is a much better question to ask after incidents.
In last week’s episode of The Debrief, we had on Colette Alexander, Director of Engineering at HashiCorp, to discuss some of the myths around incident response.
In that conversation, one of the myths we spoke about was the idea that asking “why” is better than asking “how.” And how, in reality, asking "how" allows you to focus more on the contributing factors that led to an incident happening, whereas “why” tends to single out a person, which can lead to a lot of blame.
For this episode, we’re diving a bit deeper into the reasons “how” is not only better for learning, it’s also better for the psychological safety of your team.
This time around, we’re joined by Dennis Henry who currently works on the Architecture team at Okta. Dennis is a big believer in psychological safety and learning from incidents, so he’s just the person to shed light on this fascinating topic.

Three founders, one kitchen table, and a very honest end of year conversation. In this episode we look back on 2025, from moving continents and growing the company at pace, to ski trips that probably should not have happened, live demos that absolutely could have gone wrong, and the small moments that made the year memorable.

In this episode, CTO Pete and Product Engineer Rory B. discuss how we’re using Claude Code and Git Worktrees to allow engineers to build multiple features in parallel.

In this episode, we chat with Product Engineer Leo about how we’re using AI tools like Claude Code to ship more product, more quickly.
Ready for modern incident management? Book a call with one of our experts today.
