The way you describe a problem determines the questions you ask. If you write it as a disguised solution, you may miss an opportunity before you understand it.
Why a good problem definition changes your research
“We need an app” is a possible technological answer. “Managers of small restaurants lose information when reservations arrive through different channels” is a statement about a situation that can be investigated. The first directs attention to screens and features; the second directs it to people, tasks, contexts, and consequences. Early research should seek to understand how an activity is currently performed and what difficulties arise, as GOV.UK proposes for discovery [R02, R12].
Defining a problem properly does not require finding the perfect sentence before talking to anyone. The definition is provisional: it begins as a question, changes with evidence, and may lead you to realize that the original problem was not the main one.
Distinguish the need, problem, symptom, cause, and solution
These concepts are related but not interchangeable. A need expresses what a person needs to accomplish, such as confirming reservations reliably. A problem is a meaningful obstacle to that goal, such as losing requests when calls and messages arrive simultaneously. A symptom is an observable manifestation, such as two customers arriving for the same table. A possible cause is that several employees record changes in different systems; this needs checking because other causes may exist. A solution is an intervention, such as centralizing records.
A useful chain is: “The person is trying to do X, in context Y; they face obstacle Z; this causes consequence C. We believe it happens because of cause H, which remains unconfirmed.” Do not state the cause and solution as if they were established facts.
| Weak formulation | Researchable formulation |
|---|---|
| “There is no good reservation app” | “Under what circumstances are reservations lost or duplicated?” |
| “Customers want more modern deliveries” | “What situations cause delays, and what are their consequences?” |
| “People need our course” | “What task do they want to learn, and what barriers do they face today?” |
Four components of a problem statement
1. Person or group. Not “everyone”: describe who experiences the situation. It may be the employee doing a task, the owner bearing a cost, or a family organizing its shopping.
2. Job or goal. What are they trying to achieve? A manager wants to handle reservations without mistakes; a family wants meals available throughout the week. You should be able to explain the goal without mentioning your product.
3. Context and obstacle. When does it happen? With what resources and constraints? The same restaurant may run smoothly Monday through Thursday and have problems during its busiest hours. Context can completely change an opportunity's relevance.
4. Consequence. What happens when the issue goes unresolved? Wasted time, rework, missed sales, stress, waste, or interruptions. Not every inconvenience justifies a purchase: you need to investigate its magnitude and the cost of tolerating it.
An initial template is: “When [group] tries to [task] in [situation], they encounter [obstacle], leading to [observed or unverified consequence].” This template is a writing aid developed for this guide, not an officially validated formula from any source.
How to assess severity, urgency, and frequency without inventing metrics
A problem's importance can be examined through several dimensions:
- Frequency: Does it happen daily, monthly, or only during exceptional events? An infrequent need may still matter greatly if the consequences are serious.
- Severity: What loss or harm does it cause? Distinguish minor annoyances from critical failures.
- Urgency: How long can someone wait to resolve it?
- Reach: How many people or activities does it affect?
- Alternatives: What does it cost to keep using the current method?
- Economic decision-maker: Who actually bears the cost, and who could authorize a purchase?
If you use your own scale—for instance, one to five for severity—document what each score means and do not present it as a universal scientific measure. Scales help compare cases within a study, but they cannot replace observations or economic estimates.
How to investigate causes without deciding them in advance
First, reconstruct the most recent incident: what was happening, who was involved, which tools were used, what occurred, and what the team did to recover. Then ask what other circumstances might explain the failure. A presumed cause may be incomplete: perhaps reservations are not lost because the team uses paper, but because shifts change and there is no shared procedure.
Compare at least two perspectives when possible: that of the employee performing the task and the manager seeing the outcomes; consider customers and operational records too. Contextual observation can reveal interruptions, unmentioned steps, and improvised workarounds [R05]. A responsible conclusion might be “We identified three possible mechanisms; we still need to measure their frequency,” not “The cause is proven.”
To learn how people describe real incidents without being led toward a cause, see how to conduct discovery interviews.
When turning findings into a test, separate observations from assumptions before writing testable hypotheses.
A problem is not always a commercial opportunity
You may find that the problem exists but occurs rarely, has little consequence, or would cost more to solve than to tolerate. You may also identify an important problem for someone who has neither a budget nor purchasing authority. In that case the need is real, but you have not yet demonstrated a business opportunity.
The SBA recommends investigating demand, market size, prices, and existing alternatives [R01]. These questions complement the problem definition but should not be introduced prematurely as justification for your product. First identify the problem; then assess whether a reachable opportunity exists.
Once you have enough evidence to assess commercial potential, use the guide to assessing a business opportunity before deciding whether to invest more.
Distinguishing a repeated complaint from a robust finding requires evaluating evidence without reinforcing our own biases.
Worked example: appointments at a barbershop
Initial idea: “A platform that automates barbershop appointments.” Observation shows that many customers walk in without an appointment and that the shop fills gaps between services; not everyone wants to book. On Fridays, however, a small group of customers requests specific times, and the manager receives messages while serving someone else. Replies are sometimes late, and a booking is lost.
A revised problem statement is: “In barbershops with high demand for appointments at certain times, staff serving customers struggle to respond to and confirm changes promptly; some requests do not become bookings.” Questions remain: What proportion of appointments is lost? Would another employee handle the situation better? How many shops share this pattern? What do their customers consider acceptable?
This reformulation does not declare that software must be built. It opens up operational and commercial alternatives that will be considered in the business design pillar.
Common mistakes in writing a problem statement
Defining the problem as the absence of your product. “We lack a platform” does not establish a need. Treating symptoms as causes. “Deliveries are late because employees are disorganized” may hide excess demand or conflicting instructions. Generalizing from one case. One conversation can reveal possibilities, not estimate prevalence. Confusing importance with willingness to pay. Someone may care deeply about a problem and still not want to pay for your solution. Removing contradictions. If some users handle the task successfully, investigate what makes their circumstances different.
What you should have when you finish
A revisable problem statement covering person, task, context, obstacle, and consequence; a record separating symptoms from possible causes; real examples that support it and cases that contradict it; and unanswered questions about frequency, severity, and reach. This will form the basis for interviews, segmentation, and market analysis—not a claim that the product has already been defined.
For more detail, see how to identify, organize, and prioritize customer needs.
Main sources: [R02] GOV.UK, discovery; [R05] contextual observation; [R12] understanding user needs; [R01] SBA, market research. Conceptual distinctions and the operational template are original editorial syntheses; examples are hypothetical.
Bibliography and references
- [R02] GOV.UK — User research in discovery. https://www.gov.uk/service-manual/user-research/user-research-in-discovery — Usuarios, tareas actuales, problemas, métodos y resultados de discovery.
- [R12] GOV.UK — Learning about users and their needs. https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs — Necesidades, métodos actuales y barreras en el contexto del servicio.
- [R05] GOV.UK — Contextual research and observation. https://www.gov.uk/service-manual/user-research/contextual-research-and-observation — Observación de tareas en entornos reales.
- [R01] U.S. Small Business Administration (SBA) — Market research and competitive analysis. https://legacy.sba.gov/es/guia-de-negocios/planifique-su-empresa/investigacion-de-mercado-y-analisis-competitivo — Demanda, tamaño, ubicación, competencia, investigación primaria/secundaria. Aunque el enlace incluye
/es/, el recurso puede presentarse en inglés.