Running a Retrospective Without Blame
Turn what went wrong into what do we change
A structured 30-minute conversation for after a project, a difficult week, or a mistake. Creates a safe space to examine what happened — without it becoming a search for who to blame. The goal is systemic improvement, not individual accountability.
Step-by-Step Guide
0 / 5 completedEvidence Base
Grounded in Edmondson's psychological safety research and the agile retrospective methodology (Derby & Larsen, 2006).
Tip: These tools are most effective when practiced consistently, not perfectly. Start with one framework, use it for 4-6 weeks, and observe what shifts before adding another.