Mood and Action Points Retrospective

Choose this exercise

Purpose: Track follow-through on past commitments while capturing current sentiment and operational improvements for the next work cycle.

Use it when: Use at the close of an iteration, project cycle, or sprint to audit previous commitments before generating new adjustments.

Skip it when: Skip during acute interpersonal disputes or at initial project kickoffs where no previous cycle or action points exist.

Group arrangement: Individual silent reflection followed by facilitated whole-room discussion and drafting.

Timing: 45 minutes matches the source template duration.

Materials and tools

• 1 whiteboard or digital board divided into 5 columns: Mood, Prev. Action Points, What Went Well, What Could Be Improved, New Action Points
• Sticky notes (at least 10 per participant) or digital cards
• Fine-tip markers (1 per participant)
• Timer

Before participants arrive

1. Draw or configure the 5 columns on the board: Mood, Prev. Action Points, What Went Well, What Could Be Improved, New Action Points.
2. Write the exact action items agreed upon in the previous retrospective into the 'Prev. Action Points' column before the session starts.

Say this to open

Welcome. We will review our last cycle by looking at our energy, checking our past commitments, and noting what worked and what needs adjustment. Start by posting a word or rating for your mood, or skip it if you prefer. Then write your observations under What Went Well and What Could Be Improved.

How to run it

1. Check in and review context 5 minutes

   Explain the five columns. Invite participants to post a note under 'Mood' describing their current energy in 1 or 2 words, or leave this column blank if they prefer. The facilitator then reads aloud each pre-populated item from 'Prev. Action Points' so the team recalls their prior commitments.

2. Generate feedback silently 7 minutes

   Participants write notes silently. They post observations under 'What Went Well' and 'What Could Be Improved', limiting each note to 1 distinct observation. Participants may also place silent clarification notes directly beside any previous action point.

3. Review past actions and feedback 18 minutes

   Facilitate a review column by column. First, check each previous action point: record whether it is completed, blocked, carried over, or dropped. Next, cluster related notes under 'What Went Well' and 'What Could Be Improved'. Invite comments on recurring operational themes while focusing strictly on systems, not personal attributes.

4. Draft new action points 10 minutes

   Direct the whole room to propose concrete next steps addressing the top improvement themes. Write proposals into 'New Action Points'. Each approved point must have a verifiable outcome, a single designated owner, and a target date. Limit the list to 2 to 4 total items.

5. Confirm actions and debrief 5 minutes

   Facilitator reads out the finalized action points and confirms commitments with the assigned owners. Ask one or two debrief questions to close the session.

Debrief questions

• Which completed action item from last cycle made the biggest practical difference?
• Are our new action points small enough to finish in the upcoming cycle?

Finished output: A board documenting cycle feedback and 2 to 4 agreed action points with assigned owners.

Remote

Run on a collaborative digital whiteboard configured with the five columns. Participants add notes silently. The facilitator brings the view to the focal column during review and calls on attendees by name or chat responses.

Hybrid

All participants access a shared digital board. Remote and in-person contributors add digital cards during silent phases. The facilitator calls alternately on remote and room participants during review.

Access and participation choices

• Participants may post notes anonymously or use pre-printed neutral markers.
• Anyone may choose not to share personal mood reflections without disclosing a reason.
• Discussion participation is voluntary; silent text contributions are fully valid.

If the session gets stuck

Unfinished previous action points stall the discussion and create defensiveness.

Treat incomplete tasks as capacity or scoping issues. Ask whether the item was sized wrong, blocked by external forces, or no longer necessary, and decide whether to close or resize it.

Proposed action points are vague, such as 'communicate better'.

Ask the team: 'What specific artifact, ticket, or calendar invite will prove this is done next Friday?' Rewrite it to describe that observable result.

Terms used here

• Action Point: A discrete, measurable task assigned to a single owner with an explicit due date.