Tolerance for Non-Determinism in AI-Assisted Incident Management?

  • UnStruct AI founder here. We all know that AI can be a double-edged sword. For instance, I've developed a feature (in beta) that suggests tasks/follow-ups based on what people say in Slack. While it offers convenience, it can occasionally become spammy, and during high-pressure moments, might even prove distracting.

    How do you feel about deploying such tools, especially in high-tempo situations like incident management? How do you strike a balance? I'm wondering if these tools might be more appropriate for after-action reviews once the dust has settled?

  • Exciting topic! Many mixed review on AI in general. But it can do some really awesome things in the Incident Management space.

    A great case of AI + IMS is Transposit (I work for them)! Of course AI can get overwhelming and maybe a little noisy at times. We differ by adding a "human-in-the-loop element" which allows you/ your team to have more control over what's automated vs what needs more of a "human touch".

    The gist: Transposit is designed to help with the entire on-call lifecycle. We have AI and automation that helps your on-call engineers triage alerts by bringing context to them. We’ve built an AI-powered, Virtual Incident Commander who identifies key moments for your team and reminds them to communicate status updates (and even writes drafts of them for you!).

    We are also working on new features that use AI to bring important information like 3rd party service outages to your on-call engineers at the right time as well as dynamically identifying the appropriate engineers to bring into an incident to augment your typical escalation process.