# postmortem Published articles for postmortem. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Pollen tried to remove my article about CEO Callum Negus-Fancey and CTO Bradley Wright, and Google is assisting with it DevFeed: [Pollen tried to remove my article about CEO Callum Negus-Fancey and CTO Bradley Wright, and Google is assisting with it]() Original publisher: [Read original article]() Author: Gergely Orosz Published: 2026-06-28T00:40:25Z Content type: article Language: en Sources: [The Pragmatic Engineer]() Topics: [Google](), [Software Engineering](), [atlassian](), [jira]() Tags: [article](), [atlassian](), [engineering](), [google](), [jira](), [postmortem](), [software-engineering]() ### AI overview The article recounts the collapse of events technology company Pollen, including layoffs, unpaid wages and contributions, unpaid vendors, bankruptcy, and an unresolved customer double charge. It then describes Google removing the author's article from search results after a copyright infringement claim, which the author says they appealed. ### Source excerpt In 2022, I wrote about the damning fall of events tech company Pollen. The short of it: Pollen seemed to have pulled off the improbable feat of building a business in the notoriously low margin industry of events, surviving Covid-19, and building a solid software engineering organization. In April ## Five rules for running an incident DevFeed: [Five rules for running an incident]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-05-27T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [incident](), [Learning]() Tags: [customer-experience](), [incident](), [incident-management](), [on-call](), [outage](), [postmortem](), [production](), [recovery](), [reliability](), [root-cause-analysis](), [rules](), [signal](), [speed](), [sre](), [team]() ### AI overview This opinion article presents five rules for handling production incidents: assess severity by customer impact, use an Incident Commander, mitigate before investigating root cause, maintain regular communication, and use postmortems for learning and accountable follow-up. ### Source excerpt The difference between a 10-minute incident and a 3-hour outage is rarely technical. Five things I wish every on-call team locked in before their first big page. ## How to run postmortems effectively? DevFeed: [How to run postmortems effectively?]() Original publisher: [Read original article]() Author: Peter Bergman Published: 2024-09-17T08:49:33Z Content type: tutorial Language: en Sources: [Volvo Cars Engineering - Medium]() Topics: [incident](), [systems](), [context]() Tags: [blameless-culture](), [errors](), [how-to](), [incident](), [mistakes](), [organization](), [outages](), [postmortem](), [postmortem-documentation](), [postmortem-report](), [processes](), [retrospective](), [retrospectives](), [software-development](), [systems](), [teams]() ### AI overview This article explains how to conduct effective, blameless postmortems after incidents such as outages, production bugs, or service disruptions. It emphasizes identifying root causes, examining systemic factors and context, and improving processes rather than assigning individual blame. ### Source excerpt Incidents are inevitable. As we all know, system outages, bugs in production, or service disruptions, can all have significant impacts. When that happens, the company pays the price. It's better to see it as a chance to learn instead of pointing fingers. This is where postmortems come into play. A postmortem, also referred to as an incident analysis, or retrospective, is a vital practice for understanding what went wrong, why it happened, and how to avoid such occurrences in the future. Understanding postmortemsWhat is a postmortem and why is it important? An incident postmortem is a review process carried out after an incident. Its purpose is to determine the root causes and identify strategies to avoid similar future incidents. What does blameless mean? In a blameless postmortem, the emphasis is on learning from mistakes and improving processes, rather than pointing fingers. By focusing on systems, components, roles, processes, procedures, and not individuals, we can foster a blameless culture where teams feel safe to openly discuss incidents and contribute to meaningful solutions. The aim here is to reframe the discussion to focus on the systemic factors that contributed to the incident which let teams uncover deeper insights and implement more effective solutions. What about the human factor? Even though many incidents can be attributed to being caused one way or the other by humans, due to the human factor, so to speak, it is important that we aim to shift the conversation towards understanding the "second stories" behind the incident. The "first story" of human error focuses on individual mistakes, while the "second story" examines the systemic factors contributing to errors. To do so, we focus on the underlying factors and context that may not be immediately apparent. Through the use of "second stories", human error is seen as the effect of systemic vulnerabilities deeper inside the organization. If we assume that all actions are made in good faith, then what ## Postmortem: Removing all users from github.com/trivago DevFeed: [Postmortem: Removing all users from github.com/trivago]() Original publisher: [Read original article]() Author: Andy Grunwald Follow Published: 2021-10-05T00:00:00Z Content type: opinion Language: en Sources: [Trivago]() Topics: [GitHub](), [incident](), [Post Mortem](), [Entra ID](), [pull-requests](), [ci](), [Deployment]() Tags: [azure](), [bugs](), [culture](), [engineering](), [engineering-culture](), [github](), [incident](), [mistakes](), [post-mortem](), [postmortem](), [processes](), [pull-requests](), [retrospective](), [slack](), [systems]() ### AI overview This blameless postmortem explains how trivago's automatic synchronization between GitHub and Azure Active Directory removed all synced user accounts from the company's GitHub organization. The root cause was deletion of the Azure Active Directory security group controlling access. The group was restored, users were reinvited, and the incident lasted 1 hour and 19 minutes. ### Source excerpt While engineering, we fix bugs, create new systems, build workflows and establish processes. Our job is to change things. Changing things can involve mistakes that ultimately lead to the failure... ## Localytics' Process for Responding to Service Incidents DevFeed: [Localytics' Process for Responding to Service Incidents]() Original publisher: [Read original article]() Author: Tony Wieczorek Published: 2016-09-13T18:24:39Z Content type: article Language: en Sources: [Localytics]() Topics: [incident](), [systems](), [Slack](), [realtime]() Tags: [downtime](), [engineering](), [incident](), [pagerduty](), [postmortem](), [realtime](), [slack](), [systems]() ### AI overview Localytics describes its process for responding to service degradations and downtime. The process uses Slack and PagerDuty to coordinate triage, debugging, incident follow-up, postmortems, and communication with company leaders and customers. ### Source excerpt We believe the highest performing engineering teams have a process to identify, triage, fix and learn from service degradations and downtime. At Localytics, we build highly available and scalable systems, and part of the key to our success is learning from failures. One way we foster a learning culture is