Mad-Sad-Glad

What it is

Mad-Sad-Glad sorts by emotion instead of by outcome: what made you angry, what made you sad, what made you glad. It's the only one of the three formats that asks about feelings directly rather than events or actions, which makes it better at surfacing morale and interpersonal friction that a purely process-focused retro will quietly skip past.

A "Mad" card and a "To Improve" card can describe the same incident and read completely differently — "Mad: I found out my PR was reverted from a Slack message, not from the person who reverted it" carries information a neutral "To Improve" phrasing would flatten. The process framing would likely produce something like "revert notifications are inconsistent," which is true but loses the part that actually matters: someone felt disrespected, and that's the thing the team needs to address, not the notification system.

The three-way split also matters more than it looks. A simple "good/bad" retro collapses everything negative into one bucket, but anger and sadness call for different responses — anger usually wants acknowledgment and a fix, sadness usually wants to be heard. Conflating them means a facilitator ends up applying the wrong response to half the cards in the room.

When to use it

Use it after a rough sprint (an outage, a missed deadline, a team conflict, a stretch of unplanned overtime) where the unspoken tension in the room is the actual retro topic, and pretending otherwise with a neutral format wastes the meeting. It's a poor choice for a routine, uneventful sprint; forcing an emotional framing onto a calm two weeks produces strained, low-signal cards. It's also worth reaching for after a quiet run of retros that have started feeling routine — three or four sprints of the same Went Well / To Improve rhythm can flatten out real frustration that's building underneath a calm surface. A Mad-Sad-Glad retro dropped in occasionally acts as a pressure check, not because every sprint needs it, but because a team that never runs one may be sitting on friction nobody's had a structured chance to name.

Common failure mode

Without a facilitator actively managing tone, "Mad" cards turn into a one-way complaint session, and people start writing them about colleagues rather than about the work. This format makes that easier to do than the other two formats, precisely because it's asking for feelings. Set the norm explicitly before adding cards starts: "Mad" is about situations and decisions, not people, and a card that names a colleague gets redirected into a process observation before the discussion phase, not read aloud as written.

The quieter failure is treating "Glad" as an afterthought once "Mad" has taken up all the emotional energy in the room. Read Glad cards first if the sprint was rough — it resets the room's tone before the harder conversation.

A less obvious risk is running this format too often. Its power comes from being a deliberate, occasional pressure release; used every sprint, the emotional framing stops feeling special and starts feeling like a demand to perform feelings on schedule, which produces exactly the flat, low-signal cards you'd get from forcing it onto a calm sprint in the first place.

Example cards