[mkopinsky]

Can I ask for your (biased) take on something?

My team (5 devs, 10 people total on the product) currently doesn't use any incident response-specific tooling. We have a Confluence SOP for incident response, a page template for RCAs, an #incident-response slack channel, and Zoom but no specific tooling. Just yesterday someone recommended Kintaba/incident.io/OpsGenie/etc, but I don't know if that's overkill for our team.

At what point do you think a tool like yours is necessary or worthwhile, as opposed to using generic tools?

[quartz]

Obviously biased but I definitely think you can get good value out of a tool like Kintaba at your scale (if you're only using it within engineering it would actually have no cost since we're free for 5 or fewer users!).

Kintaba is built to be simple out of the box and allow more depth and complexity as you grow, so initially you might use it the same way you manually use slack today (announce incidents, create a specific incident channel) where your primary initial value is that it makes those motions easier and helps you be more consistent with how you approach incidents and improve recordkeeping, but as you grow you can start to add oncall rotations for your incident roles, automated actions for different incident types, and other things like tagging for better reporting.

Feel free to reach out to us at [e-mail] with questions, or even if you'd just like to chat about how to get up and running!