Opportunity Discovery and Problem Framing

Introduction

Entrepreneurial products rarely fail because the team cannot build them. They more often fail because the team builds something that is insufficiently valuable, poorly timed, difficult to adopt, or directed at a problem that users do not consider important. Product prototyping therefore begins before sketches, wireframes, or engineering specifications. It begins with disciplined inquiry into people, situations, unmet needs, institutional conditions, and possible opportunities.

Opportunity discovery is the process of identifying situations in which a meaningful user problem, a feasible intervention, and a viable value-creation pathway may coexist. Problem framing is the process of defining that situation precisely enough to guide investigation and prototyping without prematurely prescribing a solution. Together, they help entrepreneurs move from vague observations—such as “customers need a better app”—to testable propositions about who experiences what difficulty, under which circumstances, with what consequences, and why existing alternatives are inadequate.

This chapter integrates design thinking, systems thinking, jobs-to-be-done, customer discovery, and problem-framing methods. These perspectives are complementary rather than interchangeable. Design thinking emphasizes human experience and iterative learning; systems thinking examines interdependence and unintended consequences; jobs-to-be-done focuses on the progress users seek; customer discovery tests assumptions with evidence; and problem framing establishes a useful boundary around the opportunity.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain opportunity discovery as an evidence-based entrepreneurial activity.
2. Distinguish symptoms, problems, needs, jobs, solutions, and opportunities.
3. Apply design-thinking and systems-thinking perspectives to ambiguous situations.
4. Formulate jobs-to-be-done and customer-problem hypotheses.
5. Plan and conduct ethically sound customer-discovery activities.
6. Frame problems using user, context, need, consequence, and constraint.
7. Prioritize opportunities using desirability, feasibility, viability, and ethical considerations.
8. Translate a validated problem frame into a focused prototyping brief.

1. From Observations to Opportunities

An observation is something noticed: commuters abandon a ticketing kiosk, nurses repeatedly re-enter patient information, or small retailers postpone inventory updates. An observation is not yet a problem statement. A problem exists when a person or organization experiences an undesirable gap between a current state and a desired state. The gap may involve time, cost, risk, effort, uncertainty, quality, access, identity, or emotion.

A need is a condition that users require or value, such as confidence, speed, safety, control, or belonging. A job is the progress a user is trying to make in a particular situation. A solution is an intervention intended to address a problem or enable a job. An opportunity is a promising, evidence-supported possibility for creating value by addressing a significant problem in a feasible and sustainable manner.

These concepts should not be collapsed:

A useful discipline is to delay solution language. “Users need an artificial-intelligence chatbot” is a solution assertion. “Users need timely answers when staff are unavailable” is a need hypothesis that permits several possible solutions.

Opportunity as a set of hypotheses

Early opportunity work is not certainty-seeking; it is uncertainty reduction. A team may hold assumptions about:

• the target user and other affected stakeholders;
• the triggering situation;
• the frequency and severity of the difficulty;
• current workarounds and competing alternatives;
• willingness and ability to adopt or pay;
• technical, legal, organizational, and environmental constraints;
• who makes, influences, and uses the purchasing decision.

Each assumption should eventually be connected to evidence. Evidence does not mean collecting opinions that confirm an attractive idea. It means seeking observations, behavior, records, experiments, and counterexamples that can distinguish among competing explanations.

2. Design Thinking for Opportunity Discovery

Design thinking is a human-centered, iterative approach to addressing complex or poorly defined challenges. Popular versions describe stages such as empathize, define, ideate, prototype, and test. These stages are best understood as activities that may loop and overlap rather than as a rigid linear process.

Empathize and understand

The purpose of empathy work is not merely to be sympathetic. It is to understand behavior, context, language, motivations, constraints, and emotional experience from the participant’s perspective. Relevant methods include contextual interviews, observation, diary studies, journey mapping, artifact analysis, and participatory workshops.

A strong inquiry distinguishes what people say, do, think, and feel. These dimensions may conflict. A participant may say that price is the main concern, while observed behavior shows that reliability determines the purchase. Such discrepancies are not errors to be eliminated; they are prompts for deeper investigation.

Define and synthesize

