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.
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.
OKR Drafting Board
Works best for:
Agile
The OKR Drafting Board (New) is a visual tool for defining and tracking Objectives and Key Results (OKRs). It provides a structured framework for setting ambitious goals, defining measurable outcomes, and aligning teams around shared objectives. This template enables organizations to articulate their strategic priorities, track progress transparently, and foster accountability and alignment across teams. By promoting focus, alignment, and agility, the OKR Drafting Board empowers organizations to achieve breakthrough results and drive continuous improvement.
Daily Standup with Jira Template
Works best for:
Daily Standup
The template is designed to improve team collaboration and streamline daily stand-up meetings by integrating Jira with Miro. This template transforms stand-ups into visual, interactive sessions, enabling teams to see real-time status updates and automatically sync changes with Jira. The key benefit of this template is its seamless integration, ensuring that all relevant information is centralized in one place. This fosters a more engaging and inclusive environment for team members, while also saving time and reducing the risk of miscommunication.
Team Charter Template
Works best for:
Meetings, Workshops, Team Meetings
A team charter is a document that outlines your team’s purpose and objectives, as well as steps you will take to reach your goals. The team charter illustrates the focus and direction for all team members. When created collaboratively, the team charter is a great way for individuals to feel even more connected to one another within the group. A team charter template is useful when you’re first establishing a new team, adding new members to an existing team, or when you need to better align regardless of your team’s tenure.
Lean Coffee by Michael de la Maza
Works best for:
Agile Methodology
Lean Coffee is a collaborative meeting format that encourages open dialogue and self-organization. Participants suggest discussion topics, vote on them, and engage in time-boxed conversations. This template provides a structured framework for facilitating Lean Coffee sessions, enabling teams to address issues, share knowledge, and make decisions collectively. By fostering inclusivity and autonomy, Lean Coffee empowers teams to drive meaningful discussions, build consensus, and drive continuous improvement.
Rose, Bud, Thorn Template
Works best for:
Retros, Agile
The Rose, Bud, Thorn template is a structured method for team reflection and feedback, designed to help teams identify positive aspects, potential opportunities, and challenges within a project or situation. One key benefit of using this template is its ability to promote balanced feedback and productive discussions, which can lead to improved team processes and outcomes.