Skip to content
Kuza Ndoto Academy

Finding Problems Worth Solving

All levelsChapter 2 · Page 4 of 293 min readUpdated 15 Nov 2026

Great startups usually begin with a problem, not a product. If you solve a problem that is real, painful and frequent for people who can pay, you have a chance. If you build a clever solution to a problem nobody cares about, you will struggle no matter how good your code or design is.

What makes a problem worth solving?

Strong problems tend to share four qualities:

  • Painful: it costs people money, time, health, stress or opportunities.
  • Frequent: it happens daily or weekly, not once in a lifetime.
  • Widespread: many people (or businesses) share it.
  • Underserved: current solutions are missing, expensive, slow or annoying.

A useful test is to look at what people already do about the problem. If they have built their own workaround (a notebook, a WhatsApp group, a relative who helps), they clearly care. If they do nothing at all, the problem may not hurt enough.

Where to find problems

SourceQuestions to ask
Your own lifeWhat annoys me every week? What do I waste time or money on?
Your communityWhat do traders, farmers, boda boda riders or parents complain about?
Work and internshipsWhich tasks are done by hand on paper or spreadsheets? Where do errors happen?
WorkaroundsWhere have people stitched together a messy solution themselves?
ChangesWhat new law, technology or habit creates new problems or new possibilities?

Scoring problems

Once you have a list, score each problem on how often it happens and how painful it is. Plotting them on a simple matrix helps you see which deserve your attention first.

Painful but rare worth it only if very costly Top priority frequent and painful Ignore for now rare and mild Frequent but mild needs a very cheap, easy fix How often it happens (frequency) Pain (cost, stress) low high
Figure 1. A problem-scoring matrix. Start with problems in the top-right box: people meet them often and they hurt.

For a more detailed comparison, score each problem from 1 to 5 on pain, frequency, number of people affected and willingness to pay, then add the scores. The numbers are rough, but they force you to compare honestly rather than follow excitement.

Example

Kevin, 24, lists problems he noticed while working at his uncle's hardware shop in Thika:

ProblemPainFrequencyPeople affectedWilling to payTotal /20
Tracking which customers owe money on credit554418
Finding a plumber for customers323311
Shop looks old-fashioned12317

Credit tracking scores highest: his uncle loses money every month because of forgotten debts written in a notebook. Kevin decides to investigate this problem with other shopkeepers before thinking about any app.

Write a clear problem statement

Before moving on, describe the problem in one or two sentences, without mentioning your solution:

[Who] struggles to [do what] because [why], which costs them [impact].

For Kevin: "Owners of small hardware shops struggle to keep track of customers who buy on credit because records are kept in paper notebooks, which leads to forgotten debts and lost income every month."

Common mistake

Starting with a solution you love ("an app for X") and then searching for a problem to justify it. Another trap is solving a problem only you have. Your own frustration is a great starting point, but check that many others feel it too.

Key points

  • Strong problems are painful, frequent, widespread and poorly served by current options.
  • Look for existing workarounds; they show that people care enough to act.
  • Score and compare problems on a matrix or simple table before choosing one.
  • Write a problem statement that names who, what, why and the impact, without mentioning a solution.
Up next · IdeationGenerating IdeasTechniques for turning problems into solution ideas.
→

Tip: use the ← and → keys to move between pages.