Researchers organize evidence into patterns. Useful synthesis tools include affinity mapping, persona hypotheses, journey maps, service blueprints, “five whys” inquiry, and insight statements. Synthesis should preserve the distinction between evidence and interpretation. For example:

• Evidence: “Four of six observed users asked another person to verify the form before submission.”
• Interpretation: “Users lack confidence that they have completed the form correctly.”
• Design implication: “A prototype should make completion status and error recovery visible.”

Ideate, prototype, and test

Ideation generates multiple responses to a framed need. Prototyping then makes assumptions tangible and testable. At this stage, a prototype may be a paper flow, role-play, storyboard, landing page, service script, clickable interface, or physical mock-up. The appropriate fidelity is the lowest level that can produce credible learning.

Testing should ask what the prototype reveals about the problem and user behavior, not only whether participants “like” the concept. Behavioral evidence—attempting a task, choosing among alternatives, providing access to data, or committing time—usually carries more weight than general enthusiasm.

Strengths and limitations

Design thinking is valuable when needs are ambiguous, stakeholders have different perspectives, and conventional requirements are incomplete. However, it can become superficial if empathy is reduced to a few interviews, if ideation begins before problem understanding, or if aesthetic desirability is confused with business viability. Human-centered methods must therefore be combined with technical, economic, regulatory, and systems analysis.

3. Systems Thinking: Seeing the Wider Situation

A product operates within a system of people, processes, technologies, institutions, incentives, infrastructures, and natural environments. A local improvement may produce undesirable effects elsewhere. For example, an automated scheduling tool may reduce administrative effort while increasing workload for frontline employees when exceptions are handled manually.

Systems thinking asks:

• Who participates directly and indirectly?
• What inputs, processes, outputs, and feedback loops shape the situation?
• Which rules, incentives, or power relationships influence behavior?
• Where are delays, bottlenecks, dependencies, and unintended consequences?
• What changes when the proposed intervention is adopted at scale?

A stakeholder map identifies actors and relationships. A causal-loop diagram explores reinforcing and balancing feedback. A service blueprint separates visible user actions from backstage processes and support systems. A system boundary clarifies what is included in the initial investigation, while acknowledging what lies outside it.

Example of a systems perspective

Consider food waste in a university cafeteria. A narrow problem statement might be “students need smaller portions.” A systems inquiry could reveal that fixed portion sizes, unpredictable class schedules, meal-plan incentives, kitchen forecasting, hygiene rules, and social norms all contribute to waste. A successful intervention might therefore involve flexible serving, demand data, changed incentives, and revised operating procedures rather than a single consumer-facing application.

Systems thinking does not require mapping everything. An excessively broad system map prevents action. The goal is a boundary appropriate to the decision being made, with explicit recognition of important external effects.

4. Jobs-to-be-Done and the Logic of User Progress

The jobs-to-be-done perspective proposes that people “hire” products and services to make progress in a particular circumstance. The job is not identical to a demographic category or a product feature. A person may hire a spreadsheet, a colleague, or a delivery service to accomplish different aspects of the same job.

A job statement commonly includes:

When [situation], I want to [motivation or progress], so that [desired outcome].

For example: “When preparing a monthly expense report, I want to reconcile transactions without checking several systems, so that I can submit an accurate report before the deadline.”

Jobs have functional, emotional, and social dimensions. The functional job concerns the practical task; the emotional job concerns how the user wants to feel; the social job concerns how the user wants to be perceived. A professional networking service may help a user find opportunities functionally, feel credible emotionally, and appear competent socially.

Job interviews

Good job interviews investigate a recent instance rather than hypothetical preference. Useful prompts include:

• What triggered the task?
• What did you do first, and what happened next?
• Which alternatives did you consider?
• Where did you experience difficulty or uncertainty?
• What workaround did you use?
• What did the situation cost in time, money, risk, or stress?
• What would make you change your current approach?

Avoid asking, “Would you use our proposed product?” Such questions invite politeness and speculation. Ask instead about actual behavior, recent decisions, and existing commitments.

5. Customer Discovery as Evidence Generation

Customer discovery is a structured process for testing assumptions about customers, problems, alternatives, and value. It is not equivalent to market research alone. Traditional market research may estimate market size or preferences; customer discovery investigates the causal details of a problem and the behavior surrounding it.

