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.
User Flow Template
Works best for:
Desk Research, Flowcharts, Mapping
User flows are diagrams that help UX and product teams map out the logical path a user should take when interacting with a system. As a visual tool, the user flow shows the relationship between a website or app’s functionality, potential actions a user could take, and the outcome of what the user decides to do. User flows help you understand what a user does to finish a task or complete a goal through your product or experience.
Customer Touchpoint Map Template
Works best for:
Desk Research, Product Management, Mapping
To attract and keep loyal customers, you have to truly start to understand them—their pain point, wants, and needs. A customer touchpoint map helps you gain that understanding by visualizing the path your customers follow, from signing up for a service, to using your site, to buying your product. And because no two customers are exactly alike, a CJM lets you plot out multiple pathways through your product. Soon you’ll be able to anticipate those pathways and satisfy your customers at every step.
SAFe Program Template
Works best for:
Agile Methodology, Diagrams, Agile Workflows
Many organizations use the Agile model, but even companies that don’t rigorously adhere to all Agile standards have adopted Agile tools and methods like Program Increment (PI) Planning. Even if you’re not participating in a formal PI session, a program board can be a great way to establish communication across teams and stakeholders, align development objectives with business goals, clarify dependencies, and foster cross-functional collaboration. The board provides much-needed structure to planning sessions, yet is adaptable enough to accommodate brainstorming and alignment meetings.
4 L's Retrospective Template
Works best for:
Retrospectives, Decision Making
So you just completed a sprint. Teams busted their humps and emotions ran high. Now take a clear-eyed look back and grade the sprint honestly—what worked, what didn’t, and what can be improved. This approach (4Ls stand for liked, learned, lacked, and longed for) is an invaluable way to remove the emotion and look at the process critically. That’s how you can build trust, improve morale, and increase engagement—as well as make adjustments to be more productive and successful in the future.
Work Plan Template
Works best for:
Mapping, Project Planning
A work plan is essentially a roadmap for a project. It articulates the steps you must take to achieve the desired goal, sets demonstrable objectives, and establishes measurable deliverables. An effective work plan guides you throughout the project lifecycle, allowing you to realize an outcome by collaborating with your team. Although work plans vary, they generally contain four core components: goals, strategy, tactics, and deliverables.
Event Planning Template
Works best for:
Planning, Workshops
Whether you’re planning a product launch, fully remote conference, or milestone event, the Event Planning Template will act as a visual checklist and map for all the details you need to consider before the big day. The Event Planning Template is an adaptable way to make sure the creative and strategic vision of your event doesn’t get lost in the details. By mapping out different sections - from the marketing plan, to the agenda, to snacks and swag for guests — you and your team can focus on the details most important to your functions, and collaborate as needed when overlaps occur.