Opportunity Framing and Customer DiscoveryIntroductionEntrepreneurial ventures rarely fail because founders lack ideas. They more often fail because an idea is treated as a validated opportunity before the underlying customer problem, context, and willingness to adopt have been understood. Basic product prototyping therefore begins before sketches, mock-ups, or minimum viable products. It begins with disciplined inquiry: identifying whose situation matters, understanding what those people are trying to accomplish, locating the obstacles they face, and converting evidence into assumptions that can be tested. Opportunity framing is the process of defining a potentially valuable problem or unmet need in a way that is specific enough to guide action but open enough to permit alternative solutions. Customer discovery is the systematic investigation of customers, users, buyers, influencers, and other stakeholders through interviews, observation, secondary research, and early experiments. Together, they establish the foundation for product decisions. A useful distinction is between a solution idea and an opportunity. “We should build an artificial-intelligence scheduling app” is a solution proposal. “Small medical practices lose appointment capacity because cancellations are discovered too late and staff cannot efficiently reallocate slots” is an opportunity hypothesis. The second statement identifies a situation, affected actors, and a possible source of value without prematurely prescribing a product. Learning ObjectivesBy the end of this chapter, students should be able to: - Distinguish markets, problems, needs, jobs-to-be-done, and opportunities.
- Map relevant customers and stakeholders, including users, buyers, beneficiaries, and gatekeepers.
- Design and conduct ethically responsible customer interviews and observations.
- Evaluate the strengths and limitations of primary and secondary research.
- Formulate evidence-based opportunity statements.
- Translate uncertain beliefs into explicit, testable assumptions.
- Prioritize assumptions according to uncertainty, importance, and cost of testing.
- Recognize common biases and methodological errors in early discovery.
- Connect discovery findings to product-prototyping decisions.
From Ideas to OpportunitiesAn opportunity is not simply a large market or an unpleasant problem. It is a plausible basis for creating and capturing value under particular conditions. These conditions may include a sufficiently important customer need, an accessible segment, feasible delivery, an acceptable cost structure, and a legal and ethical operating environment. Four concepts should be separated: | Concept | Meaning | Typical question |
|---|
| Market | A set of actual or potential exchanges involving a category of value | Who currently buys or could buy? | | Problem | An undesirable condition or obstacle | What is going wrong? | | Need | A requirement or desired outcome perceived as important | What must improve? | | Opportunity | A plausible, testable basis for value creation and capture | Why might a venture succeed here? |
A problem may exist without being an opportunity. For example, people may dislike long airport security queues, but solving the problem may require infrastructure, regulation, and capital beyond a small venture’s reach. Conversely, a modest problem may be an attractive opportunity if customers experience it frequently, already spend money to address it, and can be reached efficiently. The problem–solution separation principlePremature attachment to a solution distorts research. Founders may ask leading questions, interpret polite encouragement as demand, and ignore evidence that contradicts their concept. Discovery should therefore begin with situations and behaviors rather than product features. Weak framing: “Would you use our smart reusable food container?” Stronger framing: “How do you currently manage food storage and transport during a typical workday? Tell me about the last time this was difficult.” The stronger question seeks evidence about real behavior, frequency, consequences, and existing alternatives. It does not require respondents to imagine a hypothetical future. Jobs-to-Be-Done and Customer ContextThe jobs-to-be-done perspective proposes that customers “hire” products and services to make progress in a situation. A job is broader than a feature and more concrete than a vague demographic label. It may be functional, emotional, or social. For example, a commuter may functionally need to travel from home to work, emotionally want to feel in control of time, and socially want to appear reliable. A successful product may address all three dimensions. Job statements are often expressed as: “When [situation], I want to [motivation], so that [desired progress].” A job is not identical to a task. The task “send an invoice” may be part of the broader job “maintain predictable cash flow and professional credibility.” Understanding the broader job helps innovators avoid building a narrowly optimized feature that fails to address the customer’s real objective. Functional, emotional, and social dimensionsFunctional jobs concern practical outcomes: transporting goods, reconciling transactions, or learning a procedure. Emotional jobs concern feelings such as confidence, relief, or reduced anxiety. Social jobs concern identity and relationships, such as appearing competent, sustainable, or innovative. The dimensions should not be assumed in advance. They are hypotheses to investigate. A founder may believe that customers want speed, while interviews reveal that predictability or risk reduction matters more. Outcomes and constraintsDiscovery should examine both desired outcomes and constraints. Outcomes include accuracy, convenience, speed, reliability, status, and cost reduction. Constraints include procurement rules, technical compatibility, privacy requirements, habits, budget cycles, switching costs, and organizational politics. In business-to-business settings, the user may not be the economic buyer. A software operator may value ease of use, while an information-security officer evaluates compliance and a finance executive approves expenditure. A credible opportunity frame must therefore account for the full decision system. Stakeholder and Customer MappingCustomer discovery begins by defining who is affected. “The customer” is often an oversimplification. A stakeholder map can distinguish: - User: directly interacts with the product or service.
- Economic buyer: controls or authorizes payment.
- Beneficiary: receives value, whether or not they use the product.
- Influencer: affects evaluation or choice.
- Gatekeeper: controls access, approval, or distribution.
- Implementer: installs, configures, or operationalizes the solution.
- Affected non-customer: experiences consequences but does not choose or pay.
A stakeholder map is valuable because adoption can fail even when users are enthusiastic. For example, teachers may want classroom software, but a school district’s procurement process, privacy officer, and information-technology department may determine whether it can be purchased. Segmentation should initially be based on relevant behavior or context rather than superficial demographics. “Adults aged 25–40” is often less useful than “frequent remote workers who purchase ergonomic equipment and experience recurring wrist discomfort.” A segment is strategically meaningful when members share a problem, decision process, and reason to adopt. Customer Discovery as InquiryCustomer discovery is not a popularity survey. Its purpose is to reduce uncertainty about a set of propositions. A rigorous discovery process asks: - Does the situation occur?
- Who experiences it and under what conditions?
- How often does it occur?
- What consequences does it create?
- What alternatives are used now?
- What do those alternatives cost in money, time, risk, or effort?
- Who decides whether a new alternative is adopted?
- What constraints would prevent adoption?
The most credible evidence usually concerns observed or remembered behavior, not stated enthusiasm. “I would probably use that” is weak evidence. “Last month I paid a contractor to solve this three times” is stronger because it indicates a real event and an existing response. InterviewsA semi-structured interview combines consistency with flexibility. The researcher prepares a sequence of topics but follows relevant evidence when the participant introduces an unexpected issue. An effective interview typically includes: - Opening and consent: explain purpose, confidentiality, recording, and voluntary participation.
- Context: understand the participant’s role, environment, and relevant routines.
- Recent episode: ask about the last specific occurrence of the problem.
- Current behavior: identify tools, workarounds, people involved, and costs.
- Consequences: explore what happens if the issue is not resolved.
- Existing alternatives: determine what is liked, disliked, and tolerated.
- Decision process: identify budget, authority, timing, and approval.
- Closing: invite corrections, referrals, and additional observations.
Useful prompts include “Tell me about the last time,” “What did you do next?”, “Why was that important?”, and “What makes the current approach acceptable despite its limitations?” Avoid leading, double-barreled, and hypothetical questions. “Would a faster and cheaper dashboard improve your workflow?” contains a preferred answer and two separate value claims. Better questions are “How do you currently monitor this?” and “What, if anything, would you change?” Interview data is interpretive. The interviewer should distinguish direct quotations, observed facts, interpretations, and assumptions. A research log can use the following structure: | Evidence type | Example | Appropriate use |
|---|
| Direct behavior | “We export the report every Friday” | Establish current practice | | Consequence | “A missed update delayed a shipment” | Assess importance | | Existing workaround | “An assistant checks three systems” | Identify competing alternatives | | Opinion | “A mobile app sounds useful” | Generate a hypothesis, not validation | | Interpretation | “The issue is primarily trust” | Require further examination |
Observation and contextual inquiryObservation reveals differences between what people say and what they do. It is especially useful when work is habitual, distributed across tools, difficult to describe, or influenced by social desirability. A contextual inquiry combines observation with brief questions in the setting where work occurs. The researcher may ask, “What are you checking now?” or “What would happen if this field were missing?” The aim is not to become a passive spectator but to understand sequence, interruptions, handoffs, artifacts, and environmental constraints. An observation protocol should specify: - setting and duration;
- activities and actors;
- tools, documents, and systems used;
- interruptions and exceptions;
- decisions and handoffs;
- workarounds and errors;
- physical, organizational, and privacy constraints.
The observer must avoid disrupting safety-critical or confidential activities. Permission is required where people, private data, or controlled environments are involved. Secondary researchSecondary research uses evidence collected by others. Relevant sources include government statistics, industry reports, academic studies, regulatory documents, company filings, trade associations, reviews, support forums, job postings, and competitor materials. Secondary research can clarify market structure, terminology, regulation, trends, and existing alternatives before primary research begins. It can also reduce respondent burden by answering questions that do not require interviews. Source quality should be assessed through provenance, recency, method, incentives, sample, definitions, and consistency with other sources. A market report may quote a large market size but define the category broadly or use optimistic assumptions. A discussion forum may provide rich qualitative evidence but not represent the wider population. A disciplined evidence record includes the source, date, claim, method, limitations, and relevance to a specific assumption. Search-engine rankings are not evidence of customer importance; they are only indicators of discoverability or interest. Opportunity StatementsAn opportunity statement translates discovery into a concise claim about a meaningful situation. It should identify a target context, unmet or poorly served need, and desired progress without embedding an untested solution. One useful template is: For [specific segment] who experience [situation or problem] when [context], there is an opportunity to help them [desired progress] because [evidence or consequence]. Example: For independent physiotherapy clinics that manage appointments with small administrative teams, there is an opportunity to reduce the time and lost revenue associated with late cancellation recovery because staff currently contact patients manually and unused slots are often not refilled. This statement is stronger than “Build an AI appointment app” because it preserves solution flexibility. It also indicates what evidence must be examined: frequency of cancellations, current recovery practices, economic consequences, and acceptance of alternatives. A good opportunity statement is: - specific about the affected segment;
- grounded in a real situation;
- important enough to motivate change;
- open to multiple solutions;
- bounded enough to investigate;
- connected to evidence;
- ethically framed, without blaming vulnerable users.
It should not claim certainty prematurely. Terms such as “appears,” “may,” or “evidence suggests” can be appropriate in early-stage documentation. From Opportunity Statements to Testable AssumptionsEvery opportunity statement contains uncertainty. Assumption mapping makes that uncertainty visible. Common assumption categories include: | Category | Example assumption |
|---|
| Desirability | The problem is important enough for the segment to seek change | | Behavioral | Customers currently use a workaround with measurable cost | | Feasibility | The proposed service can operate within technical constraints | | Viability | A buyer will pay enough to support delivery | | Usability | Users can complete the critical task with limited training | | Adoption | A credible channel can reach decision-makers | | Regulatory | The concept can comply with relevant obligations | | Ethical | Benefits do not depend on unacceptable exclusion or surveillance |
A testable assumption specifies a proposition, population, observable measure, and threshold or decision rule. For example: Among independent clinics with fewer than ten administrative employees, at least six of eight interviewed managers will report experiencing two or more late cancellations per week and will describe the issue as a priority for improvement. This is not a universal truth claim. It is a decision-oriented criterion for an early investigation. The threshold should be justified by the decision at hand, not selected to guarantee a favorable result. Assumption priorityNot all assumptions deserve equal attention. A useful qualitative model prioritizes assumptions that are both important and uncertain. The highest-priority assumption is often the one whose failure would invalidate the opportunity and for which the team has weak evidence. A simple quantitative aid is an assumption risk score: Ri = Ii × Ui where Ri is the risk score for assumption i, Ii is its estimated importance if false, and Ui is its estimated uncertainty. Both may be rated on the same ordinal scale, such as 1 to 5. The product is a prioritization heuristic, not a probability or a statistically validated risk measure. It is useful only when the rating definitions are explicit and applied consistently. For example, an assumption rated importance 5 and uncertainty 4 receives Ri = 20. Another rated 3 and 3 receives 9. The first should normally be investigated earlier, although test cost, ethical risk, and time sensitivity may alter the sequence. Teams should avoid treating this score as objective measurement. Its purpose is to make reasoning discussable. More formal decision analysis may be appropriate when probabilities, consequences, and monetary values can be estimated credibly. Designing Evidence-Gathering ActivitiesThe best test is not necessarily the most sophisticated. It is the smallest ethical activity that can distinguish between meaningful alternatives. | Question | Suitable method |
|---|
| Does the behavior occur? | Interview about recent episodes; observation; records | | How often does it occur? | Operational data; diary study; structured survey | | Why does it occur? | Semi-structured interview; contextual inquiry | | What alternatives exist? | Workflow observation; competitor and substitute analysis | | Will people complete a process? | Usability test; prototype task | | Will people pay? | Pricing conversation; purchase commitment; pilot agreement | | Can the system operate? | Technical spike; service blueprint; expert review |
A survey may quantify patterns after exploratory interviews have clarified language and response categories. It is a poor substitute for understanding an unfamiliar problem. Likewise, a clickable prototype can test comprehension and task flow, but it does not by itself validate market demand. Sampling and saturationEarly discovery commonly uses purposive sampling: participants are selected because they possess relevant experience. The objective is not to claim statistical representativeness from a small convenience sample. Instead, the researcher seeks variation across contexts and examines whether important patterns recur. Researchers should document inclusion criteria, recruitment channels, refusals where relevant, and possible sampling bias. Stopping after a predetermined number of interviews can be misleading. A more defensible stopping logic considers whether additional interviews are producing new themes, whether critical stakeholder groups remain unexamined, and whether the decision can be made with acceptable uncertainty. Qualitative saturation is context-dependent and does not mean that all possible views have been discovered. Interpreting and Synthesizing FindingsAnalysis should occur during, not only after, research. After each interaction, record observations, notable quotations, surprises, contradictions, and implications. Then compare cases rather than merely collecting memorable anecdotes. A practical synthesis process is: - Transcribe or summarize evidence accurately.
- Code statements by situation, behavior, consequence, workaround, and constraint.
- Compare patterns across participants and contexts.
- Identify disconfirming evidence and negative cases.
- Separate user segments when needs or decision processes differ.
- Revise the opportunity statement.
- Update the assumption register and choose the next test.
Affinity mapping can help organize qualitative material, but clusters are interpretations rather than natural facts. Teams should retain links from themes to source evidence. A customer journey or service blueprint can then show stages, frontstage interactions, backstage activities, pain points, and opportunities for intervention. TriangulationTriangulation compares different sources or methods. For example, interview reports of delayed inventory updates can be compared with system logs, observation, and supplier records. Agreement increases confidence, but disagreement is not merely a nuisance. It may reveal differences between formal procedures and actual work, differences among segments, or measurement problems. Evidence strength depends on relevance and proximity to behavior. A signed pilot agreement may be stronger evidence of organizational commitment than a positive interview statement, but it still may not prove sustained usage or profitability. Illustrative Case: RefillRouteThe following is a fictional illustrative case designed to demonstrate the discovery process. BackgroundA graduate venture team proposed a mobile application that would help urban households purchase refillable household-cleaning products. The initial concept was a subscription app with reminders and delivery optimization. The team believed environmentally concerned consumers wanted a convenient alternative to single-use plastic bottles. Problem and initial assumptionsThe team initially assumed that environmental concern was the primary driver, that households would accept recurring subscriptions, and that delivery efficiency would create sufficient economic value. These assumptions were plausible but untested. The team mapped stakeholders: household users, retail partners, refill-station operators, delivery workers, manufacturers, and local regulators. It recognized that the person who cared about waste might not control household purchasing or be willing to store refill containers. Discovery approachOver three weeks, the team conducted twelve semi-structured interviews with households selected for variation in living arrangements, shopping habits, and access to refill stores. It observed six shopping trips and reviewed municipal waste reports, retailer reviews, and refill-station websites. Participants were asked about recent purchases rather than their reaction to the proposed app. The research showed that environmental concern was common, but it rarely overcame inconvenience. Participants reported three more immediate barriers: uncertainty about product quality, difficulty remembering which containers were clean and available, and limited access to nearby refill locations. Several participants disliked subscriptions because household consumption varied and storage space was limited. Observation revealed a further issue. Shoppers compared prices per unit but refill stations displayed pricing in inconsistent measures. The supposed delivery problem was less important than confidence, measurement clarity, and coordination among household members. Revised opportunity frameThe team revised its statement: For urban households that want to reduce packaging waste but shop across inconsistent refill locations, there is an opportunity to make refill purchasing predictable and easy by improving information about availability, quality, quantity, and household coordination. This frame allowed several solution paths: standardized product information, shared household lists, retailer tools, location-based availability, or a smaller pilot focused on one product category. Testable assumptions and next stepThe team prioritized the assumption that customers would change behavior if reliable availability and comparable pricing were visible. It created a low-fidelity directory covering one neighborhood and three product categories. The prototype did not include subscriptions or delivery. Participants were asked to complete realistic tasks: find a product, compare unit prices, check availability, and add a purchase to a shared list. The test showed that users understood the directory but distrusted availability information when it was more than one day old. Retailers, meanwhile, were unwilling to update data manually. The next prototype therefore focused on a low-effort retailer update process and clear timestamps rather than expanding consumer features. Outcome and learning pointsThe original solution concept was not validated. The discovery process nevertheless created value by revealing a more specific opportunity and a critical operational constraint. The case illustrates five principles: - Stated values do not necessarily predict behavior.
- Observation can reveal friction that interviews understate.
- A narrow prototype can test a key assumption without building the full product.
- Stakeholder incentives matter as much as user preferences.
- Negative evidence should redirect the design rather than be rationalized away.
Bias, Ethics, and GovernanceCustomer discovery involves power relationships and personal information. Ethical practice is therefore part of methodological quality, not an optional administrative step. Participants should understand the purpose of the research, what participation involves, whether recording will occur, how data will be stored, and that they may decline or withdraw where applicable. Sensitive data should be minimized, access-controlled, and retained only as long as necessary. Researchers must avoid collecting identifiable information merely because it might become useful later. Special care is required with children, employees questioned by supervisors, patients, financially distressed people, and other groups whose ability to refuse may be constrained. Compensation should recognize time without becoming coercive. Research settings should not expose confidential business information or create operational risks. Several biases commonly distort discovery: - Confirmation bias: noticing evidence that supports the initial idea.
- Leading-question bias: prompting favorable answers.
- Recency bias: overvaluing the latest interview.
- Sampling bias: recruiting only accessible or enthusiastic participants.
- Courtesy bias: participants expressing support to avoid offending the researcher.
- Survivorship bias: studying successful users while ignoring dropouts.
- Authority bias: accepting a senior stakeholder’s claim without corroboration.
- Solution bias: interpreting reactions to a prototype as proof of the underlying need.
Mitigation includes neutral prompts, diverse recruitment, explicit disconfirming questions, independent review of evidence, participant privacy, and a decision log that records why assumptions were accepted, revised, or rejected. Technology and AI in DiscoveryDigital tools can support transcription, coding, sentiment clustering, survey analysis, and synthesis. Artificial intelligence may help summarize large volumes of text or identify candidate themes, but it should not be treated as an independent researcher. Automated systems can omit context, misinterpret sarcasm, reproduce demographic bias, or expose confidential data to unauthorized services. Human researchers should verify quotations against source material, preserve uncertainty, distinguish machine-generated suggestions from findings, and avoid uploading sensitive transcripts without appropriate contractual and governance controls. AI-generated synthetic interviews are useful for rehearsing questions or exploring scenarios, but they are not evidence of customer behavior. Similarly, web analytics indicate interaction with a particular interface, not necessarily the importance of the underlying job. Contemporary discovery increasingly combines qualitative research with behavioral data, remote usability testing, digital diaries, and rapid prototype experiments. This creates greater scale but also increases risks of surveillance, consent ambiguity, algorithmic profiling, and overreliance on easily measurable behavior. Strategic judgment remains necessary. Linking Discovery to Prototyping DecisionsDiscovery is successful when it changes what the team does. A finding may lead to: - narrowing the target segment;
- redefining the job or outcome;
- removing a low-value feature;
- designing a service rather than a standalone product;
- testing a different channel or pricing model;
- addressing a regulatory or operational constraint;
- abandoning the opportunity.
The transition to prototyping should preserve the logic of the evidence. If the critical assumption concerns whether users can compare options, a comparison interface may be appropriate. If it concerns whether retailers will supply accurate data, a service blueprint and operational pilot are more relevant than a polished consumer app. Prototype fidelity should match the uncertainty being tested. A useful discovery-to-prototype record links each design decision to an evidence item and an assumption. This prevents the team from accumulating features merely because they were requested in isolated conversations. Challenges and LimitationsDiscovery cannot eliminate uncertainty. Participants may not remember accurately, behaviors may change when observed, and early adopters may differ from mainstream customers. Small qualitative samples can reveal mechanisms and language but cannot estimate prevalence with statistical confidence. Secondary sources may use incompatible definitions. Market size estimates often contain forecasts presented with unjustified precision. There is also a risk of endless research. A team may continue interviewing to postpone a difficult decision. The appropriate endpoint is not certainty but sufficient evidence for the next consequential action, accompanied by explicit residual risks. Another limitation is that customers are not always able to articulate latent needs. Research should therefore combine verbal accounts with observation, artifacts, experiments, and analysis of alternatives. However, the existence of an unarticulated need does not automatically justify a product; the venture must still establish feasibility, viability, adoption, and ethical acceptability. Best-Practice ChecklistBefore moving from discovery to a prototype, confirm that the team can answer the following: - Which specific segment and context are being addressed?
- What job or desired progress is at stake?
- What recent evidence demonstrates the problem?
- What do customers do today instead?
- What are the financial, time, emotional, or risk consequences?
- Who uses, buys, approves, implements, and is affected?
- Which assumptions are both important and uncertain?
- What evidence would change the team’s decision?
- Have contradictory cases and non-users been considered?
- Were participants treated ethically and their data protected?
- Does the planned prototype test the riskiest assumption?
Chapter SummaryOpportunity framing and customer discovery provide the intellectual and practical foundation for product prototyping. An opportunity is more than a problem or a large market; it is a plausible, evidence-informed basis for creating and capturing value. Effective discovery separates problems from solutions, investigates jobs-to-be-done in context, maps users and other stakeholders, and examines actual behavior rather than hypothetical enthusiasm. Interviews reveal meanings, motivations, and recent episodes; observation exposes routines, workarounds, and environmental constraints; secondary research contributes market, regulatory, and contextual evidence. Findings should be triangulated, recorded carefully, and used to construct an opportunity statement that is specific, important, and solution-neutral. Assumption mapping then converts uncertainty into testable propositions concerning desirability, feasibility, viability, adoption, regulation, and ethics. Graduate-level practice requires critical awareness of sampling limitations, bias, evidence quality, stakeholder power, privacy, and the limits of AI-supported analysis. The goal is not to prove an idea correct but to make better decisions with less avoidable uncertainty. A prototype should therefore be selected as an instrument for testing a prioritized assumption, not as a premature commitment to a favored solution. Key TermsOpportunity: A plausible basis for creating and capturing value under specified conditions. Opportunity framing: Defining a problem or unmet need in a focused but solution-open form. Customer discovery: Systematic investigation of customers, users, stakeholders, contexts, and alternatives. Job-to-be-done: The progress a person or organization seeks in a particular situation. Functional job: A practical task or outcome the customer seeks. Emotional job: The feeling or psychological state the customer seeks. Social job: The identity or social response the customer seeks to create. User: The person who directly interacts with a product or service. Economic buyer: The person or organization that authorizes or funds a purchase. Gatekeeper: An actor who controls access, approval, or distribution. Stakeholder map: A representation of actors affected by or able to influence an opportunity. Contextual inquiry: Observation combined with questions in the setting where work occurs. Secondary research: Use of evidence previously collected by other organizations or researchers. Assumption: A proposition accepted provisionally but not yet adequately evidenced. Desirability: The extent to which a solution addresses a meaningful customer need. Feasibility: The extent to which a solution can be built and operated. Viability: The extent to which a solution can produce sustainable economic value. Triangulation: Comparing evidence from multiple sources or methods. Qualitative saturation: The point at which additional relevant inquiry produces few substantively new themes. Prototype: A representation or experiment designed to learn about a product, service, or assumption. Review QuestionsShort Answer Questions- Distinguish a problem, a need, and an opportunity.
- Why are recent behavioral episodes generally stronger evidence than hypothetical statements of interest?
- What is the difference between a user, an economic buyer, and a gatekeeper?
- Name three types of assumptions that may be present in an opportunity statement.
- Why should a prototype be linked to a prioritized assumption?
Long Answer Questions- Explain the jobs-to-be-done perspective and show how functional, emotional, and social jobs may interact in one customer situation.
- Compare interviews, observation, and secondary research as customer-discovery methods, including their respective strengths and limitations.
- Develop an opportunity statement for a problem of your choice and explain why it is specific, important, and solution-neutral.
- Discuss how sampling, confirmation bias, courtesy bias, and solution bias can distort entrepreneurial research.
- Explain the ethical responsibilities involved in conducting customer discovery with personal, organizational, or vulnerable-participant data.
Analytical / Application Questions- A team claims that university students need an AI study-planning application because twelve students say they “would definitely use it.” Design a discovery plan that tests the underlying problem, current alternatives, decision criteria, and willingness to change behavior.
- Using the risk heuristic Ri = Ii × Ui, compare two assumptions: Assumption A has importance 5 and uncertainty 2; Assumption B has importance 3 and uncertainty 5. Calculate both scores, discuss the limitations of the comparison, and recommend which assumption to test first.
- A hospital administrator, nurse, patient, software buyer, and data-protection officer are involved in a proposed patient-monitoring service. Construct a stakeholder analysis that identifies each actor’s likely job, influence, evidence needs, and ethical concern. Explain how the analysis would affect the first prototype.
Multiple Choice Questions with AnswersQuestion 1Which statement best represents an opportunity statement? A. We will build an AI-powered scheduling application. B. Everyone wants a faster and cheaper scheduling tool. C. Small clinics lose appointment capacity because late cancellations are discovered too late and staff must recover slots manually. D. Our startup will disrupt appointment management. Correct Answer: C. Small clinics lose appointment capacity because late cancellations are discovered too late and staff must recover slots manually. Question 2Which evidence is generally strongest for establishing that a customer problem is behaviorally real? A. A participant says the proposed product sounds exciting. B. A participant describes a recent incident and shows the workaround currently used. C. A founder believes the problem is widespread. D. A competitor’s advertisement claims that the problem exists. Correct Answer: B. A participant describes a recent incident and shows the workaround currently used. Question 3Who is the economic buyer? A. The person who directly uses the product every day. B. The person who is affected by the problem but has no decision authority. C. The person or organization that authorizes or funds the purchase. D. The person who observes the product during research. Correct Answer: C. The person or organization that authorizes or funds the purchase. Question 4What is the primary purpose of contextual inquiry? A. To persuade participants to adopt a proposed solution. B. To observe work in context while asking questions about actions and constraints. C. To calculate the total addressable market from a small sample. D. To replace all secondary research. Correct Answer: B. To observe work in context while asking questions about actions and constraints. Question 5Which question is least leading in a customer interview? A. Would a cheaper mobile app solve this problem for you? B. Do you agree that the current process is inefficient? C. Tell me about the last time you encountered this situation. D. Would you prefer our solution to your current tool? Correct Answer: C. Tell me about the last time you encountered this situation. Question 6If an assumption has importance Ii = 5 and uncertainty Ui = 4, what is its risk score under Ri = Ii × Ui? A. 9 B. 16 C. 20 D. 25 Correct Answer: C. 20 Question 7Which statement about qualitative saturation is most accurate? A. It proves that a qualitative sample is statistically representative. B. It means every possible customer opinion has been discovered. C. It refers to additional relevant inquiry producing few substantively new themes in the study context. D. It occurs automatically after exactly ten interviews. Correct Answer: C. It refers to additional relevant inquiry producing few substantively new themes in the study context. Question 8A team observes that customers claim to value sustainability but repeatedly choose a less sustainable option because it is more convenient. What is the best interpretation? A. The interviews must be invalid. B. Stated values and observed behavior may differ, so convenience should be investigated as a constraint or competing outcome. C. Sustainability is never a real customer need. D. The team should immediately build a subscription product. Correct Answer: B. Stated values and observed behavior may differ, so convenience should be investigated as a constraint or competing outcome. Question 9Which prototype best tests whether retailers will provide accurate availability data? A. A polished consumer advertising campaign. B. A technical and operational pilot examining the retailer update process. C. A brand logo and social-media page. D. A survey asking consumers whether they like accurate information. Correct Answer: B. A technical and operational pilot examining the retailer update process. Question 10Why should AI-generated synthetic interviews not be treated as customer evidence? A. They are always more expensive than human interviews. B. They cannot generate any plausible language. C. They simulate responses rather than documenting behavior or experience from real participants. D. They are suitable only for accounting applications. Correct Answer: C. They simulate responses rather than documenting behavior or experience from real participants.
|