Segmenting the discovery problem

A useful initial segmentation may include:

• User: directly experiences or uses the product.
• Customer: pays for or procures the product.
• Beneficiary: receives the value.
• Decision-maker: authorizes adoption.
• Influencer: affects the decision.
• Gatekeeper: controls access or compliance.
• Affected stakeholder: experiences consequences without choosing the product.

In business-to-business contexts, these roles may be distributed across departments. In public or social ventures, the payer, user, and beneficiary may be entirely different people.

Discovery methods

Method selection should follow the uncertainty. If the team does not understand the context, observe before surveying. If it understands the problem but not prevalence, a survey or secondary dataset may be appropriate. If it doubts whether a proposed workflow is usable, test a prototype through realistic tasks.

Sampling and saturation

Early discovery usually uses purposive sampling: participants are selected because they have relevant experience, not because they statistically represent a population. Include contrasting cases, such as frequent and infrequent users, successful and unsuccessful users, and different organizational roles. Researchers should continue until additional interviews produce little substantially new insight for the specific question, while remaining alert to minority experiences that may be ethically or commercially important.

Evidence quality

Evidence is stronger when it is recent, specific, behavior-based, triangulated across methods, and connected to consequences. A participant’s statement that a problem is “annoying” is weaker than a documented workaround that consumes two hours each week and causes missed deadlines. No single evidence type is universally decisive; confidence comes from convergence and from actively searching for disconfirming evidence.

6. Problem Framing

Problem framing converts messy discovery material into a focused, testable representation. A robust frame identifies:

1. Who: the primary user and relevant stakeholders.
2. Situation: when, where, and under what trigger the problem occurs.
3. Need or job: the progress the user seeks.
4. Barrier: what prevents or complicates progress.
5. Consequence: the cost or significance of the difficulty.
6. Constraints: technical, economic, institutional, ethical, legal, or environmental boundaries.
7. Evidence and uncertainty: what is known and what remains hypothetical.

A practical template is:

[User] needs a way to [desired progress] when [context], because [important consequence], despite [current workaround or constraint].

For example:

Infrequent public-transit riders need a way to recover confidently from ticket-purchase errors when boarding time is near, because failed purchases create delay and embarrassment, despite the availability of a ticketing kiosk.

This frame is preferable to “Build a simpler ticketing app” because it describes a user situation and leaves room for multiple interventions.

Problem statements and “How might we?” questions

A problem statement should be neither so narrow that it dictates a feature nor so broad that it becomes meaningless. A “How might we?” question can open exploration:

How might we help infrequent riders recover from ticketing errors without delaying boarding?

Good questions preserve the important user, context, and outcome. They avoid embedded solutions such as “How might we build an AI chatbot?” unless the technology itself is the object of investigation.

Root causes and symptoms

The “five whys” technique can expose underlying causes, but it should not be used mechanically. Repeatedly asking why may oversimplify complex or systemic conditions. A causal explanation should be checked against observation and alternative hypotheses. For instance, delayed claims processing may arise from unclear forms, missing documents, staff incentives, legacy software, or legal verification requirements. Addressing only the visible symptom can shift rather than solve the problem.

7. Prioritizing Opportunities

Not every discovered problem deserves a prototype. A practical prioritization considers:

• Desirability: Is the problem important to a sufficiently reachable group?
• Feasibility: Can the team technically and operationally address it?
• Viability: Can value be sustained through revenue, funding, cost savings, or another model?
• Adoptability: Can users and institutions change behavior or approve implementation?
• Ethical legitimacy: Does the intervention respect autonomy, privacy, safety, fairness, and dignity?
• Strategic fit: Does it match the venture’s capabilities and purpose?

A scoring matrix may support discussion, but numerical scores do not create objectivity. Scores should be accompanied by evidence and confidence levels. A high-impact problem with weak evidence may deserve a discovery experiment rather than immediate development.

A useful experiment backlog links each assumption to a test:

8. From Problem Frame to Prototype Brief

A prototype brief should translate discovery into a bounded learning objective. It may contain:

