OpenBuilder

How to Find a Problem Worth Solving in Your Community

A practical problem-discovery guide for founders who want to build sustainable ventures around real community needs.

By Innocent Ociti

Published · Updated

The most durable venture ideas often begin close to the founder: a repeated frustration, an expensive workaround, a service people cannot reliably access, or a system that excludes capable people.

Proximity is an advantage, but it is not proof. A founder still needs to move from “this feels important” to “this is a specific problem that people are motivated to solve.”

What makes a problem worth solving?

A problem is promising when five conditions begin to appear:

  1. It is real: people can describe recent examples.
  2. It is repeated: the situation occurs often enough to matter.
  3. It has consequences: people lose money, time, opportunity, safety, trust, or dignity.
  4. People already respond: they use a workaround, pay for help, delay something else, or accept risk.
  5. You can reach the people involved: learning and distribution are possible.

You do not need certainty at the beginning. You need enough signal to justify the next round of investigation.

Begin with moments of friction

Spend one week noticing moments when people:

  • repeat the same manual task;
  • wait longer than expected;
  • travel only to access information or approval;
  • rely on one trusted intermediary;
  • lose value because timing is poor;
  • coordinate through several disconnected channels;
  • say “that is how it has always been done”;
  • pay a hidden cost that formal data does not capture.

Write observations, not ideas. “A trader made four calls to confirm one delivery” is more useful than “build a logistics app.”

Follow the workaround

Workarounds are evidence that a problem has energy. Ask what people do when the ideal option is unavailable.

A workaround may be:

  • a notebook or spreadsheet;
  • a WhatsApp group;
  • a broker or community agent;
  • borrowing equipment;
  • travelling to another district;
  • paying an unofficial convenience fee;
  • asking a relative with a smartphone;
  • doing nothing and accepting the loss.

Do not dismiss informal solutions. They often reveal the trust, flexibility, and local knowledge a new venture must preserve.

Look for the person carrying the cost

The person who experiences the inconvenience may not carry the greatest cost. A parent may wait, while a child misses school. A nurse may complete paperwork, while a clinic manager absorbs the staffing cost. A farmer may accept a low price, while a household loses planned income.

Map the people affected and ask:

  • Who feels the pain first?
  • Who pays in money or time?
  • Who makes the decision?
  • Who benefits if the situation improves?
  • Who could block a new approach?

This map helps you choose the first customer and avoid designing for an imaginary “everyone.”

Score opportunities without pretending the score is truth

Rate each observed problem from one to five on:

  • frequency;
  • severity;
  • existing spend or effort;
  • access to users;
  • founder insight or advantage;
  • ability to test cheaply;
  • potential for a sustainable model.

The score is a conversation tool, not a mathematical verdict. Investigate the high-scoring problems and the disagreements in your team.

Run a seven-day discovery sprint

Day 1: Choose one situation

Select a narrow context, such as stock ordering for independent pharmacies or fee collection for low-cost schools.

Days 2–4: Observe and interview

Speak with at least five people who recently experienced the situation. Ask about the last occurrence, current workaround, consequence, and decision process.

Day 5: Map patterns

Group repeated triggers, costs, workarounds, and contradictions. Separate what you observed from what you inferred.

Day 6: Write the problem statement

Name the specific person, situation, barrier, consequence, and evidence.

Day 7: Choose one disconfirming test

Design the smallest experiment that could show your most important assumption is wrong.

Community-first does not mean charity-only

A community-first venture can be commercial, nonprofit, cooperative, or hybrid. The defining question is whether value is created with a clear understanding of the people and systems involved.

Sustainability matters because a solution that cannot maintain delivery may deepen disappointment. Decide who receives value, who can pay, which partners benefit, and what operating model can continue without constant crisis.

The founder's discipline

Do not ask, “Is this a good idea?” Ask:

What would we need to observe to believe this problem is urgent, specific, reachable, and worth solving now?

Then go and look for that evidence. Community-first building begins with respect: listening before prescribing, testing before scaling, and making sure the venture improves the reality it claims to understand.