Updated (published )

Mad Sad Glad Retro: Questions, Process & Template

The Mad Sad Glad Retro is a simple retrospective format for teams that want to openly discuss experiences from the last sprint and turn them into concrete improvements. It combines two negative perspectives – Mad and Sad – with a positive one: Glad. This keeps the retrospective honest without just collecting problems.

Mad Sad Glad Retro: The three questions

The method works with three columns and one question per emotion:

  • Mad: What made you angry?
  • Sad: What made you sad?
  • Glad: What made you glad?

The difference between Mad and Sad helps with analysis: “Mad” often points to obstacles that can be influenced, such as unclear priorities or avoidable waiting times. “Sad” tends to reveal disappointing or burdensome experiences, for example when important feedback is missing. “Glad” draws attention to practices the team should maintain or expand.

Mad Sad Glad Retro 😯

@assets/blog/Retro-Method-Idea-Mad-Sad-Glad-EN-EN.png not found.

Open questions

What made you mad? 😤
What made you sad? 😢
What made you glad? 🤩

Examples for Mad, Sad, and Glad

What made you mad? 😤

“The new tool makes it harder to prioritize our product backlog.” Statements like this often point to a specific process the team can change. Ask: What exactly happened, who is affected, and what would be different next time?

What made you sad? 😢

“Not everyone on our team feels comfortable speaking up.” This topic may indicate a lack of psychological safety. Give the group time to understand the observation instead of immediately suggesting a solution.

Strengthening psychological safety in agile teams

What made you glad? 🤩

“Our alignment before the sprint really created clarity this time.” Positive examples are not a side note: They show which habits work and should be continued deliberately.

Moderating a Mad Sad Glad Retro in 30 minutes

  1. Set the frame (3 minutes): Remind everyone that this is about observations and shared improvement – not assigning blame.
  2. Collect silently (5 minutes): Each person writes individual notes for Mad, Sad, and Glad. Silent work also gives quieter team members space.
  3. Cluster and understand (10 minutes): Group similar notes and ask the authors to briefly provide context if needed.
  4. Prioritize (5 minutes): Choose one or two topics with the greatest benefit for the team.
  5. Define actions (7 minutes): For each topic, formulate a concrete, accountable next action and review it in the following retrospective.

Important: A good Mad Sad Glad retrospective does not end with collecting emotions. Only a clear action turns an observation into an improvement.

When is the Mad Sad Glad Retro suitable?

The format is especially useful after a turbulent sprint, when there are tensions in the team, or when you want to make successes visible alongside problems. For new teams, the structure is easy to understand; experienced teams can use the three questions as a quick check-in.

When sensitive topics arise, the facilitation should ensure a respectful setting. If uncertainty or a lack of trust becomes visible repeatedly, a more in-depth team health check is worthwhile.

Team Health Check in three steps

Frequently asked questions about the Mad Sad Glad Retro

What is a Mad Sad Glad Retro?

A retrospective with three questions about what made the team angry, sad, and glad. It helps process negative experiences and strengthen effective collaboration.

How many topics should a team work on?

Usually one or two prioritized topics are enough. Few, clearly owned actions are more valuable than a long list without implementation.

How often should you use the Mad Sad Glad Retro?

It works as a standalone sprint retrospective or as a change from other formats. Use it when emotions, collaboration, and concrete sprint experiences should be at the center.

Conclusion: Turning emotions into improvements

The Mad Sad Glad Retro is deliberately straightforward: Three questions create space for frustration, disappointments, and successes. If the team then agrees on a few concrete actions, it becomes a helpful retrospective with a lasting effect.

Blog category

More articles on "Agile Retrospective Ideas"

View all articles in this category
54 Retrospective Ideas, Templates & Formats for Agile Teams in 2026

54 Retrospective Ideas, Templates & Formats for Agile Teams in 2026

54 fun retrospective ideas, templates, and formats for agile teams: sprint retrospectives, remote team retros, project retrospectives, and classics.

First retrospective: How to get started easily as a team

First retrospective: How to get started easily as a team

Your first retrospective, explained simply: goals, process, typical mistakes, and why the Keep-Stop-Start retro is the best entry point for new teams.

9 effective team exercises for agile retrospectives

9 effective team exercises for agile retrospectives

