What Is the Product Tree? A Visual Tool for Feature Ideation and Prioritization
The Product Tree (also known as the Product Tree Pruning exercise) is a collaborative product planning and prioritization game developed by Luke Hohmann that uses a tree metaphor to help teams and customers visually map a product’s features and discuss which ones to grow, prune, or add. By organizing features into a tree structure — trunk, branches, roots, and leaves — the exercise creates a shared visual language for product discussions that is immediately accessible to both technical and non-technical participants.
The tree metaphor is intentional: the trunk represents the core product capabilities that everything else depends on; branches represent product areas or feature categories; leaves represent individual features; and roots represent the infrastructure, platform capabilities, or foundational work that supports the product but is invisible to users.
The Structure of the Product Tree
Trunk
The trunk represents the core, most fundamental capabilities of the product — the features that define what the product essentially is and that all other features build on. Features in the trunk are the product’s essential identity: removing them would fundamentally change what the product is.
Branches
Branches represent major feature areas, product domains, or user journeys — the organizational structure of the product. A project management tool might have branches for Task Management, Collaboration, Reporting, and Integrations.
Leaves
Leaves represent individual features, user stories, or capabilities that exist within a branch. Each leaf is a specific piece of functionality: “color-code tasks by priority,” “add team members to a project,” “export reports to CSV.”
Roots
The roots represent the foundational, often invisible capabilities that the product depends on but users don’t directly experience: infrastructure, security, data architecture, performance foundations, developer APIs. The roots must be strong for the tree to grow; neglecting them weakens everything above.
How to Run a Product Tree Session
Setup
Create a large drawing of a tree (physical on paper or in a digital whiteboard tool like Miro or FigJam). Add the trunk with the product’s core value proposition. Draw branches for the major product areas. Populate existing features as leaves on appropriate branches. Draw roots representing foundational capabilities.
Collaborative Pruning and Growing
Give participants (customers, users, or internal stakeholders) a set of feature cards representing new feature ideas, and also the ability to add leaves (new feature ideas) or remove leaves (deprioritize features). Participants place new features where they believe they belong on the tree and “prune” leaves they think are less important.
Crucially, participants must make trade-offs: if they want to add a new leaf (feature), they may need to prune another to balance the tree. This forced prioritization produces more honest signal than exercises where everything can be added without consequence.
Discussion
As participants place and move features, facilitate discussion about why — the conversation reveals the reasoning behind preferences, surfaces different assumptions about what the product should prioritize, and builds shared understanding.
What the Product Tree Reveals
Which features are considered core: Features participants consistently place on the trunk or large branches are seen as fundamental.
Where growth is desired: New leaves placed consistently across participants identify high-priority development directions.
What’s perceived as overhead: Features that end up on roots rather than visible branches may be foundational but not directly valued by users.
Trade-off preferences: The pruning choices reveal which existing features are least valued when participants must make space for new ones.
Key Takeaways
The Product Tree is a powerful facilitation tool that makes product discussions accessible, visual, and concrete for participants who might find abstract prioritization discussions hard to engage with. Its tree metaphor provides an intuitive organizing structure that helps participants think about the product as a whole system — where new features fit, what would be sacrificed for them, and what foundational work is needed for the product to continue growing.