Chris Evans's posts

The EU AI Act and what it means for managing incidents

Something

How incident.io helps to reduce alert noise

By linking alerts to real incidents, incident.io gives you full visibility into what’s noisy, what’s painful, and what needs fixing.

Introducing Agentic CTO: executive oversight in every incident

At incident.io, we've always focused on empowering your team to manage incidents calmly, confidently, and effectively. Today, we’re introducing a powerful new addition to our suite of AI incident responders — one designed to bring a new layer of strategic oversight to your engineering organization: Agentic CTO.

Going beyond MTTx and measuring “good” incident management

What does "good" incident management look like? MTTx metrics track speed, but speed alone doesn’t mean success. So, we decided to analyze 100,000+ incident from companies of all sizes to identify a set of new benchmarks for every stage of the incident lifecycle.

A seven-step framework for running incident debriefs

​Ever felt that post-incident debriefs are more of a chore than a chance to improve? At incident.io, we've transformed these sessions into engaging, insightful discussions. Our structured, blameless framework helps teams extract actionable lessons from incidents, turning challenges into opportunities for growth.

Overhauling PagerDuty’s data model: a better way to route alerts

PagerDuty has long been the go-to solution for reliable on-call management, but its aging data model and lack of innovation have become a challenge. In this post we explore how incident.io On-call offers a better, more flexible approach to alert routing and provide practical advice on how to migrate smoothly from PagerDuty.