Founders do not need to find a completely new problem.
They need to find a problem that is:
real
→ important
→ frequent or costly
→ poorly solved
→ worth acting on
1. Start With Problems, Not Ideas
Many founders begin with:
“What should I build?”
A better starting question is:
“What problems are people repeatedly struggling with?”
Products can change.
Technologies can change.
Business models can change.
But if the underlying customer problem is meaningful, the startup has something worth investigating.
A strong early sequence is:
Observe
→ Identify friction
→ Understand the customer
→ Measure the pain
→ Test whether action follows
2. What Makes a Problem Worth Solving?
A useful problem usually has several characteristics.
Frequency
How often does the problem occur?
A problem that happens every day may create more motivation than something that happens once a year.
Severity
How painful is the consequence?
Does it cause:
lost money,
wasted time,
operational failure,
frustration,
risk,
missed opportunities?
Urgency
Does the customer need to solve it now?
Some problems are painful but easy to postpone.
Others demand immediate action.
Existing Effort
What are customers already doing to solve it?
If they are already spending:
money,
time,
staff,
tools,
manual effort,
the problem may be meaningful.
3. The Core Lens
A simple early framework is:
Frequency
+
Severity
+
Urgency
Think of these as lenses rather than a mathematical formula.
High frequency + high severity + high urgency
Usually worth investigating deeply.
High frequency + low severity
Could still matter if the accumulated cost is large.
Low frequency + high severity
Can matter strongly in areas involving safety, financial loss, compliance, or major risk.
Low frequency + low severity
Usually harder to turn into a strong startup opportunity.
Context matters.
4. Pain vs Inconvenience
Consider two customer statements.
Customer A
“It would be nice if this were easier.”
Customer B
“Every week, our team loses several hours doing this manually.”
Both reveal friction.
But Customer B shows:
repetition,
cost,
behaviour,
stronger motivation.
Founders should learn to distinguish:
nice-to-have improvement
from:
problem customers actively want removed
5. Look for Repeated Workarounds
Customers often reveal important problems without saying:
“I need a startup to solve this.”
Watch what they do.
Examples include:
spreadsheets used for tasks they were not designed for,
repeated copying and pasting,
manual approvals,
employees moving data between systems,
WhatsApp or email replacing proper workflows,
multiple tools stitched together,
extra staff hired to manage repetitive work,
handwritten processes,
repeated phone calls.
A workaround is important because it shows:
the problem exists
+
the customer is already trying to solve it
That can be stronger evidence than a survey answer.
6. Look for Cost
Pain becomes easier to understand when you identify what the problem costs.
The cost may be:
Money
lost revenue,
unnecessary spending,
penalties,
expensive labour.
Time
repetitive work,
slow approvals,
long waiting.
Risk
mistakes,
compliance failure,
fraud,
missed deadlines.
Opportunity
customers lost,
deals delayed,
employees unable to focus on higher-value work.
Emotional friction
stress,
frustration,
uncertainty,
confusion.
Not every cost needs to be financial.
But the bigger the consequence, the stronger the reason to act.
7. Search Where Friction Is Normalized
Some of the best startup opportunities can hide inside processes people simply accept.
Common phrases reveal this:
“That is just how the industry works.”
“We always do it manually.”
“It takes a few days.”
“We need three people to check it.”
“Everyone uses spreadsheets.”
“Customers always complain about that.”
“We have no better option.”
When inefficient behaviour becomes normal, people may stop recognizing it as a problem.
Founders can ask:
“Why does this have to work this way?”
8. Look for Expensive Alternatives
A market may already have solutions.
That does not mean the problem is solved well.
Customers may be using solutions that are:
too expensive,
too complex,
too slow,
unreliable,
difficult to integrate,
designed for larger companies,
missing important workflows.
Competition can actually confirm that customers are willing to solve the problem.
The key question becomes:
“What remains poorly solved?”
9. Talk to Customers With Strong Pain
Suppose 100 people experience a problem.
But only 10 experience it intensely.
Those 10 may be more useful early customers.
Why?
They may be more willing to:
explain the problem deeply,
test something imperfect,
change behaviour,
tolerate early product limitations,
pay.
These users can become early adopters.
The goal is not immediately to serve everyone.
It is first to understand where the strongest pain exists.
10. Behaviour Is Stronger Than Complaints
Customers complain about many things.
Not every complaint creates a startup opportunity.
Compare:
Complaint
“This system is annoying.”
Behaviour
The customer:
buys another tool,
creates a spreadsheet,
hires someone,
spends hours fixing the issue,
repeatedly searches for alternatives.
The second situation contains stronger evidence.
Founders should ask:
“What is the customer already doing because this problem exists?”
11. Problem Discovery Example
Imagine you are studying small manufacturing companies.
You notice managers repeatedly coordinating maintenance through:
paper records,
calls,
spreadsheets,
messaging groups.
Instead of immediately building maintenance software, investigate.
Ask:
How often does coordination fail?
What happens when it fails?
Who experiences the pain?
What does downtime cost?
What tools are already used?
Who decides whether to buy a solution?
You may discover that:
maintenance tracking itself is not the biggest pain
but:
knowing which equipment needs urgent attention is
That changes the startup opportunity.
Problem discovery means going deeper than the visible symptom.
12. Symptoms vs Root Problems
A customer might say:
“We need a better dashboard.”
That is a requested solution.
Ask why.
Perhaps the real problem is:
“Managers cannot identify delayed orders quickly.”
Go deeper again.
Maybe:
“Data comes from three disconnected systems.”
The visible request was a dashboard.
The deeper problem was fragmented information.
A useful questioning chain is:
What happened?
→ Why is that difficult?
→ What causes it?
→ What happens because of it?
Do not stop at the first answer.
13. Avoid These Problem-Discovery Traps
Starting from technology
“Where can I use AI?”
Better:
“Which important problem could AI improve?”
Solving your own problem and assuming everyone shares it
Your experience creates a hypothesis, not proof.
Choosing a huge market before finding strong pain
A large market with weak customer motivation can still be difficult.
Trusting compliments
“Great idea” is not demand.
Looking only for completely new problems
Improving badly solved existing problems can be valuable.
Ignoring existing alternatives
Alternatives reveal how customers currently behave.
14. A Simple Problem Scorecard
Before committing deeply, rate the problem qualitatively.
Frequency
How often does it happen?
Severity
How damaging is it?
Urgency
How quickly must it be solved?
Existing spend
Are customers already using money or resources?
Workarounds
Are customers actively compensating for the problem?
Dissatisfaction
Are current solutions inadequate?
Access
Can you reach affected customers to learn?
Capability
Can your team realistically explore the space?
This is not meant to mechanically choose a startup.
It helps compare opportunities more clearly.
15. Founder Decision
When you notice an interesting problem, do not immediately ask:
“Can we build a product?”
Ask:
Who experiences this problem most strongly?
How frequently does it happen?
What happens when it is not solved?
What do customers already do about it?
What does that behaviour cost them?
Why are existing alternatives insufficient?
What evidence would show the problem is not important enough?
Then investigate.
16. The Opportunity Signal
A particularly interesting pattern is:
Important problem
+
repeated behaviour
+
poor alternatives
+
willingness to act
This does not guarantee a successful startup.
But it gives founders a stronger starting point.
17. Remember This
Do not search only for clever ideas.
Search for meaningful friction.
Look for customers who are already paying a price because the problem exists.
That price may be:
money
→ time
→ risk
→ effort
→ lost opportunity
The core principle is:
A problem becomes interesting when customers care enough to do something about it.
Your job is to discover where that behaviour already exists.