Prune the Product Tree Template
Organize and prioritize product feature requests from customers and internal stakeholders.
About the Prune the Product Tree Template
Prune the Product Tree (also known as the product tree game or the product tree prioritization framework) is a visual tool created by Luke Hohmann that helps product managers organize and prioritize product feature requests. The tree represents a product roadmap and helps your team think about how to grow and shape your product or service.
What is Prune the Product Tree
Prune the product tree helps product management teams gamify the juggling of feedback and opinions from customers and internal stakeholders.
A product tree usually has four symbolic features:
Trunk: Existing product features your team is currently building
Branches: Each branch represents primary product or system functions (you can also leave room for more branches to “grow”)
Roots: Technical requirements or infrastructure that make your listed features possible
Leaves: Each leaf represents a new idea for a product feature
You can also adapt the image as needed to suit your team discussions and business priorities. For example, apples hanging off a tree can represent a return on investment, and seed baskets under the tree can symbolize deprioritized ideas.
Create your own version of Prune the Product Tree
Making your own versions of Prune the Product Tree is easy. Miro is the perfect tool to create and share them. Get started by selecting the Prune the Product Tree Template, then take the following steps to make one.
Frame the activity for teams new to the game. For anyone who needs context, spend a few minutes guiding everyone through the exercise. The features found closest to the tree trunk represent near-term priorities. Features on the branches’ outer arms represent long-term future plans. The challenge is to prioritize near-term, current, and future product plans.
Grow each part of the tree to prioritize feature requests. You can cluster groups of features (drafted on sticky notes) around labeled branches or sub-branches (with text boxes). Avoid turning this into an idea generation activity. You want your team to focus on what features are both feasible and desirable.
Discuss each part of the tree as a group. When the tree is full of sticky note “leaves,” you can ask questions to kickstart a productive conversation. Ask each other if anyone thinks branches are too heavy. You can also ask if any feature categories are unexpected, if any feature requirements need more user research, or if the tree roots have the necessary infrastructure to make features viable. Consider dot voting with Miro’s Voting Plugin to figure out what features should be further explored.
Turn the prioritization outcomes into a product roadmap. Prune the Product Tree works as a standalone activity. You can also translate your findings into a product roadmap to shape new features you’ll focus on first from quarter to quarter.
Get started with this template right now.
Service Blueprint [Research]
Works best for:
Research & Design
A Service Blueprint is a diagram that displays the service's entire process, including people, objects, tasks, time, and processes.
Research Template
Works best for:
Education, Desk Research, Product Management
Teams often need to document findings from usability testing sessions and customer interviews into a systematic, flexible user research template. Collecting everyone’s observations into a centralized location makes it easier to share insights company-wide and suggest new features based on user needs. Research templates can be used to record quantitative or qualitative data.. When it’s your job to ask questions, take notes, learn more about your user, and test iteratively, a Research Template can help you validate your assumptions, find similarities across different users, and articulate their mental models, needs, and goals.
FMEA Analysis Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
When you’re building a business or running a team, risk comes with the territory. You can’t eliminate it. But you CAN identify it and mitigate it, to up your odds of success. Failure Modes and Effects Analysis (FMEA) is a powerful tool designed to help you manage risk and potential problems by spotting them within a process, product, or system. And you’ll spot them earlier in your process—to let you sidestep costly changes that arise late in the game or, worse, after they’ve impacted your customers and their experience.
Service Definition Canvas
Works best for:
Research & Design
The Service Definition Canvas helps you define and visualize the core components of your service. This template is perfect for outlining service interactions, identifying improvement areas, and aligning teams. Use it to create a clear and comprehensive service blueprint that enhances customer experience and operational efficiency. It's ideal for strategic planning and ensuring a cohesive understanding of service delivery among stakeholders.
Website Prototype Template
Works best for:
Prototype
Miro's website prototype template empowers teams to visualize and iterate on website designs collaboratively and efficiently, leveraging the latest AI capabilities for enhanced prototyping and seamless integration with other tools.
Six Thinking Hats Template
Works best for:
Ideation, Brainstorming
The Six Thinking Hats by Dr. Edward de Bono was created as an alternative to argument, it is designed to help teams explore and develop ideas collaboratively. Use this template to boost creative thinking and get different perspectives so you and your team can make better-informed decisions.