> Markdown version of [/events/world-congress-2026-europe/sessions/1227-blameless](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1227-blameless). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Blameless Postmortems That Change Nothing: Cultural Anti-Patterns in Incident Learning


- **Date:** Friday, Jul 10, 2026
- **Time:** 09:40–10:10 (30 min)
- **Room:** Stage 10 - powered by TikTok
- **Event:** World Congress 2026 Europe

## Recording

[Watch recording](https://www.wearedevelopers.com/videos/100211-blameless-postmortems-that-change-nothing-cultural-anti-patterns-in-incident-learning)

## Description

Blameless postmortems are meant to help teams learn from incidents. In reality, many of them result in well-written documents and no meaningful change. 

Drawing from personal experience responding to production incidents, as well as patterns observed across multiple teams and organizations, this talk examines incident reviews as a window into real engineering culture. Not the culture described in values decks, but the one revealed by how teams explain failures, assign responsibility, and decide what not to fix. 

Across incidents ranging from minor outages to multi-hour production failures, we will explore recurring cultural anti-patterns that surface during postmortems. These include reviews that avoid uncomfortable truths, blamelessness used to shut down hard conversations, action items that quietly die in backlogs, and learning that stops at technical fixes while systemic and organizational causes remain untouched. 

The talk also looks at why these patterns become more dangerous as teams adopt AI-assisted development. Faster feedback loops and accelerated code changes amplify cultural weaknesses that postmortems were supposed to correct. 

Attendees will leave with concrete signals to look for in their own incident reviews, a small set of diagnostic questions that expose stalled learning, and practical techniques to turn postmortems into drivers of real improvement. Each anti-pattern is paired with a real incident example and a concrete alternative practice that has led to measurable improvement, rather than just better documentation.

## Speaker

### [Daniel Schley](https://www.wearedevelopers.com/@daniel-schley)

Engineering Leader at Independent


## Related talks at this congress

- [Checkmate: 5 Real Incidents That Can End a Software Company](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1442-checkmate-5-real) — Jasmin Azemović
- [What Production Knows: Closing the Loop Between AI Agents and the Systems They Build](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1470-what-production) — May Walter
- [Confessions of a Software Archaeologist: What I Did Wrong in 10 Years of Restructuring Software](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1270-confessions-of-a) — Hendrik Lösch
- [Why Distributed Teams Lose Momentum – Even When Everyone Means Well](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1276-why-distributed) — Franziska Höhne