Create room for useful reflection

A retrospective gives a team time to examine how it works. Focus on behaviours, processes and conditions rather than assigning blame. Invite quieter voices to contribute through written reflection as well as discussion.

Separate symptoms from causes

A missed milestone might reflect unclear scope, dependencies or delayed decisions. Ask what happened and why before selecting an improvement. The same symptom can have different causes across projects.

Choose a small action

Select an improvement the team can actually try. Assign an owner and agree when to review it. A long list of actions without capacity or ownership is unlikely to change the next cycle.

Check whether it helped

At the next review, examine the action and its effect. Keep, adjust or stop the change based on what happened. This makes retrospectives a learning loop rather than a recurring conversation about the same concerns.

Take this with you

Move from a discussion of frustrations to a small, owned improvement.