The latest news from incident.io HQ

Forays in Fancy Formatting

At incident.io, our raison d’etre is making it as easy as possible to handle incidents. So we want to make it as easy as possible to communicate in a rich way in incident summaries and updates.

Behind the curtain: figuring out a gnarly user experience

We recently shipped Configurable Forms which introduced the ability to control the layout and content of your incident forms in a single place. In this post, we’ll take a look behind the curtain at the process we went through to build a really great editing experience for our users.

Engineering nits: Building a Storybook for Slack Block Kit

We care a lot about the pace of shipping at incident.io, and we also build lots of UIs inside Slack. Slack previews lets us collaborate on designing these experiences much more quickly.

They're not kidding about the pace...

Going from 0 to shipping 2 features by the end of my first week

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.