Mad Sad Glad Retrospective
Conduct a retrospective on understanding the emotions and feelings of the team.
About the Mad Sad Glad Retrospective
What is Mad Sad Glad?
After a Sprint, it can be helpful for the team to pause and take stock of how they feel. This is crucial for maintaining morale and getting the most out of each Sprint. But sometimes, it can be hard to gauge your team’s feelings with open-ended questions like “How are you feeling?” That’s why many teams choose to employ the Mad Sad Glad retrospective.
Mad Sad Glad is a popular technique for examining your team member's emotions and encouraging them to think about how they feel. You can use a retro tool to run a session and highlight the positive feelings your team might have after a Sprint, but also to underline concerns or questions they might have going forward.
When should you run a Mad Sad Glad retrospective?
This type of retrospective can be especially valuable when there is a negative team dynamic, or if there is tension but team members haven't spoken about it yet. Participants can find it useful to use a structured framework to talk about their emotions – particularly in a fast-paced, results-focused agile environment.
How to use the Mad Sad Glad template
Miro’s virtual collaboration platform is perfect for running a Mad Sad Glad retrospective with your team. Simply select the template and invite your team to join.
The facilitator should give everyone 30-60 minutes to think about how they felt about the previous sprint. Then, allow the respondents some time to take stock of their feelings and write down the highlights on the Mad Sad Glad template. Were there parts of the Sprint that left them angry? Upset? Or satisfied? When the team is finished writing, bring everyone together to discuss. The facilitator can ask follow-up questions and take notes throughout the process.
4 tips for running a Mad Sad Glad retrospective
1. Give people space and time to reflect
Make sure the team has about 30 to 60 minutes of uninterrupted time to take stock of how they feel. Encourage people to take copious notes. Make sure the room is quiet and out of the way.
2. Make sure phones are turned off
Ask all attendees to turn off their phones so they can focus on the retrospective. If people are distracted by their phones, then they will find it harder to reflect.
3. Be inclusive
Assure everyone that there are no right or wrong answers. Remember, the goal of Mad Sad Glad is to take stock of how everyone is feeling, not to brainstorm processes or strategies.
4. Keep the focus on emotions
Encourage your team to focus on emotion, not action. People who might feel uncomfortable sharing their feelings sometimes instead try to pivot to strategy. Gently encourage them to avoid that.
3 reasons to use a Mad Sad Glad retrospective?
The Mad Sad Glad Retrospective is specifically focused on the team's emotional journey, and this is a unique approach with different benefits from a normal agile retrospective.
1. Build trust
By giving team members a space to discuss their feelings and emotions about the work they’ve done, you encourage honesty and forthrightness. Creating more honest, open, and positive teams ultimately help team members trust each other.
2. Improve morale
Almost everyone will struggle with certain things or get frustrated, and oftentimes workplaces don’t provide an avenue to talk about these frustrations. Giving employees an opportunity to talk through their difficulties will help them feel more welcomed, and ultimately boost morale.
3. Increase engagement
If team members are frustrated and don’t feel heard, they tend to check out. With a Mad Sad Glad retrospective, those team members can speak up and work towards solving their problems and building a more inclusive workspace where people can stay engaged.
You can also explore all project retrospective templates available through our collection.
Get started with this template right now.
SCAMPER Model
Works best for:
Ideation, Operations, Brainstorming
Is your team in a rut? Have you had a lingering problem that can’t seem to be solved? First introduced in 1972, SCAMPER. is a brainstorming method developed by Bob Eberle, an author of creativity books for young people. This clever, easy-to-use method helps teams overcome creative roadblocks. SCAMPER walks you through seven questions that are meant to encourage your team to approach a problem through seven unique filters. By asking your team to think through a problem using this framework, you’ll unlock fresh, innovative ways to understand the problem you’re trying to solve.
The Emotions Wheel Icebreaker Template
Works best for:
Icebreakers, Meetings
Allow people to express emotions and connect with each other. Use the Emotions Wheel Icebreaker to build the foundations for an important conversation.
Christmas Retrospective
Works best for:
Agile Methodology, Meetings, Retrospectives
The Christmas Retrospective template offers a festive and celebratory approach to retrospectives, incorporating the holiday spirit into the session. It provides elements for reflecting on achievements, sharing gratitude, and setting intentions for the future. This template fosters a sense of warmth, togetherness, and appreciation among team members, encouraging reflection on both professional and personal growth. By infusing the retrospective with the joy of the holiday season, the Christmas Retrospective empowers teams to strengthen relationships, cultivate positivity, and drive continuous improvement effectively.
Effective Meeting Template by Zoom
Works best for:
Team Meetings
Run effective meetings and keep everyone focused with Zoom’s Effective Meeting Template. Bring structure and creativity to every online meeting.
Agile Team Events with Jira Template
Works best for:
Agile , Agile workflows
The Agile Team Events with Jira template in Miro is designed to streamline Agile workflows and enhance team collaboration. This template integrates seamlessly with Jira, allowing teams to manage their Agile events such as sprint planning, daily stand-ups, sprint reviews, and retrospectives directly within Miro. One significant benefit of this template is its ability to provide real-time updates. Any changes made in Miro can be synced back to Jira, ensuring that all team members are on the same page and that the project management tool reflects the latest status. This feature helps in maintaining consistency and accuracy across all Agile processes, reducing the risk of miscommunication and enhancing overall productivity.
Kaizen Report Template
Works best for:
Agile Methodology, Operations, Documentation
What makes a great company great? They know that greatness needs to be fostered and maintained — meaning they never stop working to improve. If you’re one of those companies (or aspire to be), a kaizen report is an ideal tool. It creates a simple visual guide to continuous improvement activities on a team, departmental, and organizational level. Using a kaizen report approach, every employee in an organization audits their own processes and understands what they might have overlooked, making this a powerful tool for increasing accountability at all levels.