Afleveringen
-
In last weekâs episode of The Debrief, we had on Colette Alexander, Director of Engineering at HashiCorp, to discuss some of the myths around incident response.
In that conversation, one of the myths we spoke about was the idea that asking âwhyâ is better than asking âhow.â And how, in reality, asking "how" allows you to focus more on the contributing factors that led to an incident happening, whereas âwhyâ tends to single out a person, which can lead to a lot of blame.
For this episode, weâre diving a bit deeper into the reasons âhowâ is not only better for learning, itâs also better for the psychological safety of your team.
This time around, weâre joined by Dennis Henry who currently works on the Architecture team at Okta. Dennis is a big believer in psychological safety and learning from incidents, so heâs just the person to shed light on this fascinating topic.
-
What if we told you that everything you thought you knew about incident response was wrong.
Well, at least some of it.
That some of the things youâve been doing for years might not actually be having the impact you thought they did. Or, even worse, that some of the assumptions youâve been making have actually been having a negative impact on you, your team and your organization.
This week, weâre talking about myths around incident response. And who better to dispel some of these myths than Director of Engineering at HashiCorp, Colette Alexander.
We chat about myths around learning and process, why âwhyâ is the wrong question to be asking after incidents, and why documenting risk doesnât necessarily help you manage them.
-
Zijn er afleveringen die ontbreken?
-
Whether youâre a seasoned company with 10+ years of operations, or a startup thatâs just getting off the ground, making sure you have a good culture of engineering is really important.
Not only will this have a significant impact on the folks on your team, itâll make a big difference with hiring.
When everyone knows that your company is the place to be when it comes to culture, attracting really good talent becomes that much easier.
But I was curious, what do some of the folks at incident.io think about engineering culture in general and how to best build it? Better yet, what about the engineering culture at incident.io? Whatâs it like?
To answer all of these questions and more, I sat down with Lisa Karlin Curtis, Tech Lead, and Alicia Collymore, Engineering Manager, to get their perspectives on this incredibly important topic.
We chat about what âcultureâ even means, why diversity is important, how teams can make sure their engineers feel empowered to share their perspectives and a whole lot more.
-
Q1 2024 is officially behind us.
So we figured that it was a great time for a bit of reflection on the exciting start to the year. In this episode, we sit down with our founders, Stephen, Chris, and Pete, to get a bit of perspective on how the last three months played out.
We chat about On-call, our AI launch, and the hundreds of other features, bug fixes, and bits of polish and delight that we've shipped over the last 12 weeks.
We also chat about the state of the company as a whole, our growth, and ultimately what's on the horizon.
-
Today, good incident communication isn't a nice to haveâit's an absolute must.
But where do you even start? To help answer that question, we sat down with the VP of Engineering at SumUp, Adriån Moreno Peña, to get his perspective on how organizations of all sizes can share stellar comms no matter the situation. We discuss:
What it means to communicate during incidents Why Status Pages are critical in helping to build trust How you can have good comms even without a lead ...and much more -
Recently, we introduced our very first VP of Engineering, Norberto Lopes, to incident.io. As with all of our new joiners, we thought it would be helpful for folks to get acquainted with who exactly he is!
So in this episode of The Debrief, we'll do exactly that.
We sat down with Norberto to ask about his background, what he was doing before incident.io, what motivated him to join the company, and a whole lot more.
If you wanted an opportunity to get to know our VP of Engineering a bit more behind the scenes, then this is the episode for you.
Read Norberto's blog post explaining why he joined incident.io: https://incident.io/blog/why-i-joined-incident-io
-
Today, incident management is a core part of organizations, both big and small.
But what if you don't have an established incident management program, where do you start? Or what if you already have a program, but you're looking to optimize it a bit? Where do you start in that case?
Consider another situation: What if you're an established organization with years of incident management experienceâwhat are some things that you can do to take things to the next level?
To talk through all of these scenarios and more, we sat down with Jeff Forde, Architect on the Platform Engineering team at Collectors.
Jeff has been a part of organizations at each of these phases, playing a key role in developing the incident management programs those organizations have today.
If you're looking for actionable advice on how to level up your incident management, then this is the episode for you.
-
This is on-call as it should be.
The secret's out. The world can finally know.
incident.io On-call is here.
Naturally, a lot of you may be wondering: why and why now. So to help answer those questions, we sat down with Chris and Pete, two of our co-founders here at incident.io to get a bit of background on this project:
What exactly went into it? What were we hoping to solve for? How are we addressing the pain points around being on call? And most importantly, how are we stacking up against the incumbents in our space?This episode will not only get you excited about this huge week, it'll get you pumped for what's ahead for on-call.
Learn more about on-call here: https://incident.io/oncall
-
Noting follow-up actions is really important at the end of the incident response process. The problem is that it can be really easy to overlook certain actions or forget to do them entirely.
With Suggested Follow-ups, this is now a thing of the past.
In this episode, you'll hear from Rob, the project lead for our latest Suggested Follow-ups feature, to get a peek behind the curtain. You'll hear him chat about:
What went into building Suggested Follow-ups What the project timelines were What were some of the challenges the team faced ...and a lot moreYou can listen to our â AI announcement episode hereâ . Here are the rest of our AI episodes:
Related Incidents Suggested Summaries Assistant -
For a lot of teams, incident management can be a bit of a headache.
It's stressful. It's not optimized. The whole process can feel like it's being held together with tape. Worst of all? Responders are the ones feeling the brunt of it. But in reality, your customers are, too. Think about it:
Incidents are running longer than they should Follow-up actions to prevent similar incidents in the future aren't being followed through with Learning from incidents doesn't happen at all due to the lack of documentation ..and the list does go on and onBut honestly, the situation doesn't even have to be so dire. Things can be, generally speaking, totally fine. But you recognize that there are some things that you can do to make incident response really shine at your organization.
So if you're finding yourself looking for a better way, we've got you covered.
In this episode, you'll hear from two folks who have years of combined experience responding to incidents: Kerim, a Senior Developer Advocate at HashiCorp, and Lawrence, a Product Engineer here at incident.io.
The topic of our conversation? How to make incidents less painful. They discuss:
The first incident they experienced that made them realize the value of a good incident response process Why teams aren't prioritizing incident response What the value of responding to incidents is What a good incident response process looks like ...and more -
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 moreYou 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 moreYou 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 AssistantSo 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 moreAs 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 incidentsIn 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 moreYou 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 usSo 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 moreRead 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
-
In this interview, we chat with Lisa Karlin Curtis, Tech Lead at incident.io, about running meetings that, well, don't suck. In it, she gives actionable advice for running your own meetings, emphasizes why empathy in the workplace is important, reflects back on bad meetings she's run, and more.
Read Lisa's blog post here: https://incident.io/blog/how-to-run-meetings-that-dont-suck
-
Earlier this year, we launched our Status Pages product. In this episode, we chat with one of the product engineers on that project, Dimitra, about how that launch went. We discuss:
What it was like working on such a big project What the team learned What it was like collaborating cross-functionally...and more
Read more about Status Pages here: https://incident.io/status-pages
Read Dimitra's post here: https://incident.io/blog/achieving-pixel-perfect-polish
- Laat meer zien