A useful founder lens is:
Pain
+
Frequency
+
Severity
+
Urgency
These four dimensions help founders judge whether a problem is merely noticeable or important enough to create action.
1. What Does “Pain” Mean?
In startup thinking, pain means the negative impact a problem creates for the customer.
Pain can appear as:
wasted time,
lost money,
frustration,
repeated manual work,
operational risk,
missed opportunities,
customer complaints,
stress,
delays,
poor outcomes.
Pain does not have to be dramatic.
A small problem repeated many times can become significant.
The key question is:
“What becomes worse because this problem exists?”
2. Pain Is Better Understood Through Behaviour
Imagine two customers.
Customer A
Says:
“This process is annoying.”
Customer B
Has created:
spreadsheets,
reminders,
manual checks,
repeated follow-ups,
extra staff effort
to manage the same problem.
Customer B demonstrates stronger pain through behaviour.
A useful principle is:
Complaints reveal opinions.
Workarounds reveal consequences.
3. Frequency: How Often Does It Happen?
Frequency measures how often the customer experiences the problem.
Consider:
Problem A
Occurs once every few years.
Problem B
Occurs every working day.
Even if Problem B is individually small, repeated exposure can create substantial accumulated cost.
For example:
5 minutes wasted once
is very different from
5 minutes wasted hundreds of times
Founders should ask:
Is this daily?
Weekly?
Monthly?
Rare?
Does it happen every transaction?
Does it affect every employee or only a few?
Frequency helps reveal the total burden of the problem.
4. Severity: What Happens When It Occurs?
Severity measures how serious the consequences are.
A high-severity problem might cause:
financial loss,
customer loss,
production stoppage,
compliance failure,
missed deadlines,
safety risk,
major operational disruption.
A low-severity problem might simply create mild inconvenience.
Ask:
“If this problem happens, how bad is the result?”
Severity is important because even rare problems can be valuable to solve when the consequence is serious.
5. Urgency: How Quickly Must It Be Solved?
A customer can have a painful problem without feeling urgency.
For example:
“We should improve this someday.”
That problem may be real.
But the customer may postpone action for months.
Compare that with:
“We need this fixed before next week's deadline.”
Urgency creates pressure to act.
Useful urgency signals include:
a deadline,
money being lost now,
customers leaving,
operations blocked,
compliance requirements,
repeated failure,
immediate business risk.
The more costly delay becomes, the more urgent the problem usually feels.
6. The Four Dimensions Can Interact
Do not evaluate each dimension in isolation.
High pain + high frequency
A repeated painful problem can create strong demand.
Low pain + very high frequency
A small annoyance can accumulate into a major productivity problem.
High severity + low frequency
A rare event can still justify action if the consequences are serious.
High pain + low urgency
The customer may care, but keep delaying the purchase.
This is why founders should avoid simple rules such as:
“Daily problems are always best.”
Context matters.
7. Four Example Patterns
Pattern 1 — Frequent but Mild
An employee repeatedly performs a small manual formatting task.
Frequency: High
Severity: Low
Urgency: Low to medium
Opportunity depends on how much total time is lost.
Pattern 2 — Rare but Severe
A system failure rarely happens, but when it does, business operations stop.
Frequency: Low
Severity: High
Urgency: High when it occurs
This can still be a valuable problem.
Pattern 3 — Painful but Postponable
A company uses an inefficient process but has tolerated it for years.
Pain: Medium to high
Urgency: Low
Sales may be difficult because the customer has learned to live with it.
Pattern 4 — Frequent, Severe and Urgent
A recurring operational issue:
happens often,
creates significant cost,
interrupts important work,
needs immediate correction.
This deserves serious investigation.
8. Look at the Cost of Doing Nothing
One of the strongest questions founders can ask is:
“What happens if the customer does nothing?”
Possible answers:
nothing significant,
more manual work,
increasing costs,
lost sales,
penalties,
customer dissatisfaction,
operational disruption,
greater risk.
If the answer is:
“Not much.”
the problem may be weak.
If the consequence grows over time, motivation to solve it may be much stronger.
9. Urgency Often Comes From a Trigger
Customers may tolerate a problem until something changes.
A trigger can turn an old problem into an urgent one.
Examples:
the company grows,
regulations change,
costs rise,
a major customer complains,
a deadline approaches,
a process breaks,
the team becomes larger,
the existing system reaches its limit.
Before the trigger:
“We can manage.”
After the trigger:
“We need a solution.”
Understanding triggers can be important for both product design and sales timing.
10. Different Customers Can Experience the Same Problem Differently
Imagine software that reduces manual reporting.
Small company
Two reports per month.
The problem may be manageable.
Larger company
Hundreds of reports across multiple teams.
The same underlying problem may become:
more frequent,
more expensive,
more complex,
more urgent.
This means problem strength depends partly on the customer segment.
The best early customer may not be the person who has the problem.
It may be the person who feels it most intensely.
11. Do Not Confuse Emotional Complaints With High Severity
Some customers complain strongly about minor issues.
Others barely complain about expensive problems because they have accepted them as normal.
Founders should investigate both:
What customers say
and
what actually happens
Ask for concrete examples:
When did this last happen?
How often?
Who was affected?
What did you do?
How long did it take?
What was the consequence?
Specific past behaviour is usually more informative than general opinion.
12. A Simple Problem-Priority Map
You can compare startup problems using four questions.
Dimension | Founder Question |
|---|---|
Pain | How much does the customer care? |
Frequency | How often does it happen? |
Severity | How serious is the consequence? |
Urgency | How quickly must it be solved? |
Then add supporting evidence:
current workaround,
money already spent,
time already lost,
willingness to change,
willingness to pay.
This gives a much stronger view than asking only:
“Does this problem exist?”
13. A Practical Example
Suppose a startup discovers that small retailers sometimes run out of important stock.
Instead of immediately assuming this is a strong opportunity, investigate.
Pain
Does stock shortage frustrate the owner?
Frequency
Does it happen every week or twice a year?
Severity
Does it merely inconvenience staff, or does it cause lost sales?
Urgency
Do owners need to correct it immediately?
Existing behaviour
Are they:
manually checking shelves,
maintaining spreadsheets,
calling suppliers repeatedly,
keeping excess inventory?
The answers reveal whether the problem deserves deeper validation.
14. Warning Signs of a Weak Problem
Be careful when:
customers rarely encounter it,
consequences are minor,
there is no urgency,
customers do nothing about it,
existing solutions are considered good enough,
no one is willing to spend time or money fixing it.
One weak dimension does not automatically kill the opportunity.
But several weak dimensions together should make founders cautious.
15. Founder Decision
When evaluating a problem, ask:
How painful is it?
How often does it occur?
What is the consequence when it happens?
How quickly does the customer need relief?
What happens if they do nothing?
What are they already doing to manage it?
Which customer segment experiences it most intensely?
Then compare evidence across opportunities.
16. The Strong Problem Signal
A particularly attractive pattern is:
Meaningful pain
+
repeated occurrence
+
serious consequence
+
pressure to act
supported by:
real customer behaviour
This still does not prove that your proposed solution will work.
It tells you that the problem deserves further attention.
17. Remember This
A problem should not be judged only by whether customers dislike it.
Understand:
Pain
→ how much it hurts
Frequency
→ how often it happens
Severity
→ how serious the consequences are
Urgency
→ how quickly action is required
The core principle is:
The strongest opportunities often appear where customers experience meaningful consequences and have a real reason to act.