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.
SaaS Implementation Timeline
Works best for:
Agile
The SaaS Implementation Timeline template offers a visual roadmap for planning and tracking the implementation of Software as a Service (SaaS) solutions. It provides a structured framework for defining milestones, allocating resources, and monitoring progress. This template enables organizations to manage SaaS deployments effectively, ensuring successful adoption and realization of business value. By promoting transparency and accountability, the SaaS Implementation Timeline empowers teams to deliver projects on time and within budget, driving organizational agility and competitiveness.
Conversion Funnel Backlog Template
Works best for:
Decision Making, Product Management, Prioritization
If you’re working on a product that has clear conversions, then it can help to structure your backlog around the conversion funnel to make sure you’re reaching your audience. Creating a conversion funnel backlog brings together information around potential pain-points in your funnel and opportunities for growth. Once you’ve identified that information, it becomes easier to prioritize. You and your team can use the conversion funnel backlog to focus on conversion, retention, and referral, or to tweak your workflow in more mature products.
HEART Framework Template
Works best for:
Desk Research, Project Management, User Experience
Happiness, Engagement, Adoption, Retention, and Task Success. Those are the pillars of user experience — which is why they serve as the key metrics in the HEART framework. Developed by the research team at Google, this framework gives larger companies an accurate way to measure user experience at scale, which you can then reference throughout the product development lifecycle. While the HEART framework uses five metrics, you might not need all five for every project — choose the ones that will be most useful for your company and project.
Huddle Board Template
Works best for:
Meetings
The Huddle Board Template is a digital and interactive tool that fosters seamless team collaboration. Mimicking the traditional physical boards used in office environments provides a visual platform where teams can organize tasks, share updates, and track progress. One standout benefit of this template is its real-time collaboration feature. With it, team members can instantly share feedback, change tasks, or raise queries, ensuring everyone is aligned and updated, significantly reducing miscommunication and streamlining project execution.
Starfish Retrospective
Works best for:
Retrospectives, Agile Methodology, Meetings
The Starfish Retrospective template offers a structured approach to retrospectives using the metaphor of a starfish. It provides elements for identifying what to start, stop, continue, do more of, and do less of. This template enables teams to reflect on past iterations, identify actionable insights, and prioritize improvements. By promoting clarity and focus, the Starfish Retrospective empowers teams to drive meaningful change and continuous improvement effectively.
Product Vision Statement
Works best for:
Product Management, Planning
The Product Vision Statement template helps product teams articulate clear and inspiring visions for product development. By defining long-term goals, market aspirations, and customer value propositions, this template aligns teams around a shared vision for success. With sections for outlining strategic objectives, guiding principles, and success metrics, it provides clarity and direction for product development efforts. This template serves as a compass for product teams, guiding them towards meaningful outcomes and driving innovation and growth.