• target participant and recruitment criteria;
• problem statement and job hypothesis;
• critical user scenario;
• assumptions being tested;
• prototype form and rationale;
• task participants will attempt;
• success indicators;
• ethical and data-protection requirements;
• decision rule for continuing, modifying, or abandoning the concept.

For example, if the uncertainty concerns whether users understand an error-recovery process, a clickable interface is more appropriate than a fully engineered platform. If the uncertainty concerns whether staff can deliver a new service, a role-play or service blueprint may be more informative than a visual mock-up.

The prototype should make the riskiest assumption observable. A polished prototype that tests only visual preference can create false confidence. Conversely, a rough prototype can generate strong evidence when the learning question is clear.

9. Illustrative Case: Reframing Medication Adherence Support

The following is a fictional illustrative case designed for learning.

Background

A student venture proposes a mobile application to remind older adults to take prescribed medication. The founders initially believe the opportunity is “an AI-powered reminder app.” They plan to add voice notifications, family dashboards, and predictive analytics.

Problem investigation

The team conducts interviews with older adults, family caregivers, and pharmacists; observes medication routines in several homes; and reviews anonymized pharmacy guidance. It finds that missed doses are not always caused by forgetting. Participants also encounter changing prescriptions, uncertainty about whether a dose was already taken, difficulty opening packaging, travel interruptions, side effects, and reluctance to appear dependent on family members. Caregivers are concerned about privacy and excessive alerts.

The initial solution framing is therefore incomplete. A reminder may address one symptom while failing to address uncertainty, physical access, changing instructions, and emotional concerns.

Systems analysis

The relevant system includes the patient, caregiver, prescriber, pharmacist, packaging, prescription record, home routine, and data-protection environment. A reminder application could create new risks if it displays sensitive medication information on a shared device or sends incorrect prompts after a prescription changes.

Reframed opportunity

A more useful frame is:

Older adults managing changing medication routines need a low-burden way to confirm what action is required and recover safely from uncertainty, while preserving control over personal information.

This frame does not assume that the answer is an app. Possible interventions include clearer packaging coordination, pharmacist-supported onboarding, a physical confirmation aid, or a carefully constrained digital service.

Prototype approach

The team creates a paper-based medication schedule and a role-play service. Participants complete three scenarios: a normal dose, an uncertain dose, and a changed prescription. The team observes whether participants can identify the next safe action and whether caregivers understand permission settings. It does not initially build predictive analytics because the core uncertainty concerns comprehension, safety, and workflow fit.

Outcome

Testing reveals that participants value confirmation and change management more than generic reminders. The team narrows the concept to a pharmacist-linked confirmation service with optional caregiver access. Further clinical, regulatory, privacy, and usability review is required before deployment.

Learning points

1. The first proposed solution may conceal several distinct problems.
2. Jobs and contexts reveal needs that demographic segmentation misses.
3. Systems analysis identifies stakeholders and risks outside the user interface.
4. Low-fidelity prototypes can test high-risk assumptions economically.
5. Health-related products require safety governance, consent, accessibility, and professional oversight.

10. Ethics, Governance, and Responsible Discovery

Opportunity discovery involves people’s experiences, identities, workplaces, and sometimes sensitive data. Researchers should obtain informed consent, explain the purpose of the activity, minimize data collection, protect confidentiality, and allow participants to withdraw where feasible. Compensation should recognize time without becoming coercive.

Special care is required when researching children, patients, employees, financially vulnerable people, or communities with limited power. Researchers should avoid extracting stories without returning value or explaining how findings will be used. Accessibility should be considered in recruitment, communication, prototype interaction, and participation conditions.

Artificial intelligence can assist with transcript organization, pattern detection, persona drafting, and generation of alternative interview prompts. It should not replace direct engagement or be treated as an impartial interpreter. AI-generated summaries can omit minority experiences, reproduce stereotypes, or expose confidential data. Teams should define data-handling rules, verify outputs against source material, record uncertainty, and retain human accountability for decisions.

In regulated domains such as health, finance, education, employment, and transport, discovery findings do not by themselves establish compliance or safety. Legal duties, professional standards, accessibility requirements, cybersecurity, data protection, and sector-specific approval processes must be investigated early enough to influence the opportunity definition.

11. Common Failure Modes and Best Practices

