Mad, Sad, Glad Retrospective

Help your team name frustration, acknowledge disappointment, celebrate success, and turn emotional feedback into thoughtful improvements.

What Is a Mad, Sad, Glad Retrospective?

Mad, Sad, Glad is a Sprint Retrospective technique that invites team members to reflect on three emotional responses. “Mad” captures frustration, “Sad” captures disappointment or missed opportunities, and “Glad” recognizes moments that created satisfaction, confidence, or pride.

Emotional feedback matters because a process can look acceptable on paper while still exhausting, discouraging, or energizing the people doing the work. Naming those reactions helps teams understand impact, uncover patterns, and improve collaboration. The goal is learning—not blaming individuals for how others felt.

Mad, Sad, Glad Examples

Mad

Frustrations that made effective work more difficult.

Constant interruptions made it difficult to finish focused work.
Frequent production issues repeatedly displaced sprint priorities.
Poorly defined requirements caused avoidable rework.
Long code review delays blocked dependent stories.
Excessive context switching slowed progress toward the sprint goal.

Sad

Disappointments, losses, and opportunities the team wishes had gone differently.

The team did not achieve the sprint goal despite sustained effort.
Customer feedback arrived too late to influence the solution.
A valuable product idea was postponed again.
Technical debt continued to grow without a shared plan.
Some team members could not participate fully in key decisions.

Glad

Successes and experiences the team wants to recognize and repeat.

Strong teamwork helped resolve an unexpected blocker quickly.
The team delivered an important feature successfully.
Improved automated testing caught a regression before release.
Positive customer feedback confirmed the value of recent work.
Clearer communication reduced surprises during the sprint.

Use specific observations rather than judgments. BugNBrag's What Went Well examples and constructive What Didn't Go Well examples can help participants describe events and their impact clearly.

How to Facilitate Psychological Safety

Set expectations. Explain that every reaction is valid and the discussion will focus on learning and improvement.
Begin privately. Give everyone quiet writing time so early speakers do not shape every response.
Invite broad participation. Use anonymous input or a round-robin when people need more space to contribute.
Group related feedback. Combine similar observations and ask clarifying questions without debating feelings.
Keep discussion constructive. Translate criticism of a person into the behavior, process, or condition the team can address.
Select actionable improvements. Prioritize one or two themes, name an owner, and define a small next-sprint action.

Review the Sprint Retrospective best practices for more guidance on safety, focus, and follow-through. A neutral retrospective icebreaker can also help the team settle into an honest conversation.

Discussion Tips

Listen without judgment or immediately trying to correct another person's experience.
Focus on observable behaviors, team processes, and working conditions.
Encourage every team member to contribute before prioritizing themes.
Look for recurring patterns across multiple responses and sprints.
Finish with specific improvement actions the team can review next time.
Give Glad responses real discussion time instead of treating them as decoration.

Distributed teams should combine silent input with deliberate turn-taking. The guide to remote Sprint Retrospectives offers practical ways to make participation more equitable.

When This Format Works Best

Mad, Sad, Glad works well after an intense sprint, a significant delivery, a team change, or any period when morale and collaboration deserve closer attention. It can reveal why an event mattered, not merely whether it succeeded or failed. These broader Sprint Retrospective examples can help teams turn the resulting themes into clear cards and actions.

Choose another format when serious conflict requires a trained facilitator, when participants do not yet have enough trust to discuss emotions safely, or when the team needs a detailed technical root-cause analysis. For a more process-oriented review, try the Start, Stop, Continue retrospective instead.

Create space for honest, constructive reflection

Free. No account. No setup. Just better team conversations.

Create Free Session