The latest news from incident.io HQ

Your incident declaration form is (probably) too long: The power of concise reporting

Do you have a lot of required fields on your incident declaration form? You may be creating lots of extra work for your responders.

"The dashboard looks broken!": How should data teams respond to incidents?

For data teams, the thought of using an incident management tool feels like an odd fit. But if you look deeper, it just makes sense.

Incident management really can be for everyone

It's time to move past the idea that incident management tools can only be used to respond to incidents—and only by engineering teams.

The price of building your own incident management tool is not what it seems.

Build or buy? An age-old decision that gets made dozens of times a year. It’s quite possibly one of the most important decisions you make as an organization.

Post-incident flows: Bringing consistency to your post incident processes

With Post-incident flows, you can create a checklist of tasks and actions to ensure consistency across your teams and facilitate deeper learning.

A guide to post-mortem meetings and how we run them at incident.io

Post-mortem meetings can play a crucial role in fostering an environment of continuous learning. Here's how we do them!

Whose fault was it anyway? On blameless post-mortems

While blameless post-mortems are a great idea on the surface, if taken to the extreme, they can muddy how much you actually learn from incidents.

Keeping the codebase consistent with Pattern Parties

As a codebase evolves, it’s common to see some divergence in the design patterns within it.

Better learning from incidents: A guide to incident post-mortem documents

Post-mortem documents are a great way to facilitate learning after incidents are resolved.