March 2024 Summaries

Effective incident communication is crucial for organizations of all sizes. Adrián Moreno Peña, VP of Engineering at SumUp, shares insights on how to communicate during incidents, emphasizing the importance of Status Pages in building trust and maintaining good communications even without a lead.

Today, good incident communication isn't just a nicety, but an absolute must for organizations of all sizes.` `To achieve this, it's essential to understand what it means to communicate during incidents and how Status Pages can help build trust with stakeholders.` `Even without an experienced lead, effective comms is still possible by identifying the right team members to take on responsibilities and leveraging technology to streamline processes.

The text discusses the challenges faced by both executives and incident responders during an incident, highlighting the importance of effective communication to ensure a smooth resolution process. It emphasizes that while responders focus on mitigating the issue, executives want assurance that everything is under control. To bridge this gap, the article suggests proactive communication, setting triggers for executive involvement, designating a communications role, and having an agreed-upon incident response process. Furthermore, it recommends seeking feedback from all levels during post-incident processes to continuously improve the response mechanism. The text concludes by emphasizing that incident management is a team effort involving everyone in the organization.

The text discusses the decision to switch from using Google's common expression language (CEL) to JavaScript for the Catalog importer tool in incident.io. The reason behind this change is that JavaScript is more widely used and understood by developers, making it easier for newcomers to use the tool without losing momentum due to unfamiliar syntax. Additionally, JavaScript offers greater flexibility and consistency with other parts of the product. This decision aims to improve user experience and speed up incident response.

In a recent introduction, Norberto Lopes was appointed as the first VP of Engineering at incident.io. To help familiarize everyone with him, an episode of The Debrief was created to delve into his background and motivations for joining the company. Key points covered include his previous work experience, what inspired him to join incident.io, and a blog post he wrote explaining his decision.

The incident.io On-call app is designed to be as interruptive as possible, ensuring that users are alerted even when in silent mode or during other activities. It aims to provide clarity and calm in high-pressure situations by addressing key questions such as "Is anything on fire?", "Will I definitely get paged?" and more. The app features a card metaphor for representing escalation paths, nudge cards for testing notifications, dark mode by default for alerts, large text style for easy understanding, a timeline showing alert history, and a 'cover me' feature to allow users to ask someone to cover for them temporarily.

In this episode of The Debrief, Jeff Forde, an Architect on the Platform Engineering team at Collectors, shares insights on building effective incident management programs. Key takeaways include understanding why an organization implements such a program and aligning everyone with these goals. Common missteps in incident management are also discussed, including viewing it as a productivity drain and trying to implement an end-to-end program all at once. For startups, establishing a learning culture from incidents can lay the groundwork for continuous improvement. Maintaining a blameless culture is crucial, focusing on understanding actions rather than assigning blame. Lastly, incident management should be tailored to each organization's unique context and needs, with regular feedback sessions and check-ins to ensure continuous improvement.

Incident management is crucial for both small and large organizations. This article discusses different stages of implementing or improving an incident management program. It features Jeff Forde, an Architect on the Platform Engineering team at Collectors, who has experience in developing such programs. The discussion covers actionable advice for organizations looking to enhance their incident management capabilities.