Retrospective

A structured post-project review examining what went well, what didn't, and what to change going forward. Unlike a casual debrief, a retrospective follows a deliberate format that ensures both successes and failures get equal attention. The power is in making reflection routine rather than exceptional—teams that run retrospectives after every sprint or project create a continuous improvement loop that compounds over time.

When to use it

After every sprint, project, or major milestone; at regular intervals (monthly, quarterly) for ongoing operations; when a team feels stuck in recurring patterns; after both successes and failures—you can learn from what worked, not just what didn't.

How it can help

The simplest high-ROI management practice: after every significant project or time period, gather the team for 45-60 minutes and answer three questions: (1) What should we keep doing? (2) What should we stop doing? (3) What should we start doing? Document the answers and assign owners to action items. The key discipline is actually changing behavior based on findings—most teams do retrospectives but never implement the changes they identify.