Root Cause vs Symptom
Decompose a metric change before choosing a fix. · Product Judgment · Lesson 08 · 3 min
Root Cause vs Symptom · 3 min
Product Judgment
The metric changed
Checkout conversion falls from 62% to 49%.
That is important.
But it is not a diagnosis.
It is a symptom.
Product Judgment
Symptom
A symptom is what you observe.
Examples:
- conversion dropped
- support tickets increased
- users are cancelling
- page load time increased
The symptom tells you something changed.
It does not tell you why.
Product Judgment
Root cause
The root cause is the underlying reason the problem is happening.
For the checkout drop, possible causes include:
- payment errors
- slower page load
- confusing new copy
- traffic from a different audience
- a tracking bug
Each requires a different response.
Product Judgment
The danger of reacting too early
Imagine the team sees lower conversion and redesigns checkout.
Two weeks later, nothing improves.
Then they discover a payment provider had been rejecting one type of card.
The redesign attacked the symptom, not the cause.
Product Judgment
Decompose the problem
Ask:
Where did the behavior change?
Maybe:
Product page → cart: stable
Cart → checkout: stable
Checkout → payment success: down sharply
Now the investigation becomes much narrower.
Product Judgment
PM behavior
Strong PMs resist the urge to immediately propose fixes.
First ask:
What evidence would help us locate the cause?
Sometimes the best next step is not building.
It is diagnosis.
Remember this
Remember this
A metric change tells you where to look.
It does not automatically tell you what to fix.