The Debrief by incident.io

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.

In this episode, we chat with Alicia Collymore, Engineering Manager at incident.io, about advice she'd give EM's to be successful in their roles.

In this week's episode, we're joined by Matt Huxtable, CTO at Ziglu (an e-money issuer, offering a variety of digital finance services, particularly well known for its cryptocurrency services). Matt talks about how the engineering team at Ziglu has evolved over time, building an agile culture and why "keep it boring" is his mantra. Chris, Pete and Matt cover how to context switch between solving and communicating during an incident, their most creative incident fixes and why AI isn't ready to solve incidents for us just yet. In this episode we cover: [01:20] Introducing Matt and Ziglu [05:45] The evolution of the team at Ziglu [09:45] Horizontal career growth in Engineering [12:15] Finding an incident solution at Ziglu [18:00] Balancing fixing with communicating during an incident [20:26] Could AI help you solve incidents? [27:00] Matt’s most creative incident fix For more information, head over to incident.io/blog/podcast

In this episode, Pete and Lisa discuss why great communication is essential to the success of any incident management process. From keeping your wider team in the loop to minimise disruption, to using customer communication to strengthen your brand when things go wrong, the team share their experiences and top tips for having a transparent incident communication culture. In this episode we cover: [01:10] Why is communication so important? [07:30] Practical advice on building a good internal communication culture [15:20] The cultural challenges of incident transparency [25:30] Building trust with customer communications For more information, head over to https://incident.io/blog/podcast

In this podcast, the three incident.io co-founders Stephen, Chris and Pete take a trip down memory lane, revisiting the story of how they came to found incident.io and the major milestones of the first 12 months in business. Key topics/timestamps: [01:36] The origins of incident.io [07:00] Building Response at Monzo [17:00] The side hustle begins [22:00] The first demo [27:00] The first off-site [34:00] Moving into the old fire station [41:00] Hiring a team [47:00] What next? For more information, head over to https://incident.io/blog/podcast