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 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.
PI Planning Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
PI planning stands for “program increment planning.” Part of a Scaled Agile Framework (SAFe), PI Planning helps teams strategize toward a shared vision. In a typical PI planning session, teams get together to review a program backlog, align cross-functionally, and decide on the next steps. Many teams carry out a PI planning event every 8 to 12 weeks, but you can customize your planning schedule to fit your needs. Use PI planning to break down features, identify risks, find dependencies, and decide which stories you’re going to develop.
Breakout Group Template
Works best for:
Education, Team Meetings, Workshops
Breakout groups provide an excellent opportunity for teammates to have candid conversations and connect on a more intimate level than is possible during a broader meeting. When you’re in a large group setting, it can be difficult for people to feel safe or comfortable speaking up. In a smaller group, participants can feel safer sharing their ideas. Since the group is more intimate, teams are empowered to participate rather than observe.
Kano Model Template
Works best for:
Desk Research, Product Management, Prioritization
When it comes down to it, a product’s success is determined by the features it offers and the satisfaction it gives to customers. So which features matter most? The Kano model will help you decide. It’s a simple, powerful method for helping you prioritize all your features — by comparing how much satisfaction a feature will deliver to what it will cost to implement. This template lets you easily create a standard Kano model, with two axes (satisfaction and functionality) creating a quadrant with four values: attractive, performance, indifferent, and must-be.
OKR Planning Template
Works best for:
Strategic Planning, Meetings, Workshops
The OKR Planning template helps you turn exhaustive OKR sessions into dynamic and productive meetings. Use this template to make OKR planning more interactive, guiding your team through the session with creative Ice Breakers and Brainstorms, so you can co-create your OKRs and define the key results and action plans to achieve them.
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.
Hiring Process Template
Works best for:
Operations, Org Charts, Kanban Boards
Having a hiring process in place simplifies that process each step of the way, from recruiting for the position to making finalizing offers. This simple, effective template will give you a straightforward, high-level view of where employees are as they move from applicant to new hire.