What Is a Burning Issue?
A burning issue is a customer problem that:
- Affects significant revenue or user base
- Causes measurable negative outcomes
- Persists despite workarounds
- Demands attention regardless of roadmap
Not everything customers complain about is a burning issue. Burning issues are the problems that, if unsolved, threaten the business.
Identifying Burning Issues
Signal 1: Frequency × Impact
Frequency alone isn't enough. "The button color is ugly" might get mentioned often but has low impact.
Impact alone isn't enough. A critical bug affecting one user isn't a burning issue.
The combination matters:
- High frequency + High impact = Burning issue
- High frequency + Low impact = Nice to fix
- Low frequency + High impact = Investigate further
- Low frequency + Low impact = Ignore
Signal 2: Revenue at Risk
Which issues threaten:
- Deal closures? ("We won't buy until X is fixed")
- Renewals? ("We're considering alternatives because of X")
- Expansion? ("We'd pay more if you solved X")
Revenue signals cut through noise. Issues connected to money get attention.
Signal 3: Churn Correlation
Do customers who churn mention specific issues more than customers who stay?
Compare:
- Exit survey themes from churned customers
- Feedback themes from retained customers
- The gaps reveal what's driving departure
Signal 4: Support Load
Which issues generate:
- High ticket volume?
- Repeat contacts?
- Escalations?
- Long resolution times?
Support costs are a proxy for customer pain.
Signal 5: Trend Direction
Is the issue:
- Getting worse? (Burning issue, growing fire)
- Staying constant? (Burning issue, stable fire)
- Improving? (Maybe not burning anymore)
Trends reveal urgency. A rising issue needs faster action than a stable one.
Quantifying Burning Issues
For each potential burning issue, estimate:
Customer impact:
- How many customers affected?
- What's their total ARR?
- How severe is their pain?
Business impact:
- Revenue at risk (churn, failed deals)
- Support cost
- Brand/reputation risk
Effort to resolve:
- Engineering time
- Design time
- Complexity and risk
Score: (Customer impact × Business impact) / Effort
This isn't precise—estimates are rough. But it enables comparison and prioritization.
The Burning Issues Dashboard
A dedicated view of critical problems:
Columns:
- Issue name/description
- Customer count
- Revenue at risk
- Support ticket count
- Trend (increasing/stable/decreasing)
- Status (investigating/in-progress/blocked)
Sorted by: Composite score or revenue at risk
Updated: Weekly minimum, ideally real-time from data
Common Mistakes
Mistake 1: Everything is burning If everything is urgent, nothing is. True burning issues should be limited (3-5 at a time).
Mistake 2: Recency bias The issue from yesterday's angry email feels burning. The persistent issue from last quarter gets forgotten.
Mistake 3: Loud minority dominance One vocal customer can make their issue seem burning. Check breadth, not just intensity.
Mistake 4: Ignoring positive trends An issue that was burning but is improving might not need the same urgency. Reallocate.
Mistake 5: Never graduating issues Burning issues should be resolved and removed. If the same issues stay burning for quarters, something is broken.
Responding to Burning Issues
When you identify a true burning issue:
1. Assign ownership One person responsible for resolution, not a committee.
2. Create visibility Leadership and cross-functional teams should know. This isn't just a product problem.
3. Set timeline When will this be resolved? What milestones indicate progress?
4. Communicate to customers Affected customers should know you're aware and working on it.
5. Track to resolution Monitor progress. Escalate blockers. Don't let it drift.
6. Confirm resolution When resolved, verify the issue actually improved. Remove from burning list.
Preventing Burning Issues
The best burning issues are the ones that never ignite:
- Early detection: Monitor signals that indicate emerging problems
- Systematic feedback analysis: Catch patterns before they become crises
- Proactive communication: Customers who feel heard escalate less
- Quality processes: Prevent issues from shipping in the first place
Burning issues demand reaction. Great product management minimizes how often you're reacting.