Common failure modes

• Solution-first framing: treating a preferred technology as the problem.
• Leading questions: asking participants to validate the founder’s idea.
• Hypothetical evidence: relying on statements about what people might do.
• Convenience sampling: interviewing only friends, colleagues, or enthusiastic early adopters.
• Feature inflation: adding functionality before validating the central job.
• Ignoring non-users: overlooking buyers, gatekeepers, affected workers, or regulators.
• Premature scaling: estimating a large market before confirming problem significance.
• Overgeneralization: treating a small qualitative sample as population prevalence.
• Confusing satisfaction with value: assuming positive reactions predict adoption.

Best practices

1. Start with a situation and behavior, not a feature.
2. Investigate recent concrete episodes.
3. Separate observations, interpretations, and assumptions.
4. Seek disconfirming evidence deliberately.
5. Include contrasting users and stakeholders.
6. Map the system sufficiently to expose dependencies and harms.
7. Choose research methods according to uncertainty.
8. Prototype the riskiest assumption at the lowest useful fidelity.
9. Define evidence thresholds before testing.
10. Reframe openly when evidence contradicts the original idea.

Contemporary Developments

Opportunity discovery increasingly uses digital trace data, remote research, participatory design platforms, service analytics, and rapid experimentation. These tools improve reach and speed but can privilege users who are digitally visible and can obscure people excluded from data systems. Privacy-preserving analytics, inclusive research practices, and qualitative interpretation remain important.

Climate change, demographic shifts, platform economies, geopolitical uncertainty, and changing regulation are also reshaping opportunity discovery. Entrepreneurs must consider resilience, resource use, repairability, accessibility, and distributional effects rather than evaluating opportunities only through short-term growth. In this environment, responsible problem framing is not a constraint added after innovation; it is part of identifying whether an opportunity is genuinely valuable.

Chapter Summary

Opportunity discovery is the disciplined identification of meaningful, feasible, and sustainable possibilities for value creation. It requires distinguishing observations, symptoms, problems, needs, jobs, solutions, and opportunities. Design thinking helps teams understand human experience and learn iteratively. Systems thinking reveals stakeholders, dependencies, feedback, and unintended consequences. Jobs-to-be-done explains the progress users seek in particular situations, while customer discovery tests assumptions through observation, interviews, behavioral evidence, data, and prototypes.

Problem framing establishes who experiences a difficulty, in what context, with what desired progress, barriers, consequences, and constraints. Effective frames avoid prescribing a solution and remain testable. Prioritization should consider desirability, feasibility, viability, adoptability, ethical legitimacy, and strategic fit. A prototype brief then converts the frame into a focused learning experiment. Ethical discovery requires consent, privacy, inclusion, accessibility, data governance, and human accountability—especially when AI or regulated domains are involved.

Key Terms

Opportunity discovery: The process of identifying evidence-supported possibilities for creating value.

Problem framing: Defining a problem’s users, context, needs, consequences, and constraints.

Design thinking: An iterative, human-centered approach to understanding and addressing complex challenges.

Systems thinking: Analysis of relationships, interdependencies, feedback, and wider consequences.

Jobs-to-be-done: The progress a person seeks to make in a particular situation.

Customer discovery: Testing assumptions about users, problems, alternatives, and value.

User: A person who directly interacts with or experiences a product or service.

Customer: The person or organization that pays for or procures an offering.

Stakeholder: Any party that affects or is affected by the product or its adoption.

Need: A desired condition or outcome valued by a person or group.

Symptom: A visible consequence that may indicate a deeper problem.

Workaround: An alternative behavior used when an existing solution is inadequate.

Insight: An evidence-based interpretation that explains a meaningful pattern.

Problem statement: A concise description of a significant user difficulty and its context.

“How might we?” question: An open design prompt that invites multiple interventions.

Prototype: A representation used to learn about an idea, workflow, or interaction.

Triangulation: Strengthening understanding by comparing evidence from different sources or methods.

Desirability: The extent to which an offering addresses an important user or stakeholder need.

Feasibility: The extent to which an intervention can be built and operated.

Viability: The extent to which an intervention can be sustained economically or organizationally.

Review Questions

Short Answer Questions

