The video explores the difference between incident management and problem management in modern organizations. It describes a common scenario where operations teams focus on immediate fixes, like rebooting systems, without addressing the root causes. Once the immediate issue is resolved, these teams pass the incident report to the developers, who are then responsible for digging deeper to prevent future occurrences.

In this snippet, Alon Levi of WorkOS highlights some of his favorite and most-used incident.io features: follow-ups and Workflows.

In this snippet, Alon Levi, VP of Engineering at WorkOS, talks about how his team has gained the confidence to declare more incidents with incident.io.

In this snippet, Alon Levi, VP of Engineering at WorkOS, talks about how non-technical responders have been able to confidently declare incidents thanks to incident.io's intuitive UI.

In this snippet, Alon Levi, VP of Engineering at WorkOS, talks about the quality of support his team has received from incident.io.

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.

In this video, incident.io co-founder and CPO Chris Evans walks through his blog post "Learning from incidents is not the goal". We cover why he wrote this, his thoughts on the gap between theory and practice, and how people can really learn from incidents.

A overview of how incident.io thinks about incidents, and how they promote learning in a smaller organisation.