[TEMPLATE] - Post-Mortem 2.0: Culture & Process
Most post-mortems find the wrong thing.
They find the person who made the call. The line of code that failed. The decision that, in retrospect, was clearly wrong. They write it up, assign a lesson learned, and file it somewhere.
Then the same thing happens again three months later because nothing in the environment actually changed.
This template runs a different kind of session. Instead of asking who made the mistake, it asks what in our environment made that choice feel like the right one at the time. That question changes everything about the conversation that follows.
Four sections. The Mirror Test examining the environmental conditions that produced the outcome. A psychological safety check because how safe people felt raising a concern is often the real story. A stop/start/simplify action list. And a human action item — one specific thing the team will do to support whoever was closest to the friction point.
Use it 24 to 72 hours after an incident. Use it after near-misses too, not just disasters. The teams that improve fastest are the ones that are honest enough to learn while the memory is still fresh.
Bring your questions to the Q&A.
About the Author
Tino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human, one verb at a time.



I’d love your input.
I believe that the best systems aren't built in isolation they are refined through shared leadership and collective insight. This template is a starting point, but I want it to be a living document.
Is there a 'deal-breaker' question you’ve faced in a pitch that isn't covered here?