1. Distinguish a symptom from a problem and provide an example.
2. What is meant by a job-to-be-done?
3. Why should customer-discovery interviews focus on recent behavior?
4. Identify four components of a strong problem frame.
5. What is the purpose of a low-fidelity prototype?

Long Answer Questions

1. Explain how design thinking and systems thinking complement one another in opportunity discovery.
2. Compare observation, interview, survey, and prototype testing as discovery methods.
3. Discuss how users, customers, beneficiaries, decision-makers, and gatekeepers may differ.
4. Explain the desirability–feasibility–viability perspective and its limitations.
5. Describe ethical responsibilities when conducting discovery with vulnerable participants.

Analytical / Application Questions

1. A university observes that students frequently miss deadlines for financial-aid submissions. Develop two competing problem frames without proposing a specific software solution. Identify the evidence needed to distinguish between them.
2. A startup wants to build an AI chatbot for small-business tax questions. Apply jobs-to-be-done and systems thinking to identify at least five assumptions and propose a test for each.
3. Using the medication-adherence case, explain why a reminder application may address a symptom rather than the underlying opportunity. Recommend the next prototype and justify its fidelity and learning objective.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a problem from a solution?

A. A problem describes an undesirable user condition; a solution is an intervention intended to address it.

B. A problem is always technical; a solution is always social.

C. A problem is a feature request; a solution is a market segment.

D. A problem can be measured only after a product is launched.

Correct Answer: A. A problem describes an undesirable user condition; a solution is an intervention intended to address it.

Question 2

Which question is most consistent with a jobs-to-be-done interview?

A. Would you download our proposed application?

B. What features should our product include?

C. Tell me about the last time you tried to complete this task.

D. Would you recommend this idea to your friends?

Correct Answer: C. Tell me about the last time you tried to complete this task.

Question 3

What is a central purpose of systems thinking in product discovery?

A. To eliminate the need for user research

B. To identify relationships, dependencies, and unintended consequences

C. To guarantee that a product will be profitable

D. To select interface colors and typography

Correct Answer: B. To identify relationships, dependencies, and unintended consequences

Question 4

Which participant is the gatekeeper?

A. The person who experiences the problem

B. The person who receives the benefit

C. The person who controls access or compliance

D. The person who designs the prototype

Correct Answer: C. The person who controls access or compliance

Question 5

Which is the strongest evidence of a recurring problem?

A. A participant says the idea sounds interesting

B. A participant predicts that others might use it

C. Observed repeated workarounds that consume time and cause measurable consequences

D. A founder believes the market is large

Correct Answer: C. Observed repeated workarounds that consume time and cause measurable consequences

Question 6

Which problem frame is least solution-prescriptive?

A. Build an AI tutor for students who struggle

B. Create a dashboard for administrators

C. Help first-time users recover from payment errors before boarding

D. Add a chatbot to every ticketing kiosk

Correct Answer: C. Help first-time users recover from payment errors before boarding

Question 7

Why might a team use a low-fidelity prototype?

A. To test learning questions cheaply before investing in full development

B. To demonstrate that technical feasibility is already proven

C. To avoid speaking with real users

D. To replace all regulatory review

Correct Answer: A. To test learning questions cheaply before investing in full development

Question 8

Which consideration belongs most directly to ethical opportunity evaluation?

A. Whether the logo is visually distinctive

B. Whether the intervention respects privacy, autonomy, safety, and fairness

C. Whether competitors use similar fonts

D. Whether the team can add more features

Correct Answer: B. Whether the intervention respects privacy, autonomy, safety, and fairness

Question 9

A customer-discovery team wants to know whether a problem is common across a large population after first understanding its causes. Which method is most suitable next?

A. A population-oriented survey or analysis of relevant secondary data

B. A single additional anecdotal interview with a founder

C. A branding workshop

D. A high-fidelity animation

Correct Answer: A. A population-oriented survey or analysis of relevant secondary data

Question 10

Which statement best describes viability?

A. The extent to which users find an idea attractive

B. The extent to which an intervention can be built technically

C. The extent to which an intervention can be sustained economically or organizationally

D. The extent to which a prototype has many features

Correct Answer: C. The extent to which an intervention can be sustained economically or organizationally