9 team exercises that prepare your team for agile retrospectives and ensure that retros become more open and effective.

26 Fun & Fresh Agile Retrospective Templates in 2026

26 Fun & Fresh Agile Retrospective Templates in 2026

Discover 26 fun & fresh Agile Retrospective templates for 2026. Find the best method for your team and make your retrospectives successful.

Spotify Health Check Retrospective: Moderation & Tips

Spotify Health Check Retrospective: Moderation & Tips

Use the Spotify Health Check in retrospectives for team development. This guide offers moderation questions and templates for Team, Tech & Co.

Sprint Refinement vs Sprint Retrospective: Explained Simply

Sprint Refinement vs Sprint Retrospective: Explained Simply

Sprint Refinement vs Sprint Retrospective explained simply: clear differences, practical examples, decision support, 2 retro ideas and FAQ.

4-Quadrant Retrospective: Examples & Implementation Tips

4-Quadrant Retrospective: Examples & Implementation Tips

What is a 4-quadrant retrospective? Learn about the structure, quick facts, origin, comparison, and concrete implementation for effective sprint retros.

42 Fun & Creative Retrospective Icebreakers breaking any Ice

42 Fun & Creative Retrospective Icebreakers breaking any Ice

Discover 42 creative retrospective check-ins and icebreakers for agile teams. Find the best questions and methods to make every retro interactive.

When should a sprint retrospective happen?

When should a sprint retrospective happen?

When is the best time to hold a sprint retrospective? Find out when in the sprint cycle and on which day the retrospective is most effective.

Echometer Newsletter

Don't miss updates on Echometer & get inspiration for agile working

FAQs about Retrospective Tool

Top answers for anyone exploring our Retrospective Tool.

Do I have to register to test the Retro Tool?

No, you do not need to log in to Echometer or register to test the Retro Board and Retro Tool in Echometer.

You can try out Echometer’s Retro Board via the following link without logging in: Try a Practice Round

Where can I try retrospective software for free?

You can test retrospective software directly in Echometer for free. You do not need to log in or register: the retro board and templates can be tried out immediately in the browser.

You can easily try out Echometer’s retro board without logging in using the following link: Start trial run

You can find more ways to try it out for free on the Page for the retro board without login and registration.

How can I buy Echometer's retro tool?

First, simply register for free in Echometer. Then navigate to the workspace for which you would like to purchase the retro tool. If you haven’t already done so, you can do so here: Create account in Echometer 1:1 tool

You can then manage your subscription (for both the retro tool and the 1:1 software) within the workspace settings.

You can choose from various payment methods when upgrading.

If you do not have access to your company’s credit card yourself, you can simply add a buyer as a workspace admin in your Echometer workspace so that this admin can carry out the upgrade for you.

What is the difference between the Retrospective tool and the 1:1 software?

In Echometer there are two separate software solutions that are available within each workspace in Echometer:

  • 1:1 tool: Software for planning and conducting 1:1 meetings and tracking employee development
  • Retrospective tool: Software for planning and moderating retrospectives and tracking team development through team health checks

Both are independent software solutions, so they can be used separately from each other.

However, they work according to the same principles and aim to achieve the same added value: The continuous improvement of agile teams. In this respect, the simultaneous use of both software solutions is recommended.

Can I appoint several admins in Echometer?

Yes, you can assign administration rights to any number of users at both team level and workspace level. Please note the following:

  • Only workspace admins can take out and manage a Echometer subscription for a Echometer workspace.
  • Only workspace admins can create additional teams and name or remove additional workspace admins.
  • Team admins can appoint and remove additional team admins and team members for their team
What is the structure of retrospectives in Echometer?

The Echometer Retrospective software is designed to guide teams through the retrospective process with maximum ease and effectiveness, following best practices.

The steps and their sequence can be customized using the navigation within the retro. By default, a retrospective in Echometer is structured in this way:

  • Icebreaker
  • Review of open measures from past retros
  • Collect feedback (first Health Checks, then open questions)
  • Prioritization of feedback
  • Deriving action items
  • Concluding the retrospective with the “ROTI score” (Return on Time Invested)

Additional whiteboards (e.g. for workshops, for analyzing problems or for brainstorming measures) can also be added spontaneously at any point using the Retrospective navigation.