Prune the Product Tree Template
Organize and prioritize product feature requests from customers and internal stakeholders.
Trusted by 65M+ users and leading companies
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.
Low-Fidelity Prototype Template
Works best for:
Design, Desk Research, Wireframes
Low fidelity prototypes serve as practical early visions of your product or service. These simple prototypes share only a few features with the final product. They are best for testing broad concepts and validating ideas. Low fidelity prototypes help product and UX teams study product or service functionality by focusing on rapid iteration and user testing to inform future designs. The focus on sketching and mapping out content, menus, and user flow allows both designers and non-designers to participate in the design and ideation process. Instead of producing linked interactive screens, low fidelity prototypes focus on insights about user needs, designer vision, and alignment of stakeholder goals.
Software Requirements Document
Works best for:
Product Development, Software Development
Unlock unmatched project clarity and effortlessly manage your software project requirements with Miro's Software Requirements Document Template. This template helps you empower your team by visually representing your project's scope, including functional and non-functional requirements. With dynamic flowchart features, you can effortlessly expand and refine your project details, ensuring a shared understanding among team members.
RICE Prioritization Template
Works best for:
Project Management, Strategic Planning, Prioritization
Teams use the RICE framework to prioritize the best course of action for their business. Using the model, you assign a RICE score to different ideas and tasks. This score tells you whether that item is something to prioritize. As a result, you make better-informed decisions about growing your business.
Perceptual Map Template
Works best for:
Marketing, Desk Research, Mapping
To shape your messaging, tailor your marketing, improve your product, and build your brand, you have to know your customers’ perceptions — what they think of you and your competitors. You can gain those insights by exploring a perceptual map. This simple, powerful tool creates a visual representation of how customers rank your price, performance, safety, and reliability. Put this template to work and you’ll be able to size up your competition, see gaps in the market, and understand changes in customer behavior and purchasing decisions.
Proto Persona Template
Works best for:
UX, UX Research, Product Design
The Proto Persona Template is tailored to capture the essence of hypothetical user segments. It encapsulates key attributes such as user needs, behaviors, and potential pain points. One of its standout benefits is its ability to foster empathy. By visualizing and understanding these preliminary user profiles, design and strategy teams can tap into a deeper connection with their target audience, ensuring that solutions resonate authentically and address genuine needs.
Feature Canvas Template
Works best for:
Design, Desk Research, Product Management
When you’re working on a new feature that solves a problem for your users, it’s easy to dive right in and start looking for solutions. However, it’s important to understand the initial user problem first. Use the Feature Canvas template to do a deep-dive into the user’s problems, the context in which they will use your feature, and the value proposition you will deliver to your users. The template enables you to spend more time exploring the problem to anticipate any potential blind spots before jumping into solutions mode.