Taco Tuesday Retrospective
Use this retrospective to inspect & adapt as a team through the medium of Tacos.
Break the ice by creating your perfect taco.
Explore how you team can add some hot sauce (Motivate each other) or cool things down (Achieve a more sustainable pace)
How to use this template:
Step 1: Prepare the Team - Pre-retro
Ensure the team involved in the retrospective understands the outcome behind the ceremony. Articulate this well in the calendar invite, encouraging people to come prepared to the session with their thoughts on how things have gone in the team recently.
Step 2: Break the ice - 5mins
Set the expectation that this session will be engaging, immersive and participate by inviting the team to participate in the icebreaker related to the retro theme. This could be anything from building characters with post-it notes, assembling tacos or simply answering a random question
Step 3: Set the stage.
Remind participants of the purpose behind the retrospective. Norm Kerth Retro prime directive built into the template is a great way to reinforce the focus on unconditional positive regard. This helps create an environment of psychological safety and a bias towards continuous improvement & action.
It should be noted that not all of the prompts / questions presented MUST be completed within the timebox for the retrospective. A good discussion on one or two prompts that result in tangible actions is better than all of them being discussed, without actions being identified.
Step 4: Generate insights - Silent reflection
The template has built in a number of question prompts or options the team may use to provoke discussion around how the team can improve. The facilitator may choose the first topic, or empower the team to choose. From there, suggest that the person who chose first nominates the next prompt.
With the prompt chosen, set a timer for 3 minutes and encourage silent reflection by requesting the team to add their thoughts onto the post-it notes related to the prompt. This will enable quieter voices to share their insight and can promote psychological safety
Step 5: Generate insights - Discussion
When the timer is up, ask the team if there insights written down that they don't understand. Invite discussion on any themes or trends that may be observed. Ensure to invite quieter voices to share their insight aloud if they wish to do so.When the team are happy to proceed, proceed to stage 6, dot voting.
Step 6: Dot vote
After allowing time for individual, silent reflection. Encourage the team to downselect to the item that most needs an action or experiment against. Do so using shapes within Miro or for bonus engagement points, encourage the team to choose random images from Google related to the theme of the retro. Dot voting with tiny tacos or pirates is more fun than just circles!
Step 7: A little less conversation, a little more action
After each question and dot vote, encourage 1 or 2 actions to be identified that the team should try in their next iteration. A retrospective that doesn't produce actionable experiments won't have much value.
When the team has between 3 and 5 small experiments to try next, you can close out the retro
Step 8: Retro your retro
With actions captured, ask the team to vote with a fist of five how they felt the retrospective went. The 'Rate your retro' section at the bottom of the template includes the detail as to how the team should do this
Step 9: The next retro
Crystallize in the teams mind when the next retro is & empower your team to decide what the theme for the next retrospective should be. There are so many options for these out there these days, you can even create one together.
This template was created by Chris Stone.
Use Miro's tool for retrospective meeting to run more inclusive and engaging retro sessions.
Get started with this template right now.
Feature Planning Template
Works best for:
Desk Research, Agile Methodology, Product Management
Features are what make a product or service fun, but adding new ones is no walk in the park. It takes many steps—ideating, designing, refining, building, testing, launching, and promoting—and just as many stakeholders. Feature Planning lets you put a smooth, sturdy process in place, so you can add a feature successfully, and spend less time and resources doing it. That makes our Feature Planning Template a smart starting point for anyone looking to add new product features, especially members of product, engineering, marketing, and sales teams.
Design Research Template
Works best for:
UX Design, Design Thinking, Desk Research
A design research map is a grid framework showing the relationship between two key intersections in research methodologies: mindset and approach. Design research maps encourage your team or clients to develop new business strategies using generative design thinking. Originally designed by academic Liz Sanders, the framework is meant to resolve confusion or overlap between research and design methods. Whether your team is in problem-solving or problem space definition mode, using a research design template can help you consider the collective value of many unrelated practices.
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.
Improve Any Product - Product Management
Works best for:
Product Management, Planning
Improve Any Product - Product Management template provides a structured framework for enhancing product quality and performance. By analyzing customer feedback, identifying improvement areas, and implementing iterative enhancements, this template empowers product managers to optimize product features and functionalities. With sections for prioritizing enhancements and tracking progress, it facilitates continuous improvement efforts, ensuring that products meet evolving customer needs and market demands.
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.
Competitor Product Research
Works best for:
Product Management, Planning
The Competitor Product Research template assists product teams in analyzing competitor offerings and market landscapes effectively. By identifying competitor strengths, weaknesses, and market trends, this template enables teams to uncover insights and opportunities for differentiation. With sections for conducting feature comparisons, SWOT analysis, and market positioning assessments, it facilitates informed decision-making and strategic planning. This template serves as a valuable resource for gaining competitive intelligence and driving product innovation and differentiation.