A business cannot address every need mentioned in research. Designing a business requires choosing which customer outcomes deserve attention and which you can deliver with available resources. Before dreaming up features, revisit pillar 1 on defining the problem and customer segmentation. Needs should be written from the customer's desired outcome, not as a feature of your product [R05].
Distinguish needs, problems, wants, and solutions
- Need: “I need to finish lunch during my break so I can return on time.”
- Problem: “Existing deliveries often arrive late in my area.”
- Want or preference: “I would prefer several menu choices.”
- Suggested solution: “There should be an app with live tracking.”
The final statement does not establish the underlying need. Nontechnical solutions may exist: a fixed delivery window or advance ordering. GOV.UK recommends expressing needs in terms of tasks and outcomes, supported by research, without assuming the delivery mechanism [R05].
Step 1. Build a traceable inventory
For each need, record the group, context, task, obstacle, consequence, current alternative, supporting evidence, contradictory evidence, and source. Keep participants' words separate from the team's inferences. When someone says “I would like an app,” investigate the job they are trying to do. It is fine to mark needs as unverified, but not to present them as established findings.
Step 2. Group by functional, social, and emotional job
One buying decision may involve several outcomes: receiving lunch at a usable time (functional), avoiding disruption to a meeting (social or organizational), and reducing daily uncertainty (emotional). These lenses can reveal value, but they are not a compulsory checklist for every business. The Value Proposition Canvas uses jobs, pains, and desired gains to structure a customer profile [R03].
Step 3. Assess importance and ability to respond
Use explicit criteria such as the consequence of failure, frequency, size of the affected segment, available alternatives, strength of evidence, ability to deliver, and expected cost. Do not invent scores. An “importance of 5/5” without evidence is still an opinion. If information is missing, show a range or write “unknown.”
| Need (hypothetical) | Available evidence | Consequence | Delivery difficulty | Provisional decision |
|---|---|---|---|---|
| Receive order during break | Three reported cases; nonrepresentative sample | High for those cases | Medium | Investigate and design |
| Customize every ingredient | One isolated request | Unknown | High | Do not promise yet |
| Know the price before buying | Repeated questions observed but not measured | Medium | Low | Make prices clear |
This table is illustrative. Three interviews do not establish market prevalence. Challenge every conclusion using evidence evaluation and bias checks.
Step 4. Prioritize without confusing importance with scope
A need can be important and still fall outside the initial offer due to excessive cost, legal restrictions, or limited delivery capacity. Create three groups: “include in initial design,” “investigate before committing,” and “out of scope for now.” Preserve the reasons and decision owner. Do not turn a strategic ranking into a claim that demand has already been validated.
When these offering decisions become concrete launch work, see how to define milestones, deliverables, and scope using MoSCoW. Prioritizing execution scope comes later and does not establish that a customer need has been validated in the market.
Step 5. Check compatibility with your proposition
An offer centered on punctuality might prioritize a realistic delivery window over dozens of variations. Compare possible benefits against production constraints. This choice informs the value proposition, the customer journey, and key capabilities.
How to write a need that supports design
Try this pattern: “When [context], [segment] needs [outcome] so that [desired consequence].” For example: “When lunch breaks last 45 minutes, employees staying in the office need a reliable arrival time so they do not waste their break waiting.” Mark which parts come from evidence and which are inferences.
Mistakes and limits
Do not prioritize by number of feature requests without studying sampling bias; treat imaginary personas as measured data; invent numeric scores and present them as science; or promise a solution for every complaint. When knowledge is insufficient, return to research. Experimental validation of promises belongs to pillar 3.
Decide when two needs compete
Imagine “on-time delivery” and “fully customizable menus” both attract positive opinions, but the kitchen cannot guarantee both within the planned budget. Do not settle the conflict by counting positive comments: compare consequences, frequency, marginal cost, contradictory evidence, and the most affected segment. Then record a revisable decision: “We will prioritize punctuality; we will reconsider customization if we find recurring cases and a way to provide it without breaking delivery windows.” State what future evidence would change the priority, so a provisional decision does not become a permanent rule without support.
What you should have when you finish
A segment-based inventory with evidence and contradictions, grouped needs, visible prioritization criteria, scope decisions, and open questions. Then connect these decisions to a concrete value proposition. Sources: [R03][R05].
Bibliography and references
- [R05] GOV.UK — Learning about users and their needs. https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs — Necesidades reales, formulación basada en resultados y evidencia.
- [R03] Strategyzer — Value Proposition Canvas. https://www.strategyzer.com/library/the-value-proposition-canvas — Jobs, pains, gains y mapeo de la oferta; encaje hipotético.