Complaints Are Not Demand: How to Find Problems People Will Pay to Solve

The decision underneath the tactic

A market is not created when people agree that a problem exists. It begins when the problem is frequent, costly, urgent and poorly served enough to change behaviour.

Creators often collect encouraging comments, likes and survey answers, then treat them as proof. Those signals are cheap to give. The harder evidence is sacrifice: time spent on workarounds, money paid for imperfect alternatives, repeated searching, missed outcomes or a willingness to pre-commit. This matters because a creator can execute the visible tactic perfectly while leaving the commercial question untouched. More activity then produces more noise, not more certainty. The first responsibility is to define the decision, the evidence that would change it and the cost of remaining wrong.

Use this article as a working session. Read once for the argument, then return with a real offer, customer or operating week in mind. Replace general language with names, dates, quantities and observed behaviour. A framework becomes valuable only when it changes what you will do next.

What the research suggests

Discovery research can begin before a product exists, but it should investigate real behaviour rather than invite compliments. Jobs, pains and gains become commercially useful only when they are ranked and connected to observable evidence.

Research rarely hands a small business a universal answer. Its better use is to reveal recurring failure patterns and improve the quality of a test. Evidence from usability, customer discovery, financial planning and buyer behaviour points in the same direction: reduce avoidable friction, make assumptions visible and compare what people say with what they actually do.

That does not mean copying a benchmark as a target. Context changes with audience, geography, price, trust, device and product maturity. Treat external research as a map of places worth inspecting; treat your own customer behaviour and transaction data as the ground beneath your feet.

A five-part working framework

1. Describe the job in the buyer's language, without mentioning your solution. Write the answer in a form another person could inspect. Add the evidence currently available, the assumption still exposed and the smallest next action that would strengthen or disprove it.

2. Record frequency, consequence and current workaround separately. Write the answer in a form another person could inspect. Add the evidence currently available, the assumption still exposed and the smallest next action that would strengthen or disprove it.

3. Ask for the last real example, not a prediction about the future. Write the answer in a form another person could inspect. Add the evidence currently available, the assumption still exposed and the smallest next action that would strengthen or disprove it.

4. Look for sacrifice: money, time, reputation, delay or repeated effort. Write the answer in a form another person could inspect. Add the evidence currently available, the assumption still exposed and the smallest next action that would strengthen or disprove it.

5. Choose a next test that requires a small but meaningful commitment. Write the answer in a form another person could inspect. Add the evidence currently available, the assumption still exposed and the smallest next action that would strengthen or disprove it.

Put it into practice this week

Interview five people who recently experienced the problem. Build an evidence table with exact phrases, the event that triggered action, the workaround used and what that workaround cost. A repeated story is more valuable than a high average score on a vague survey.

Time-box the exercise. A useful first pass should expose uncertainty rather than eliminate it. Mark each conclusion as observed fact, customer statement, calculation, inference or guess. This simple labelling prevents confidence from quietly outrunning evidence.

Finish with a decision record: what you decided, why, what you rejected, who owns the next action, when it will be reviewed and which signal would cause you to change course. The record protects learning when memory later edits the story.

Where creators usually lose the plot

The most common problems are not a lack of intelligence or effort. They are category errors: treating attention as demand, output as progress, gross revenue as profit, automation as strategy or length as value. Watch especially for these four traps:

Asking whether someone likes the idea. When this appears, pause the next production task and return to the decision, evidence and buyer outcome. The repair is usually a narrower question and a more observable test, not another layer of presentation.

Counting audience size as buying intent. When this appears, pause the next production task and return to the decision, evidence and buyer outcome. The repair is usually a narrower question and a more observable test, not another layer of presentation.

Treating one dramatic complaint as a segment. When this appears, pause the next production task and return to the decision, evidence and buyer outcome. The repair is usually a narrower question and a more observable test, not another layer of presentation.

Changing the product before identifying the job. When this appears, pause the next production task and return to the decision, evidence and buyer outcome. The repair is usually a narrower question and a more observable test, not another layer of presentation.

Measure learning as well as results

Track a compact scorecard: Recent problem examples, Paid or time-intensive workarounds, Interview-to-test conversion, Pre-commitment rate. Define each measure before collecting it so the meaning does not change when the result becomes uncomfortable. Use counts and rates together; a strong percentage based on three visitors is a clue, not a conclusion.

Review the scorecard on a fixed rhythm and annotate unusual events. Ask three questions: What changed? What most likely caused it? What single action will we take before the next review? Measurement without a decision is storage.

Keep a counter-metric beside every success measure. Revenue belongs beside refunds, conversion beside qualification, speed beside defects, content volume beside engaged reading. Counter-metrics prevent a local improvement from quietly damaging the whole system.

The next useful move

Validation is not a ceremony performed before building. It is a discipline for replacing attractive assumptions with progressively stronger evidence.

Do not attempt to implement every idea at once. Choose the section closest to your current bottleneck, complete one evidence-producing action and schedule the review. The linked Nexa Shelf system continues this work with structured prompts, scorecards and reusable decision pages.