Resources

Large Language Models provide a powerful "sidekick" in resolving incidents. Our talk opens by exploring what LLMs can do when things go wrong: from parsing your codebase to debug, to ad-hoc testing scripts, to brainstorming solutions with engineers. These features ought to be considered by orgs of all sizes. Not only do they reduce the time sink of incidents, they open up that time for feature development, compounding advantages. LLMs aren’t perfect, and their common failure modes are critical when applied to incident response. We’ll cover some of these failures and how they’d look in the context of incident response, including hallucination, misprioritization, and black boxing. This isn’t the end of the world. Orgs just need to weigh these risks versus the speed and convenience of LLM incident response. To mitigate the risk, orgs need to invest in people. We’ll show how the resilience, adaptability, and knowledge of your incident response teams can compensate for the risks of LLMs. Emily Arnott Community Manager at Blameless @emilyarnott8 Emily is the community manager at Blameless, an incident workflow solution. She loves seeking out the cutting edge in how companies stay online. ---- Recorded Sept 21, 2023 at Strange Loop 2023 in St. Louis, MO. https://thestrangeloop.com

Are you an MS Teams shop that wants to level up your incident resolution strategy? Blameless has you covered. Learn all about our MS Teams integration.

Understanding the full scope of incident cost is the first step to reducing it. To do that, were taking a deep dive into the many ways that unchecked engineering incidents hamper your teams success. Join CEO Jim Gochee and COO Ken Gavranovic on September 21st at 10 am PST for a live webinar, as they explore how industry leaders are beginning to measure and mitigate the cost of incidents and poor reliability.

Explore effective incident resolution strategies and processes for streamlined problem-solving and improved operations.

Learn step-by-step strategies for successful zero trust implementation in your organization.

It's always important to retrospect, whether it's the latest outage or the latest sprint. This blog breaks down how to analyze both.

Join COO Ken Gavranovic and author of Architecting For Scale Lee Atchison, August 31th at 10 am PST for a live webinar with as they discuss the blueprint for high-performing engineering teams to maximize the value of retrospectives.

Best practices for clear and timely incident communication. Empower your team with a plan for successful incident response.

Wondering about incident management KPIs? We explain what incident management metrics are, how to track them, and what to do with the information.

Curious about MTTR? We explain what the mean time to recovery is, why it matters to your development team, and how to reduce it.