The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
When you’re deep into an incident and there’s alerts firing, decisions to be made, and people to escalate to, it’s easy for outward communication with your customers to fall off the priority list. In many regards this makes sense; it seems natural to put all of your focus and energy into minimising the impact and getting things back on track as soon as possible.
In the last two years, we have seen the rise of remote and hybrid work, and with that, a proliferation of tools and apps needed to support critical communication and collaboration. Finding that app-life balance has become increasingly complex, so simplifying “how” we work is key for every organization.
ChatOps has become an integral part of software development and IT operations, as teams rely on automated notifications to take the place of manual alerts. In the past, if there was an alert, someone would need to manually find that notification. Then, they would have contact team members to notify them one by one so they could start working on a resolution. In this complex network of communications, it was easy to lose information, duplicate work, and simply waste time coordinating the team.
Learn about the key roles within an incident response team, as well as optional incident roles you may not have thought about.
