How to Run Community Retrospectives

A retrospective is a structured conversation about how work happened, not an exercise in assigning blame. It helps a community carry lessons into its next activity.

Set the scope. Focus on one event, project, or period so the conversation remains concrete.

Invite observations before solutions. Understanding what happened makes it easier to choose improvements that address the real issue.

Include different perspectives. Organizers, participants, newcomers, and people who could not take part may notice different barriers.

Separate urgent repairs from longer-term ideas. A broken access link may need immediate action, while a new event format can be tested later.

Record a few commitments. Too many action items make follow-through difficult; choose the changes most likely to improve the next experience.

Revisit the commitments. A retrospective creates value when its lessons affect future practice rather than remaining in private notes.