Run a FigJam Retrospective with Actions
Use a FigJam retrospective to examine a bounded period, distinguish events from interpretations and commit to a small measurable change. The board organizes the discussion; the value comes from an action someone can test during the next cycle.
Before you start: Have the period’s timeline, relevant delivery evidence and a facilitator. Agree how sensitive comments will be handled and whether attribution is appropriate for this team.
Worked example: A release slipped after two late handoff changes. Capture when each change occurred, why it was needed and how it affected work before concluding that the team needs more meetings.
Step-by-step guide
Bound the review period
Write the dates and goal at the top of the board. Add a short event timeline so participants discuss the same work rather than mixing unrelated frustrations.
Collect observations independently
Ask participants to add specific events and outcomes before group discussion. Allow time for quieter contributors and distinguish firsthand observations from secondhand assumptions.
Group possible causes
Cluster related observations and ask what conditions enabled the problem. Keep blame directed away from individuals and preserve evidence that challenges the most convenient explanation.
Choose a tractable change
Evaluate proposed actions by the problem they address and whether the team can run them next cycle. Prefer one clear experiment over a long list of aspirational improvements.
Assign ownership and evidence
Record an owner, due date and observable check. For a handoff change, define what will be reviewed earlier and how the team will know whether it helped.
Schedule the follow-through
Begin the next retrospective by reviewing the previous action. Keep the board’s decision summary accessible so the learning is not lost in a wall of sticky notes.
Common mistakes
General feelings replace events
Sentiment matters, but it does not identify a cause. Ask for the concrete moment and effect behind a broad complaint.
Too many actions
An unowned list rarely changes behavior. Choose a small action with a clear check.
No next-cycle review
Without follow-through the team cannot tell whether the change helped. Reserve time to revisit it.
Tips
Use a short factual timeline before collecting interpretations.
Let participants write before the loudest voice frames the discussion.
Record the follow-up outcome beside the original action.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.