A problem tree is a visual tool that breaks a complex problem down into its causes and effects. You put the core problem in the middle, the causes below it as roots and the effects above it as branches. That way you see at a glance what the real problem is and where to tackle it.
Many teams jump straight to solutions, without first getting clear on which problem they are actually solving. A problem tree forces you to understand before you build. This guide explains how to make one, with a method per step and a fully worked example.
1 core
one sharply worded main problem
Roots
the underlying causes
Branches
the effects and consequences
Five whys
keep asking until the real source
The three layers of a problem tree
The central problem, sharp and in one sentence.
Why does the problem exist? Keep asking.
Which effects do you notice, for customer, team and result?
How to make a problem tree, step by step
1. Word the core problem sharply
Start with a clear sentence that names the problem, not the solution. A good core problem is concrete and measurable, and not too broad.
How to approach it: write the problem as a factual state, not as a lack of something. Not “we do not have a good website”, but “our webshop gets visitors but sells too little”. A lack of a solution is not a problem but a pre chosen answer.
2. Ask why five times
For each cause you ask why again, until you reach the real source. This method, the five whys, keeps you from getting stuck on symptoms.
How to approach it: take the core problem and ask why it exists. To each answer, ask why again. Often after three to five rounds you reach a cause you can actually tackle. Place each layer below the previous as a root.
Example: why does the webshop sell too little? Because too few of the right visitors reach a purchase. Why do they not buy? Because the site is slow and the value proposition is unclear. Why is the site slow? Because it runs on a heavy template. That is how you descend to the real cause.
3. Map the effects
Work out which effects the problem has and place them as branches above the core problem. That makes the impact visible and builds urgency.
How to approach it: ask what happens as long as the problem persists. Think of effects on your revenue, your customers, your team and your costs. Effects also help you later to measure the result of a solution.
Example: the effects of the low sales are falling revenue, rising ad costs to compensate the shortfall, few repeat purchases and frustration in the team.
4. Choose where to act
You cannot influence every cause. Mark the causes that are within your power and have the most impact. That is where you put your energy.
How to approach it: score each cause on impact and feasibility. A high impact cause you can solve yourself is your best starting point. Fighting symptoms delivers nothing lasting.
Tackle the cause, not the symptom
The power of a problem tree is that it separates causes from effects. If you only solve the effects, the problem keeps coming back. Focus on the roots and the problem disappears at the source.
A worked example
Suppose the core problem is “our webshop gets visitors but sells too little”. After asking why, four roots emerge, and they happen to point exactly to the levers that make the difference.
You attract traffic, but not the people with buying intent. The solution is findability: getting found on the terms your customer types. This is our flagship service, SEO and AIO.
Visitors drop off before they can buy anything. A fast, clean custom site with strong Core Web Vitals removes this cause at the source.
Visitors do not grasp quickly enough why they should buy from you. Strong branding and clear positioning solve this.
Whoever does not buy right away you never hear from again. With marketing automation you follow up on drop offs automatically, without extra work for your team.
See what happens here? A good problem analysis leads naturally to concrete levers. In this case to findability, speed, positioning and follow up, exactly the disciplines we bring together under one direction. Read more about our SEO approach, a custom site and marketing automation.
From problem tree to objective tree
A problem tree is not a goal in itself. Once the causes are clear, you flip the tree into an objective tree: each cause becomes a goal, and each effect a desired result.
How to approach it: rewrite each cause as a positive goal. “The site is slow” becomes “the site loads lightning fast”. “Too few of the right visitors” becomes “we get found on buying intent”. That way you translate your analysis straight into an action plan with a clear direction.
The most common mistakes
- Jumping to solutions without breaking down the problem.
- Mistaking symptoms for causes, so the problem returns.
- Wording the core problem as a lack of a solution.
- Choosing causes you cannot influence.
- Stopping at the first why, instead of asking through to the source.
From problem to solution?
In a free call we help you move from sharp analysis to a concrete approach that works. No strings attached.
Frequently asked questions about the problem tree
What is a problem tree?
According to Viralistic, a problem tree is a visual tool that breaks a complex problem down into its causes (the roots) and effects (the branches), with the core problem as the trunk in the middle.
How do you make a problem tree?
Word the core problem in a factual sentence, ask why five times to find the causes, map the effects as branches, and choose the causes you can actually influence to tackle.
What is the five whys method?
With the five whys you ask why again to each answer, until after three to five rounds you reach the real source of the problem instead of a symptom.
What is the difference with an objective tree?
An objective tree is the reverse version: each cause becomes a goal and each effect a desired result. That way you translate the analysis straight into concrete actions.
From insight to a strong approach
Move from fighting symptoms to solving the problem at the source. Book a free call with Viralistic.
