Chris explains his thoughts on the theory of learning from incidents, and why work needs to be done to close the gap and help folks actually trying to get their job done.

Taken from our a full debrief on "Learning from incidents is not the goal", Chris walks through MTTR, the justifiable bad rap it has, and his thoughts on it as a measure.

In this video, Chris shares his thoughts on the difference between active learning: writing and sharing debriefs, meeting to walk through an incident, etc., and passive learning: running incidents in the open, dynamic collaboration, reviewing past incidents.

The incident.io Catalog is a connected, navigable, map of "things" that exist in your organization. We can use it to describe an organization as a connected graph, and use that graph to drive powerful workflow automations during incidents. In this hands-on training session, we'll work through an example of building a catalog for a mock organization. We'll then use the catalog to solve some real business problems, including automated incident data attribution, and some realistic workflows which outline how it works and what it enables in the context of incident management.

In this week's episode, we're joined by Matt Huxtable, CTO at Ziglu (an e-money issuer, offering a variety of digital finance services, particularly well known for its cryptocurrency services). Matt talks about how the engineering team at Ziglu has evolved over time, building an agile culture and why "keep it boring" is his mantra. Chris, Pete and Matt cover how to context switch between solving and communicating during an incident, their most creative incident fixes and why AI isn't ready to solve incidents for us just yet.

In this episode, Pete and Lisa discuss why great communication is essential to the success of any incident management process. From keeping your wider team in the loop to minimise disruption, to using customer communication to strengthen your brand when things go wrong, the team share their experiences and top tips for having a transparent incident communication culture.

In this podcast, the three incident.io co-founders Stephen, Chris and Pete take a trip down memory lane, revisiting the story of how they came to found incident.io and the major milestones of the first 12 months in business. Key topics/timestamps.

In this podcast, our panellists discuss the foundations that any team needs to put in place when designing their incident management process. Starting from the basics of defining what we really mean by an incident, to how to set your severity levels, roles and statuses, Chris and Pete share their tips for building solid foundations to run your incidents.

In this podcast, our panellists discuss what it means to build a successful on-call team. Drawing on their experiences at fast growing start-ups and scale-ups, incident.io co-founders Pete and Chris cover everything from who should be on the rota and how to build a compassionate on-call culture, to compensation structures and tips for operationalising on-call.

incident.io is helps global technology companies to rapidly resolve and learn from incidents. Find out how in this video.