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.
Zoom Levels Template
The Zoom Level Template is a tool to examine a problem from various perspectives. For more innovative solutions, consider the issue broadly. Ascending the ladder enables you to broaden your perspective (ask, 'How might we?'). When confronted with an overly broad scope that hinders progress, descending the ladder helps narrow your focus (ask 'What if we narrowed?').
Timeline Template
Works best for:
Project Management, Flowcharts, Project Planning
A timeline displays a chronological order of important dates, and scheduled events. Timelines help product managers, project managers, and team members tell visual stories about progress and obstacles. Timelines enable teams to see at a glance what happened before, what progress is happening now, and what needs tackling in the future. Projects or products with specific purpose or deliverables should be based on a timeline to be successful. Use the timeline as a shared reference for start dates, end dates, and milestones.
Eisenhower Matrix Template
Works best for:
Leadership, Strategic Planning, Prioritization
Have an overwhelming list of to-dos? Prioritize them based on two key factors: urgency and importance. It worked for American president Dwight D. Eisenhower, and it can work for you—this decision-making framework will help you know where to start and how to plan your day. With our template, you can easily build an Eisenhower Matrix with a quadrant of key areas (Do, Schedule, Delegate, and Don’t Do) and revisit it throughout the day as your priorities change.
Project Status Report Template
Works best for:
Project Management, Documentation, Project Planning
When a project is in motion, the project manager must keep clients and shareholders updated on the project’s progress. Rather than waste time with constant meetings, leaders can send out weekly or daily project status reports to keep everyone informed. You can use the Project Status Report Template to streamline the report creation and distribution process.
Website Wireframing Template
Works best for:
Wireframes, User Experience
Wireframing is a method for designing a website at the structural level. A wireframe is a stylized layout of a web page showcasing the interface elements on each page. Use this Wireframe Template to iterate on web pages quickly and cheaply. You can share the wireframe with clients or teammates and collaborate with stakeholders. Wireframes allow teams to get stakeholder buy-in without investing too much time or resources. They help ensure that your website’s structure and flow will meet user needs and expectations.
What's on Your Radar Template
Works best for:
Business Management, Operations, Strategic Planning
Do you or your team feel overburdened by tasks? Having trouble focusing on particular problems? What’s on Your Radar is a thought exercise in which you plot ideas according to their importance or relevance. Designers and teams use what’s on your radar to ensure that their ideas are within the scope of a given project. They also rely on the method to assess whether a given solution is likely to solve the problem at hand. But even if you’re not a designer, the method can help assign priorities and ground your ideas in reality.