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.
Product Vision Statement
Works best for:
Product Management, Planning
The Product Vision Statement template helps product teams articulate clear and inspiring visions for product development. By defining long-term goals, market aspirations, and customer value propositions, this template aligns teams around a shared vision for success. With sections for outlining strategic objectives, guiding principles, and success metrics, it provides clarity and direction for product development efforts. This template serves as a compass for product teams, guiding them towards meaningful outcomes and driving innovation and growth.
4P Marketing Mix Template
Works best for:
Marketing, Brainstorming, Workshops
Product, Place, Promotions, and Price. Starting with this template (and those 4Ps) you can choose the best way to take your product or service to market. The secret is to create just the right mix—deciding how much each P needs in terms of investment, attention, and resources. That will help you build your strengths, adapt to the market, and collaborate with partners. And our tool is the perfect canvas to create your marketing mix and share with teams and across your organization.
Service Experience Observation Sheet
Works best for:
Research & Design
The Expanded Service Blueprint provides a detailed view of your service processes and interactions. This template is ideal for comprehensive service analysis and improvement. Use it to align teams, visualize the customer journey, and identify opportunities for optimization. It's perfect for enhancing service delivery, fostering collaboration, and ensuring a seamless and efficient service experience for your customers.
Agile Transition Plan Template
Works best for:
Agile Methodology, Agile Workflows
An Agile transformation roadmap can help you, your team, and your organization transition from rigid compliance-heavy methods to the more flexible Agile way of doing things incrementally. From requirements to integrations to security, you can map out your organization's moving parts as “swim lanes” that you can then update regularly. Use your roadmap as a way to tell the story of how you see your product growing over a period of time. Get buy-in without overselling and keep your roadmap simple, viable and measurable. By using an Agile transformation roadmap, you can avoid getting bogged down in details and instead invest in big-picture strategic thinking.
Product Canvas Template
Works best for:
Desk Research, UX Design
Product canvases are a concise yet content-rich tool that conveys what your product is and how it is strategically positioned. Combining Agile and UX, a project canvas complements user stories with personas, storyboards, scenarios, design sketches, and other UX artefacts. Product canvases are useful because they help product managers define a prototype. Creating a product canvas is an important first step in deciding who potential users may be, the problem to be solved, basic product functionality, advanced functionalities worth exploring, competitive advantage, and customers’ potential gain from the product.
Sailboat Template
Works best for:
Agile Methodology, Meetings, Retrospectives
The Sailboat Retrospective is a low-pressure way for teams to reflect on how they handled a project. By defining your risks (the rocks), delaying issues (anchors), helping teams (wind), and the goal (land), you’ll be able to work out what you’re doing well and what you need to improve on for the next sprint. Approaching team dynamics with a sailboat metaphor helps everyone describe where they want to go together by figuring out what slows them down and what helps them reach their future goals.