Imagine an AI assistant that could automatically surface a whole host of useful incident response data points with just a prompt. Well, you won't need to imagine for much longer. That's exactly what we built in Assistant, one of our newest features powered by AI. In this episode, you'll hear from Charlie, the project lead for Assistant, to get a peek behind this game-changing product. You'll hear him chat about: What went into building Assistant What the project timelines were What were some of the challenges the team faced What was it like learning the ropes of prompt engineering while building out Assistant ...and a lot more You can listen to our ⁠AI announcement episode here⁠ and our previous ⁠episode on Suggested Summaries here⁠. Read our blog about Assistant.

Incident summaries are the source of truth for responders joining an incident at any point. But the reality is that with so many things happening at once—like needing to respond to the actual incident—updating these summaries as things play out can fall by the wayside. Enter, Suggested Summaries, one of our newest features powered by AI. In this episode, you'll hear from Milly, the project lead for Suggested Summaries, to get a peek behind the curtain. You'll hear her chat about: What went into building Suggested Summaries What the project timelines were What were some of the challenges the team faced What was it like learning the ropes of prompt engineering while building out Suggested Summaries ...and a lot more You can listen to our AI announcement episode here and our previous episode on Related Incidents here.

For financial services companies, good incident management is absolutely critical—maybe more so than in other industries. So, for Michael Cullum and his team at Bud Financial, the choice to build an incident response tool felt right for them in the moment. But very quickly, Michael and the team came face-to-face with the myriad limitations that come with building your own response tooling. Soon after, they would adopt incident.io to replace that internal Slackbot and save money, resources, and headaches in the end. The end result? A total transformation of the way they managed incidents. In this conversation, Chris Evans, CPO of incident.io, sits down with Michael to chat through this journey. Read more about Michael's buying decision: https://incident.io/customers/bud

Recently we went live with one of our biggest product launches to date AI. And this product was unique in that it was broken up into four smaller projects: Related incidents Suggested summaries Suggested follow-ups Assistant So naturally most folks might be wondering: What were the biggest differences between these projects and what went into actually building out each of these features? In this episode, you'll hear from Rob and Isaac, both Product Engineers who played a really critical role in the building out of related incidents, to get a peek behind the curtain. You'll hear them chat about: What went into building related incidents What their project timelines were What were some of the challenges they faced What was it like learning the ropes of prompt engineering while building out related incidents ...and a lot more As an aside, if you want to learn more about each of these features, we're releasing four mini-episodes diving into each of them.

This week was a particularly exciting one for us at incident.io. We launched not one, not two, but four AI-powered features to help folks get the most out of their incidents. Assistant Suggested summaries Suggested follow-ups Related incidents In this episode of The Debrief, we sit down with Ed Dean, Product Analyst, and Charlie Revett, Product Engineer, to talk through all of these features and explain how they're already making an impact. We discuss: How we made sure to balance autonomy with AI Why we decided to build these features and why now What it was like working with design partners throughout this process What it was like learning prompt engineering while simultaneously building a product rooted in the practice ...and much more You can learn more about our AI features here: https://incident.io/ai

What a year 2023 was at incident.io! While it's hard to summarize 365 days, a few things stand out: We launched a bunch of new products like Catalog and Status Pages. We hired a ton and we're now sitting at nearly 80 employees as of December 2023. We expanded into the U S opening up a brand new office just a few weeks ago. ...and there's still so much more ahead of us So as we close the curtain on 2023, we sat down with the three co-founders of incident.io to do a bit of reflection on the wild ride that was this year. In this episode you'll hear them discuss challenges, big wins, moments of growth, what's next for us, and most importantly, what the three co-founders like most about one another. Read our year-end blog post here: https://incident.io/blog/reflecting-on-a-momentous-2023

If you're on a data team, have you ever considered using an incident management tool to respond to pipeline issues? If the answer is no, then you might want to check out this episode. Here, we chat with Jack, Data Analyst at incident.io, to better understand why data teams can—and should—look to incident management tools like incident.io to manage issues. We chat about: Why there's a big push for data teams to adopt the practices of engineering teams—from tools to processes Why incident management tools aren't just for engineers How an incident management tool like incident.io can transform the way you respond to things like pipeline issues ...and much more Read Jack's blog post about incident management for data teams here: https://incident.io/blog/incident-management-for-data-teams

At incident.io, we like to push the pace to deliver feature requests and bug fixes quickly. What's one of the things that helps us move with pace? The Product Responder role. In this episode, we sit down with Sam Starling, Product Engineer, to talk about this crucial role and how it, ultimately, gives us an upper hand. We chat about: How the role came about What responsibilities the role has What Sam's week as a Product Responder looked like ...and more Read more about the Product Responder here: https://incident.io/blog/how-we-leverage-our-product-responder-role

Join Lisa Karlin Curtis, Tech Lead at incident.io, as she shares her expertise on how to make meetings effective. Dive into actionable strategies to improve meeting quality, focusing on preparation and structure. Lisa highlights the importance of empathy and emotional needs in workplace interactions. Discover innovative approaches to rethink meetings, especially in a remote world, advocating for fewer but more productive gatherings. With anecdotes of both chaotic and successful meetings, she emphasizes the balance of preparation and engagement for optimal outcomes.

Dimitra, a product engineer behind the new Status Pages project, shares her insights on the challenges and triumphs of launching this significant tool for system transparency. She highlights the importance of collaboration within cross-functional teams and the value of user feedback in creating a product that truly resonates with users. Dimitra also discusses innovative practices like 'polished parties' for refining user flows, revealing how teamwork dynamics can elevate project outcomes and enhance customer satisfaction.