A retrospective format should make reflection easier, not distract the team with decoration. Process-focused retrospectives can miss the human impact of work.
This guide explains the approach in practical terms: what it is, why it is useful, when to use it, how to apply it step by step, and which mistakes to avoid.
Mad Sad Glad is a retrospective activity that asks participants to sort experiences into three emotional categories. Mad captures frustration or anger, Sad captures disappointment or loss, and Glad captures satisfaction, pride, or gratitude.
Process-focused retrospectives can miss the human impact of work. Emotions often reveal unresolved conflict, loss of trust, overload, or positive practices worth protecting. The format gives those signals a legitimate place without turning the meeting into unstructured venting.
Use Mad Sad Glad after a demanding sprint, reorganization, major incident, deadline, team change, or period of conflict. Do not use it as a substitute for professional support when serious wellbeing concerns are present.
After a difficult release, a team listed frustration about last-minute scope, sadness that planned quality work was dropped, and pride in how support and engineering collaborated during launch. The discussion showed that the deepest issue was not overtime alone; it was the absence of a clear scope-freeze decision. The team created a launch change policy and preserved the cross-functional support channel that had worked well.
It can be appropriate when the scope is work-related and the facilitator creates clear boundaries. Participation in personal disclosure should not be forced.
No, especially when anonymous input is enabled. Focus on understanding the pattern and its impact.
Yes. Some teams use Frustrated, Disappointed, and Energized to fit their culture.
Mad Sad Glad helps teams treat emotions as useful information about the work system. Facilitate carefully, avoid blame, and translate the most important signal into a concrete change or support action.
Use SprintsPlans to collect Mad, Sad, and Glad cards anonymously, vote on the most important theme, and record the team's response as an action item.
Use a Lean Coffee retrospective when the team needs an agenda created through participant input, democratic voting, and tightly timeboxed discussion.
Use the Sailboat retrospective to explore goals, accelerators, obstacles, and risks through a visual format that keeps team discussion practical and engaging.
Learn what retrospective means in Agile and everyday work, why teams use retrospectives, and how a simple retrospective process can turn lessons learned into meaningful improvements.