# postmortems Published articles for postmortems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Senior Leaders Should Attend Post-Incident Reviews for Major Cloud Incidents DevFeed: [Why Senior Leaders Should Attend Post-Incident Reviews for Major Cloud Incidents]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-29T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [incident](), [Cloud](), [control-plane](), [Deployment]() Tags: [cloud](), [control-plane](), [customers](), [deploy](), [incident](), [incident-management](), [leadership](), [major](), [operations](), [post](), [postmortems](), [reliability](), [review](), [service]() ### AI overview The article argues that senior leaders should attend Post Incident Reviews for major cloud incidents because failures can affect many customers and teams. Leadership helps approve cross-team changes, resolve trade-offs, and ensure corrective actions are completed. ### Source excerpt For major incidents, a Post Incident Review is not an operations meeting. It is where leaders remove the blockers that keep the service from becoming safer. ## Cloud provider postmortems: volume vs depth DevFeed: [Cloud provider postmortems: volume vs depth]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-05T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [Cloud](), [incident](), [SRE](), [site-reliability-engineering](), [engineering-culture]() Tags: [2017](), [2025](), [2026](), [aws](), [azure](), [cloud](), [dynamodb](), [engineering-culture](), [gcp](), [incident](), [incident-management](), [postmortems](), [s3](), [sre](), [transparency](), [writeup]() ### AI overview The article compares public postmortem practices among Google Cloud, Azure, and AWS. It argues that Google Cloud emphasizes high volume and speed, Azure emphasizes detailed transparency and customer accountability, and AWS publishes fewer writeups with greater depth and industry influence. ### Source excerpt GCP publishes 100+ postmortems a year. AWS publishes almost none. Azure has become the transparency leader. What each posture reveals about engineering culture, and what SREs should steal from all three. ## ITIL vs SRE: why the big clouds went their own way DevFeed: [ITIL vs SRE: why the big clouds went their own way]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-07-26T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [SRE](), [site-reliability-engineering](), [Development](), [Terraform](), [pulumi](), [Availability](), [feature flags](), [incident]() Tags: [automated](), [aws](), [azure](), [cloud](), [feature-flags](), [gcp](), [human-review](), [hyperscaler](), [incident](), [incident-management](), [infrastructure-as-code](), [itil](), [on-call](), [postmortems](), [pulumi](), [release](), [reliability](), [service-catalog](), [sre](), [terraform]() ### AI overview This opinion article compares ITIL practices with SRE operations at hyperscaler scale. It argues that human change boards, single production instances, developer-to-operations handoffs, documentation-first configuration management, and weekly release windows do not fit environments serving millions of external customers. It describes automated approvals, gradual deployments, service-team ownership, infrastructure as code, continuous release, error budgets, SLOs, and blameless postmortems as alternatives. ### Source excerpt The big clouds don't run ITIL. Five assumptions ITIL makes that break at hyperscaler scale, and what AWS, Azure, GCP, and OCI use instead. ## Using Postmortems to Learn from Mistakes DevFeed: [Using Postmortems to Learn from Mistakes]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-06-21T00:00:00Z Content type: opinion Language: en Sources: [Fernando Cejas Blog]() Topics: [Learning](), [retrospectives](), [Resilience]() Tags: [android](), [culture](), [development](), [engineering](), [infrastructure](), [ios](), [java](), [kotlin](), [learning](), [linux](), [open-source](), [postmortems](), [processes](), [programming](), [python](), [resilience](), [retrospectives](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview The article argues that organizations should treat mistakes as opportunities to learn, share lessons, and avoid repeating failures. It presents postmortems as a tool for drawing useful conclusions and supporting retrospective discussion. ### Source excerpt **Postmortems** are a valuable tool for learning out of mistakes. They provide **useful conclusions** and should be included in retrospectives for further discussion in order to **not fall into the same trap again.** ## Postmortems for Learning From Mistakes DevFeed: [Postmortems for Learning From Mistakes]() Original publisher: [Read original article]() Author: Fernando Cejas (me@fernandocejas.com) Published: 2020-06-21T00:00:00Z Content type: opinion Language: en Sources: [Fernando Cejas Blog]() Topics: [Learning](), [retrospectives](), [Resilience]() Tags: [android](), [culture](), [development](), [engineering](), [infrastructure](), [ios](), [java](), [kotlin](), [learning](), [linux](), [open-source](), [postmortems](), [processes](), [programming](), [python](), [resilience](), [rust](), [scala](), [software](), [software-development](), [web-development]() ### AI overview The author argues that organizations should treat mistakes as opportunities to learn without blaming people. The article presents postmortems as a way to share lessons, discuss them in retrospectives, avoid repeating failures, and build resilience. ### Source excerpt **Postmortems** are a valuable tool for learning out of mistakes. They provide **useful conclusions** and should be included in retrospectives for further discussion in order to **not fall into the same trap again.**