Why problems win
A product idea is usually a personal preference: “I wish this existed.” A problem worth solving is a market reality: “People are already suffering and already paying to reduce it.”
If the problem is real, the market is already trying to solve it—using hacks, substitutes, or expensive alternatives. Your job is to notice those signals.
Signals of a real problem
Use these signals like a checklist. The more boxes you tick, the more likely the problem is worth solving.
Behavior signals
- People complain repeatedly (not once).
- They’ve created workarounds (spreadsheets, WhatsApp groups, manual routines).
- They actively search for solutions (queries, forums, referrals).
- They switch tools often (churn shows dissatisfaction).
Money signals
- They already pay for alternatives (even if it’s overpriced).
- They spend time (time is money) to avoid the pain.
- They accept measurable losses (leads, retention, wastage, delays).
- Budget exists in a department / category.
“People like it” is not a signal. People changing behavior (paying, switching, repeating, referring) is the signal.
Frame the problem properly
A well-framed problem is specific, measurable, and connected to a real person in a real context. Use the international standard format below (simple, clear, and decision-friendly).
The 6-line problem statement
Define the target user/customer precisely (role + environment + frequency).
State the goal in plain language (the “job to be done”).
Name the friction: time, cost, stress, risk, skill gap, uncertainty, access.
Quantify or categorize: lost revenue, wasted hours, errors, churn, compliance risk.
List current substitutes: manual process, agency, competitor tool, “do nothing.”
Define a measurable improvement (speed, quality, cost, reliability, confidence).
Weak framing
- “People don’t have a good dashboard.”
- “They need a modern UI.”
- “We can build an app for that.”
These are solution statements. They describe the “how” before proving the “why.”
Strong framing
- Who: Export managers in small industrial suppliers.
- Goal: Track quotes → orders → dispatch without loss.
- Friction: Scattered info across WhatsApp, email, sheets.
- Cost: Missed follow-ups, delayed shipments, repeat errors.
This is testable. You can interview it, measure it, and confirm spending.
Score the problem fast
When you have multiple problems, you need a simple model to pick one. Use a 10-point score for each category below.
Problem strength (0–10)
- Frequency: How often it happens.
- Severity: How painful it is.
- Urgency: How quickly they need relief.
- Awareness: Do they already admit it’s a problem?
Market proof (0–10)
- Existing spend: Are they paying today?
- Switching: Are they open to change tools/vendors?
- Reachability: Can you access them easily to interview/sell?
- Scalability: Does the problem repeat across many users?
If Problem Strength ≥ 30/40 and Market Proof ≥ 30/40, you have a strong candidate. If not, refine the problem or find a sharper segment.
Problem vs product examples
Use this section to train your brain to separate the “pain” from the “tool.”
Example 1
Product idea: “An AI meal planner app.”
Problem worth solving: “Busy workers want healthy food, but planning + shopping + cooking costs time and decision energy daily.”
Better questions: How often? How much time? What do they do instead (delivery, skipping meals, junk)?
Example 2
Product idea: “A new CRM for small businesses.”
Problem worth solving: “Founders lose leads because follow-ups live across WhatsApp, email, and memory—creating missed revenue.”
Proof signals: existing spreadsheet tracking, reminders, multiple tools, paid agencies.
Example 3
Product idea: “A marketplace for creators.”
Problem worth solving: “Early-stage brands can’t access reliable, budget-fit talent; they waste time hiring wrong or overpaying agencies.”
Proof signals: repeated hiring cycles, poor deliverables, churn, delays in launch.
Example 4
Product idea: “A smarter inventory dashboard.”
Problem worth solving: “Operators lose money due to stock-outs and overstock because data is late, manual, and inconsistent.”
Proof signals: urgent calls, emergency orders, high wastage, manual reconciliations.
Problem worksheet
Copy-paste and fill this in. Keep answers short and real. If you can’t answer a question, that’s a research task.