The retrospective becomes a blame session. How should I run it?

Unsafe and unproductive learning review

Focus discussion on observable events, decision context, system conditions, and improvements within the team's influence. Use a neutral facilitator when needed and keep individual performance or misconduct processes separate. Psychological safety does not mean ignoring serious concerns; it means handling them through the proper process.

What to do now

Establish a constructive evidence-based review scope
Collect events and perspectives without personal attacks
Select practical improvements and owners
Route separate conduct concerns appropriately

Recommended action flow for unsafe and unproductive learning review: Establish a constructive evidence-based review scope then Collect events and perspectives without personal attacks then Select practical improvements and owners then Route separate conduct concerns appropriately. Escalate when the discussion becomes harmful or raises a concern requiring a formal process.

When to escalate

Escalate when

The discussion becomes harmful or raises a concern requiring a formal process.

Who decides

The sponsor and accepting business or service owner

Example

The team examines why review capacity was missing instead of blaming the person who waited for approval.

Mistake to avoid

Using the retrospective to publicly rank who caused the most problems.

Prevent a repeat

Verify that transferred obligations and important lesson actions are completed after the project closes.

Suggested ApprovedFlow setup

Projects
Documents
Tasks
Approvals

Keep the closure decision and final evidence with the project and transfer accepted residual actions to named ongoing owners. See the platform