Product Discovery Ideation Session
As part of Product Discovery, cross-functional product teams should be given the autonomy and freedom to explore the solution space on their own.
As part of Product Discovery, cross-functional product teams should be given the autonomy and freedom to explore the solution space on their own. Their complementary skills and perspectives lead to objectively better and more creative ideas than top-level management can come up with. But in order to harness this creativity, it takes structure. That's why I created this step-by-step ideation session template for teams to use during Product Discovery. I've incorporated proven ideas from my own experience and from others, while providing enough flexibility to make it your own.
For the "context" stage, I recommend frameworks like Impact Mapping, which can quickly bring participants up to speed in terms of recently gathered user insights. Throughout the ideation process, I encourage a "together alone" working mode, giving individuals the freedom to sort their thoughts without the bias and pressure of group thinking.
The session should end with a prioritization of the identified ideas. Here it's important to keep an iterative and experimental mindset for the following steps of your Product Discovery: Think how easy it would be to launch an experiment around this idea and how high your confidence is at the moment in terms of creating the changes in behavior you have prioritized.
This template was created by Tim Herbig.
Get started with this template right now.
Festival Retrospective
Works best for:
Retrospectives, Meetings, Agile Methodology
The Festival Retrospective template offers a unique and engaging approach to retrospectives by framing the session as a festive event. It provides elements for reflecting on past experiences, celebrating achievements, and setting goals for the future. This template enables teams to foster a positive and celebratory atmosphere, encouraging open communication and collaboration. By promoting a festive spirit, the Festival Retrospective empowers teams to strengthen bonds, boost morale, and drive continuous improvement effectively.
Sailboat Retro
Works best for:
Retrospectives, Agile Methodology, Meetings
The Sailboat Retrospective template offers a metaphorical journey through past iterations and future goals, likening the retrospective process to sailing a boat. It provides elements for identifying driving forces (winds), restraining forces (anchors), and destination (goal). This template enables teams to reflect on what propels them forward, what holds them back, and where they want to go next. By promoting visualization and metaphorical thinking, the Sailboat Retrospective empowers teams to navigate challenges, set sail towards their objectives, and steer towards success effectively.
Mad Sad Glad Retrospective
Works best for:
Brainstorming, Ideation
It's tempting to measure a sprint’s success solely by whether goals and timelines were met. But there’s another important success metric: emotions. And Mad Sad Glad is a popular, effective technique for teams to explore and share their emotions after a sprint. That allows you to highlight the positive, underline the concerns, and decide how to move forward as a team. This template makes it easy to conduct a Mad Sad Glad that helps you build trust, improve team morale, and increase engagement.
Penny Game
Works best for:
Agile
The Penny Game is a simulation exercise that illustrates the impact of batch size and work in progress on cycle time and throughput. By tracking the flow of pennies through a production system, teams learn how to identify bottlenecks, optimize processes, and improve efficiency. This template offers a practical way to explore Lean principles and drive continuous improvement, empowering teams to streamline their workflow and deliver value more predictably.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.
8 Different Ways to Organize Your Backlog
Works best for:
Agile
Explore 8 different techniques for managing and prioritizing work effectively with this template. From prioritization matrices to story mapping, it offers a comprehensive overview of backlog management strategies. By understanding the strengths and limitations of each approach, teams can tailor their backlog organization to optimize workflow, empowering teams to stay organized and focused on delivering value.