Decompose complex problems into root causes and effects to identify the most impactful intervention points.
The Problem Tree Method maps root causes below and consequences above a core problem, helping teams move past symptoms to find actionable leverage points.
The Problem Tree Method is a structured visual analysis tool where a core problem is placed at the trunk of a tree diagram, its root causes branch downward, and its consequences branch upward. Teams build problem trees collaboratively to move past surface-level symptoms and uncover the underlying reasons why a problem actually exists. UX researchers, project managers, social scientists, and design teams use problem trees to create shared understanding before jumping to solutions, particularly when stakeholders hold different views about what the real problem is. The method is highly participatory, typically conducted in workshop settings with sticky notes and flipcharts, making it accessible to people regardless of their analytical background. Once the problem tree is complete, teams can convert it into an objective tree by rephrasing each negative statement as a positive goal, creating a natural bridge from analysis to action. The visual format makes complex cause-and-effect relationships tangible and debatable, helping teams identify leverage points where interventions will have the greatest impact. Problem trees are especially valuable at the start of projects when clarity about the problem space is essential before resources are committed to specific solutions.
Gather your research team and stakeholders to discuss and agree on the core problem that needs to be addressed. The core problem should be clear, concise and specific.
Draw a tree structure on a whiteboard or large piece of paper. Write the core problem in the middle of the tree, which will become the trunk. The tree structure will consist of roots (causes), trunk (core problem), and branches (effects).
Discuss and brainstorm the underlying causes of the core problem. Write each cause on a sticky note and place them as the roots of the tree. As you identify more in-depth causes, you can create sub-roots that branch off from the main root.
Now identify the consequences or effects that result from the core problem. Write each effect on a sticky note and place them as branches on the tree. Sub-branches can be added for secondary or tertiary effects that arise from the main branches.
Draw lines connecting the main roots to the trunk, and then connect the branches to the trunk. This visualizes the relationships between the causes, core problem, and effects. Ensure that the connections and relationships make logical sense.
Review and analyze the completed problem tree, looking for patterns, trends, and areas for further investigation. Encourage discussions to gain insights, prioritize causes, and identify potential user pain points that need to be addressed.
Once the problem tree is complete, you can transform it into an objective tree by rephrasing negative statements into positive ones. This process helps to create constructive, solution-focused objectives for your project.
Using the objective tree, the team can now brainstorm, develop, and prioritize potential solutions that address the root causes and effects of the core problem. This sets the stage for designing and implementing effective UX improvements.
After completing a problem tree analysis, your team will have a comprehensive, visual map of the core problem, its root causes, and its consequences that all stakeholders understand and agree upon. The tree reveals which causes are within your influence and which are external constraints, enabling focused intervention design. Converting the problem tree to an objective tree provides a clear set of positive goals and potential solution directions. Teams gain alignment around what the real problem is, reducing the risk of building solutions that address symptoms rather than root causes. The visual artifact serves as a reference document throughout the project, helping new team members quickly understand the problem context. Prioritized root causes translate directly into actionable project objectives with clear rationale for stakeholder communication.
Create a separate tree for each distinct problem you are addressing -- do not try to map multiple problems on one tree.
Involve as many relevant stakeholders as possible and designate a facilitator to capture notes on the flipchart.
Ask 'why?' five times for each cause to dig deeper into root causes rather than stopping at surface symptoms.
Distinguish between causes you can influence directly and external factors beyond your control.
Convert completed problem trees into objective trees by rephrasing each negative statement as a positive goal.
Use color coding to distinguish between confirmed causes backed by data and hypothesized ones needing validation.
Validate root causes with user research data before committing resources to solutions that address them.
Revisit the tree after solutions are implemented to update your understanding and track what has changed.
Listing symptoms rather than true root causes produces a shallow tree. Use the 'five whys' technique to drill deeper into each cause until you reach factors that can be directly addressed.
Placing a consequence below the trunk or a cause above it confuses the analysis. Test each item by asking: does this lead to the problem (cause) or result from it (effect)?
Creating the problem tree without converting it to an objective tree leaves the team stuck in analysis. The objective tree is the essential bridge from understanding problems to designing solutions.
Building the tree with only designers or only managers produces a narrow view. Include users, developers, business stakeholders, and domain experts for a comprehensive perspective.
Treating workshop-generated causes as confirmed facts leads to solving the wrong problems. Mark hypothesized causes differently from data-backed ones and validate before acting.
Clear, concise statement of the core problem to be analyzed.
Listed sub-problems and contributing causes forming the tree branches.
Illustrated connections between sub-problems showing interdependencies.
Identified underlying factors at the base of the problem tree.
Stakeholder-reviewed and validated problem tree documentation.
Identified interventions addressing root causes and sub-problems.
Ranked opportunities evaluated by impact, relevance, and feasibility.
Visual diagram showing the complete problem, causes, and effects.