Mad Sad Glad Retrospective
Conduct a retrospective on understanding the emotions and feelings of the team.
Trusted by 65M+ users and leading companies
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 the retrospective to 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.
Get started with this template right now.
Software Requirements Document
Works best for:
Product Development, Software Development
Unlock unmatched project clarity and effortlessly manage your software project requirements with Miro's Software Requirements Document Template. This template helps you empower your team by visually representing your project's scope, including functional and non-functional requirements. With dynamic flowchart features, you can effortlessly expand and refine your project details, ensuring a shared understanding among team members.
Lesson Reflection Template
Works best for:
Education, Meetings
The Lesson Reflection template is a tool to create space for self-reflection and improvement. Students can evaluate the key takeaways from a lesson and what are the topics they find most interesting. As teachers receive the student’s Lesson Reflection, they can look for opportunities to improve learning and teaching methodologies. The Lesson Reflection template can help you facilitate the educational process, and it’s easy to use and straightforward.
Burndown Chart Template
Works best for:
Project Management, Agile Workflows, Mapping
Whoa whoa whoa, pace yourself! That means knowing how much work is left—and, based on the delivery date, how much time you’ll have for each task. Perfect for project managers, Burndown Charts create a clear visualization of a team’s remaining work to help get it done on time and on budget. These charts have other big benefits, too. They encourage transparency and help individual team members be aware of their work pace so they can adjust or maintain it.
Brainwriting Template
Works best for:
Education, Ideation, Brainstorming
Brainstorming is such a big part of ideation. But not everyone does their best work out loud and on the spot, yelling out thoughts and building on others’ ideas. Brainwriting is a brilliant solution for them—creative thinkers who happen to be more introverted. This approach and template invites participants to reflect quietly and write out their ideas, and then pass them to someone else who will read the idea and add to it. So you’ll get creative ideas from everyone—not just the loudest few.
PRD Template
Works best for:
Product Development, Product , Management
The PRD Template by Miro is a blueprint designed to streamline the product development process. Acting as a central hub for all essential details, this template ensures team alignment by laying out clear project objectives, use cases, and design specifics. The primary benefit? Seamless communication and clarity, reducing the likelihood of missteps and fostering a smooth transition from idea conception to product launch.
Impact/Effort Matrix Template
Works best for:
Project Management, Strategic Planning, Prioritization
Growing organizations have countless to-do’s and only so many hours in a day (or weeks before a big launch) to get them done. That’s where an impact effort matrix comes in. It gives you a quick visual guide to help prioritize your tasks and know exactly what’s worth doing. Using our template, you can create a matrix that organizes your activities into four main categories: quick wins that are low effort, effort-intensive projects that provide long-term returns, fill-ins that are low effort but low value, and time-wasters.