Foundations of Product Discovery and Validation

Introduction

Product management is often described as the activity of deciding what to build, for whom, and why. That description is useful but incomplete. Before a team can responsibly build a product, it must understand a problem, identify a sufficiently important customer need, formulate a value proposition, and gather credible evidence that a proposed solution is desirable, feasible, viable, usable, and ethically acceptable. These activities constitute product discovery and validation.

Discovery and validation are especially important because product decisions are made under uncertainty. Teams rarely possess complete information about customer behaviour, market demand, competitors, technology, regulation, or the economics of a business model. A product may fail not because it was poorly engineered, but because it solved an unimportant problem, targeted the wrong customers, used an unsustainable business model, or was launched before the organization understood the conditions for adoption.

This chapter establishes the conceptual foundation for product discovery and validation. It explains core terminology, types of uncertainty, product–market fit, evidence quality, and the relationship among discovery, validation, delivery, and the product lifecycle. It also distinguishes outputs, outcomes, and impacts—three terms that are frequently confused in product planning and evaluation.

Learning Objectives

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

1. Define and distinguish major discovery and validation terms.
2. Explain why product decisions involve different forms of uncertainty.
3. Relate customer problems, hypotheses, value propositions, and product–market fit.
4. Assess evidence according to relevance, reliability, behavioural proximity, and decision usefulness.
5. Explain the relationship among discovery, validation, delivery, and the product lifecycle.
6. Distinguish outputs, outcomes, and impacts in product evaluation.
7. Apply these concepts to a product-management case and identify appropriate next steps.

1. Product Management as a Decision Discipline

Product management is not simply project coordination or feature administration. It is a decision discipline concerned with maximizing the value created by a product over time while managing constraints and uncertainty. A product manager integrates customer understanding, business strategy, technology, design, analytics, operations, and governance.

A product decision can be represented conceptually as:

Decision = target customer + problem or opportunity + proposed intervention + evidence + constraints

This is not a mathematical identity. It is a reminder that a decision is incomplete when it states only an intervention—for example, “build a mobile application”—without specifying whose problem is being addressed, what evidence supports the choice, and what constraints apply.

Product discovery addresses questions such as:

• Who experiences the problem?
• In what context does it occur?
• How important and frequent is it?
• What alternatives do people currently use?
• What value could a new solution create?
• Which assumptions are most dangerous?

Validation addresses whether available evidence is strong enough to support a decision. Validation does not prove that a product will succeed. Rather, it reduces particular uncertainties to an acceptable level for a particular decision.

For example, a prototype test may provide useful evidence about usability but little evidence about willingness to pay. A pricing experiment may provide evidence about commercial interest but not necessarily about long-term retention. Evidence must therefore be interpreted in relation to the question it is intended to answer.

2. Essential Terminology

2.1 Product, customer, user, and buyer

A product is a system of value offered to address a need or enable a desired outcome. It may include software, hardware, services, processes, content, support, and business rules. A product is therefore broader than a feature or technical component.

A customer is the individual or organization that obtains, uses, or pays for value from the product. A user interacts with the product, but may not be the purchaser. A buyer authorizes or makes the purchase. In business-to-business settings, the user, buyer, economic decision-maker, administrator, and beneficiary may all be different stakeholders.

2.2 Problem, need, job, and opportunity

A problem is an undesirable condition or obstacle experienced by a stakeholder. A need is a requirement or desired condition that motivates action. A job to be done describes what a person is trying to accomplish in a particular circumstance. Jobs may be functional, emotional, or social.

An opportunity is a potentially valuable area for intervention. It is not automatically a product idea. A strong opportunity connects a meaningful problem with a reachable customer group, a feasible intervention, and an economically or strategically attractive context.

2.3 Hypothesis and assumption

A hypothesis is a testable proposition about customers, problems, solutions, behaviour, or business performance. For example: “Independent retailers with fewer than ten employees will use an automated stock-replenishment tool if it reduces weekly inventory work by at least two hours.”

An assumption is something treated as true for planning purposes but not yet adequately supported by evidence. Every hypothesis contains assumptions. Product discovery makes assumptions visible so that they can be investigated.

2.4 Experiment and prototype

An experiment is a deliberately designed investigation that exposes an assumption to evidence. It should specify the assumption, method, participants or data, decision rule, and limitations.

A prototype is a representation of a proposed product or experience used to learn. Prototypes range from sketches and storyboards to clickable interfaces, service simulations, technical spikes, and limited live releases. Fidelity should be appropriate to the question. A highly polished prototype can create false confidence if the underlying problem has not been established.

2.5 Minimum viable product

A minimum viable product (MVP) is the smallest product or product-enabled service that allows a team to test a meaningful value proposition with real or realistically situated users. “Minimum” refers to scope; “viable” refers to the ability to create sufficient value for a defined purpose. An MVP is not necessarily a low-quality product, nor is it always the first version released to the entire market.

2.6 Value proposition and business model

A value proposition explains why a target customer should prefer an offering over available alternatives. It should identify the customer, important problem or desired outcome, proposed value, and basis for differentiation.

A business model describes how an organization creates, delivers, and captures value. Product validation must consider both customer value and organizational viability. A product can be desirable but financially unsustainable, or profitable for a firm while producing unacceptable harm or poor user outcomes.

3. The Nature of Product Uncertainty

Uncertainty is not the same as risk. Uncertainty exists when the relevant state of the world or the probability of outcomes is not sufficiently known. Risk generally refers to the possibility of an adverse outcome, often with some ability to estimate likelihood and consequence. In practice, product teams face both measurable risks and poorly understood uncertainties.

Five categories are particularly important:

These categories interact. A solution may be desirable but infeasible under current technology. It may be feasible and viable but illegitimate because it violates privacy expectations or discriminates against a group.

A useful principle is uncertainty reduction before commitment. The cost of learning is usually lower before extensive delivery investment. However, discovery itself has a cost. Teams should not investigate every conceivable question indefinitely. They should prioritize assumptions according to importance and uncertainty.

One practical prioritization rule is:

Priority of learning = consequence of being wrong × current uncertainty

This is a conceptual scoring rule rather than a universal numerical formula. Teams may use ordinal ratings such as low, medium, and high, provided they define the scale consistently. The purpose is to investigate assumptions that could most seriously alter the product direction.

4. From Ideas to Testable Value Propositions

An idea is not yet a product strategy. Product discovery transforms an idea into a set of explicit claims. A useful hypothesis statement includes:

• target segment or context;
• customer problem or job;
• proposed intervention;
• expected behaviour or outcome;
• evidence threshold and time period;
• important exclusions and risks.

For example:

For urban apartment residents who struggle to recycle correctly, a photograph-based sorting assistant will increase correct disposal decisions because it provides immediate, item-specific guidance at the point of disposal.

This statement contains several claims: the problem exists, the target group experiences it, the proposed intervention is understandable, the intervention changes behaviour, and the change has value. These claims should not be tested as though they were one assumption.

A theory of change makes the causal logic explicit:

Intervention → user behaviour → immediate outcome → organizational or social impact

For the recycling example, the intervention may provide item-specific guidance; the behaviour may be a correct disposal decision; the immediate outcome may be improved sorting accuracy; and the impact may be lower contamination in the recycling stream. Each link can fail, so discovery and validation should examine the chain rather than only the interface.

5. Evidence Quality and Research Design

Evidence is not automatically strong because it is quantitative, recent, or collected from many people. Evidence quality depends on whether it is appropriate for the decision being made.

5.1 Dimensions of evidence quality

Relevance concerns whether the evidence addresses the actual decision. A survey about general interest may be irrelevant to a decision about sustained weekly use.

Reliability concerns consistency and dependability of measurement. Ambiguous questions, unstable instrumentation, and inconsistent sampling reduce reliability.

Validity concerns whether the evidence supports the intended interpretation. A click may indicate curiosity, not genuine willingness to pay.

Behavioural proximity concerns how closely the evidence reflects real behaviour in a realistic context. Observed payment or repeated use is generally closer to behaviour than a stated intention in an interview, although context still matters.

Representativeness concerns whether the participants or data reflect the population to which the decision will be applied. A convenience sample can be useful for early exploration but may not support market-wide claims.

Timeliness concerns whether conditions have changed since the evidence was collected. Market conditions, regulations, technologies, and customer practices may change quickly.

Actionability concerns whether the evidence supports a clear decision or next experiment.

5.2 Qualitative and quantitative evidence

Qualitative research is valuable for understanding meaning, context, language, workarounds, and unmet needs. Interviews and observation can reveal behaviour that customers do not spontaneously report. Their limitations include small samples, interviewer effects, recall problems, and difficulty estimating prevalence.

Quantitative research is useful for estimating frequency, comparing groups, monitoring behaviour, and assessing relationships. Its limitations include measurement error, sampling bias, response bias, and the danger of mistaking correlation for causation.

The choice is not qualitative versus quantitative. Strong discovery often uses methodological triangulation: different methods examine the same proposition from complementary perspectives.

5.3 A hierarchy of commitment

Evidence can be viewed as a progression from weak signals to stronger behavioural commitment:

1. Speculation by the product team.
2. Customer statements about problems or intentions.
3. Reactions to a concept or prototype.
4. Behaviour in a simulated or limited context.
5. Repeated behaviour in a real context.
6. Payment, renewal, referral, or sustained use.

This is not a rigid hierarchy. For example, a poorly designed payment test may be less informative than careful observation of a complex workplace process. Nevertheless, teams should distinguish what people say from what they do and what they repeatedly do from what they do once.

5.4 Falsifiability and decision rules

A useful experiment can produce a result that changes the team’s mind. The team should specify in advance what result would support, weaken, or reject the hypothesis. For example:

Proceed to a limited pilot if at least 8 of 12 target participants complete the critical task without assistance and at least 5 indicate that the problem is sufficiently important to change their current behaviour.

The threshold is not a law of nature. It is a decision rule whose appropriateness depends on the cost of proceeding, the consequences of failure, sample limitations, and the maturity of the product. It should be documented rather than selected after seeing the result.

6. Product–Market Fit

Product–market fit (PMF) describes a condition in which a product provides compelling value to a sufficiently large or strategically important market, leading to sustained adoption and supporting a viable model. PMF is not a single universal metric or a one-time event. It is a multidimensional and evolving relationship among customer value, adoption, retention, competition, and economics.

Important indicators may include:

• repeated use for the target job;
• retention appropriate to the product category;
• organic referrals or advocacy;
• willingness to pay or organizational commitment;
• successful acquisition through repeatable channels;
• evidence that customers choose the product over alternatives;
• unit economics that can improve with scale.

PMF should not be inferred from downloads, website visits, press attention, or a temporary spike caused by novelty. A product may have strong engagement among a niche segment but weak fit in a broader market. Product managers must therefore define the target market and the relevant usage occasion.

PMF is also not equivalent to customer satisfaction. Satisfaction may be high even when usage is infrequent, switching costs are low, or the product does not solve a sufficiently important problem. Conversely, a mission-critical product may be valued despite a difficult interface, although poor usability can eventually limit adoption.

A mature interpretation treats PMF as a portfolio of evidence rather than a binary status. Teams should ask: fit for whom, for which job, in which context, against which alternatives, and under what economic conditions?

7. Discovery, Validation, Delivery, and the Product Lifecycle

Discovery and delivery are related but different modes of work. Discovery focuses on learning what should be built and why. Delivery focuses on building, releasing, operating, and improving a chosen solution. They should not be treated as completely separate phases because delivery creates new learning and discovery continues after launch.

The product lifecycle commonly includes:

1. Opportunity framing – identify strategic context, users, problems, and constraints.
2. Problem discovery – investigate needs, workarounds, alternatives, and context.
3. Solution exploration – generate and compare possible interventions.
4. Validation – test the most consequential assumptions.
5. Delivery and launch – build, release, support, and instrument the product.
6. Adoption and growth – improve acquisition, activation, retention, and expansion.
7. Maturity and renewal – defend value, simplify operations, extend the product, or reposition it.
8. Sunset or replacement – responsibly retire the product when value no longer justifies its cost or risk.

These stages are not strictly linear. Discovery may reveal that the problem is poorly defined, causing reframing. Delivery may reveal operational constraints. Post-launch data may expose a different user segment or a new problem. A useful operating model therefore maintains a continuous loop:

Figure: Discovery, validation, delivery, and outcome learning form a continuous product loop.

A stage-gate approach can be useful for high-cost or highly regulated products, but rigid handoffs create a risk that discovery findings will not influence delivery. Cross-functional teams, shared outcome measures, and continuous evidence review help preserve the connection.

8. Outputs, Outcomes, and Impacts

Confusing outputs with outcomes is one of the most common weaknesses in product planning.

An output is what the team produces or releases. Examples include a feature, training session, API, report, or number of customer-support conversations completed.

An outcome is the change in behaviour, condition, or capability that follows from an output. Examples include customers completing a task faster, using a service more consistently, or reducing errors.

An impact is the broader and more enduring consequence of outcomes for the organization, customers, society, or environment. Examples include improved financial resilience, reduced health inequalities, or lower carbon emissions.

The causal relationship is not automatic. Releasing a dashboard does not guarantee advisor action; advisor action does not guarantee student engagement; and engagement does not guarantee improved completion. Evaluation should therefore measure the relevant level and test assumptions between levels.

A product team may use an outcome statement such as:

Increase the proportion of identified at-risk students who receive a meaningful advisor interaction within seven days.

This is more informative than “launch an alert feature” because it describes a change in behaviour and service performance. An impact statement might be: “Improve continuation rates among students facing financial or academic barriers.” Impact measures are important but often influenced by many external factors, so attribution should be treated cautiously.

9. Illustrative Case: Validating a Clinic Appointment Product

Background

The following is a fictional illustrative case. CareBridge is a proposed service intended to reduce missed appointments at community health clinics. The initial idea is a mobile application that sends reminders and allows patients to reschedule.

Problem framing

The team initially assumes that missed appointments result primarily from forgetfulness. Interviews with clinic staff reveal additional causes: patients cannot easily reach the clinic by telephone, appointment times conflict with work, transport is unreliable, and some patients fear fees for cancellation. The original problem statement is therefore too narrow.

The team segments the context into patients, clinic administrators, clinicians, and family members who sometimes coordinate care. The most urgent early opportunity appears to be appointments requiring preparation, because a missed appointment wastes scarce clinical capacity and may delay treatment.

Hypotheses

The team identifies three consequential hypotheses:

1. Patients value a low-friction way to confirm or reschedule an appointment.
2. Clinics can integrate the service with existing scheduling systems without unacceptable operational burden.
3. Timely confirmation and rescheduling will reduce avoidable missed appointments.

Evidence plan

For desirability, researchers observe scheduling and cancellation processes and conduct interviews with patients who recently missed appointments. For usability, they test a multilingual prototype using realistic appointment scenarios. For feasibility, engineers conduct a technical integration spike with a representative clinic system. For outcome validation, the team proposes a limited pilot comparing missed-appointment rates before and after implementation while monitoring changes in appointment volume and patient mix.

The team avoids treating interview statements as proof of impact. Patients may express enthusiasm for reminders but still fail to act when transport or work conflicts occur. The pilot therefore includes options for rescheduling and records the reason for each missed appointment.

Approach and decision

Prototype sessions show that patients understand confirmation messages but struggle with a long registration process. The team removes account creation from the first interaction and adds a telephone option for patients without reliable data access. The integration spike reveals that real-time rescheduling is not initially feasible, so the first service allows patients to request a change, after which clinic staff confirm availability.

After the pilot, confirmation rates improve, but missed appointments decline only for appointments that can be rescheduled easily. The evidence supports a narrower proposition: the service is valuable when it combines reminders with accessible rescheduling and clinic follow-up. The team does not claim that reminders alone solve the problem.

Learning points

The case illustrates five principles:

• The first stated problem may be a symptom rather than the underlying service problem.
• Different hypotheses require different evidence.
• A prototype can reveal usability issues without validating business impact.
• Feasibility constraints can change the solution design.
• Outcomes should be measured directly rather than inferred from outputs.

10. Governance, Ethics, and Responsible Validation

Discovery research involves people, personal information, and sometimes sensitive circumstances. Professional practice requires informed participation, appropriate consent, confidentiality, secure data handling, and respect for the right to withdraw. Organizations must comply with applicable privacy and data-protection law, but legal compliance is only a baseline; ethical practice also considers power imbalances, exclusion, dignity, and potential harm.

Teams should avoid deceptive experiments unless they are justified, proportionate, approved through appropriate governance, and followed by suitable disclosure. Vulnerable populations require additional care. A product experiment that improves an aggregate metric while harming a minority group is not a successful validation result.

AI-enabled products introduce further questions. Teams should distinguish model performance from product value. A highly accurate model may still produce poor outcomes if users do not trust it, if decisions are unactionable, or if errors are distributed unfairly. Validation should examine data provenance, explainability appropriate to the context, privacy, security, human oversight, and failure modes. Automated experimentation should not remove accountability from product leaders.

11. Common Failure Modes and Best Practices

Failure modes

Solution-first discovery: Teams begin with a predetermined feature and selectively collect supporting opinions.

Leading questions: Researchers ask whether participants “would love” a proposed solution rather than investigating actual behaviour and alternatives.

Vanity metrics: Teams celebrate downloads, impressions, or total registered users without examining activation, retention, or meaningful outcomes.

False precision: A small, biased sample is used to make highly precise market claims.

Premature scaling: Teams invest in architecture, marketing, or organizational expansion before validating the core value proposition.

Local optimization: A team improves a feature metric while worsening the end-to-end customer or business outcome.

Evidence laundering: Weak evidence is repeatedly summarized until it appears stronger than it is.

Best practices

1. Make assumptions explicit and rank them by consequence and uncertainty.
2. Start with the customer’s context, existing alternatives, and actual behaviour.
3. Match each research method to a clearly stated decision.
4. Use the smallest credible experiment, not merely the smallest artifact.
5. Define decision rules before reviewing results.
6. Record contradictory evidence and reasons for changing direction.
7. Include feasibility, viability, usability, and legitimacy—not only desirability.
8. Measure outcomes and unintended consequences after release.
9. Involve design, engineering, operations, legal, data, and domain experts early.
10. Treat discovery as continuous learning rather than a one-time prelude to delivery.

Contemporary Developments

Modern product teams increasingly use continuous discovery practices, experimentation platforms, product analytics, remote research, synthetic or simulated environments, and AI-assisted analysis. These tools can increase speed, but they do not eliminate the need for research judgment. Automated summaries may omit context; dashboards may encode biased definitions; and rapid experimentation can normalize intrusive data collection.

The contemporary product manager must therefore be both evidence-oriented and evidence-critical. The relevant question is not “How much data do we have?” but “What decision does this evidence support, under what assumptions, with what limitations, and with what consequences for different stakeholders?”

Chapter Summary

Product discovery and validation are disciplines for making better product decisions under uncertainty. Discovery investigates customers, contexts, problems, alternatives, and opportunities. Validation tests whether important claims are supported strongly enough to justify a decision. Desirability, usability, feasibility, viability, and legitimacy are complementary dimensions of product assessment.

High-quality evidence is relevant to the decision, reasonably reliable and valid, behaviourally meaningful, appropriately representative, timely, and actionable. Qualitative and quantitative methods serve different purposes and are often strongest when combined. Product–market fit is an evolving relationship among customer value, sustained adoption, market conditions, and viable economics; it cannot be inferred from vanity metrics alone.

Discovery, validation, delivery, and lifecycle management should operate as a continuous learning system. Outputs are what a team produces, outcomes are changes resulting from those outputs, and impacts are broader consequences. Ethical governance, inclusion, privacy, and responsible use of technology are integral to validation rather than optional additions.

Key Terms

Product: A system of offerings and experiences that creates value for defined stakeholders.

Product discovery: Investigation of customer problems, opportunities, solutions, and assumptions.

Validation: Gathering and evaluating evidence to support or revise a product decision.

Customer: A person or organization that obtains, uses, or pays for product value.

User: A person who interacts with a product.

Problem: An undesirable condition, obstacle, or unmet need.

Job to be done: The functional, emotional, or social progress a person seeks in a context.

Hypothesis: A testable proposition about customers, behaviour, solutions, or performance.

Assumption: An unverified belief treated as true for planning purposes.

Experiment: A deliberately designed investigation of an assumption.

Prototype: A representation used to learn about a proposed product or experience.

Minimum viable product: The smallest product-enabled offering that tests a meaningful value proposition.

Value proposition: The reason a target customer should prefer an offering over alternatives.

Product–market fit: Sustained alignment among customer value, adoption, market need, and viable economics.

Desirability: The extent to which stakeholders want or value a product.

Feasibility: The extent to which a product can be built and operated under constraints.

Viability: The extent to which a product supports sustainable organizational value.

Output: A product, feature, service, or activity produced by a team.

Outcome: A change in behaviour, condition, or capability resulting from an output.

Impact: A broader and more enduring consequence of outcomes.

Review Questions

Short Answer Questions

1. What is the difference between product discovery and product validation?
2. Distinguish a customer, a user, and a buyer.
3. Why is a prototype not, by itself, evidence of product–market fit?
4. Define output, outcome, and impact.
5. Name five categories of uncertainty relevant to product decisions.

Long Answer Questions

1. Explain how a product team can convert an initial product idea into testable hypotheses.
2. Discuss the dimensions of evidence quality and explain why quantitative evidence is not automatically superior to qualitative evidence.
3. Explain product–market fit as a multidimensional and evolving condition.
4. Compare discovery and delivery, and explain why they should operate as a continuous loop.
5. Discuss the ethical and governance responsibilities involved in product research and validation.

Analytical / Application Questions

1. A team claims that 20,000 downloads prove that its budgeting application has product–market fit. Critically assess this claim and propose a stronger evidence plan.
2. Design three experiments for a proposed service that helps small retailers forecast inventory demand. For each experiment, identify the assumption, method, evidence threshold, and principal limitation.
3. A product improves the number of completed online applications but increases abandonment among users with disabilities. Analyze the situation using desirability, usability, legitimacy, outputs, outcomes, and impacts. Recommend a responsible product decision.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes product discovery from product validation?

A. Discovery builds the final product, while validation manages the project schedule.

B. Discovery investigates problems and opportunities, while validation tests whether important claims are sufficiently supported.

C. Discovery measures revenue, while validation writes technical requirements.

D. Discovery occurs only after launch, while validation occurs only before ideation.

Correct Answer: B. Discovery investigates problems and opportunities, while validation tests whether important claims are sufficiently supported.

Question 2

Which evidence is generally closest to demonstrating sustained customer behaviour?

A. A participant says the product sounds useful.

B. A visitor clicks an advertisement.

C. A customer repeatedly uses the product in a realistic context and renews payment.

D. A product manager believes the problem is important.

Correct Answer: C. A customer repeatedly uses the product in a realistic context and renews payment.

Question 3

Which of the following is primarily an outcome rather than an output?

A. A dashboard is released.

B. Five training sessions are delivered.

C. A new API is deployed.

D. Advisors contact at-risk students earlier.

Correct Answer: D. Advisors contact at-risk students earlier.

Question 4

A product is technically possible but customers do not value it. Which dimension is most directly failing?

A. Desirability

B. Feasibility

C. Security

D. Delivery capacity

Correct Answer: A. Desirability

Question 5

Why should a team define an experiment’s decision rule before reviewing its results?

A. To guarantee a positive result.

B. To prevent evidence from being interpreted selectively after the result is known.

C. To eliminate the need for qualitative research.

D. To ensure the sample is statistically representative.

Correct Answer: B. To prevent evidence from being interpreted selectively after the result is known.

Question 6

Which statement about product–market fit is most accurate?

A. It is proven by a large number of downloads alone.

B. It is a one-time milestone that does not change after launch.

C. It concerns sustained customer value and adoption under viable market and economic conditions.

D. It is identical to high customer satisfaction in a usability test.

Correct Answer: C. It concerns sustained customer value and adoption under viable market and economic conditions.

Question 7

A team observes customers struggling to complete a task with a clickable prototype. What does this evidence most directly address?

A. Usability

B. Market size

C. Long-term profitability

D. Organizational impact

Correct Answer: A. Usability

Question 8

Which example is an impact rather than an output or immediate outcome?

A. A reminder feature is released.

B. Users receive more appointment confirmations.

C. The service reduces avoidable missed appointments.

D. Community health access improves over time.

Correct Answer: D. Community health access improves over time.

Question 9

Why is methodological triangulation useful in product discovery?

A. It guarantees that every hypothesis is true.

B. It combines complementary methods to examine a proposition from different perspectives.

C. It replaces the need to define a target customer.

D. It ensures that qualitative research has no bias.

Correct Answer: B. It combines complementary methods to examine a proposition from different perspectives.

Question 10

A product team ranks assumptions by the consequence of being wrong and the uncertainty surrounding each assumption. What is the main purpose of this practice?

A. To prioritize the most important learning before major commitment.

B. To calculate exact product revenue.

C. To replace customer research with internal judgement.

D. To determine the final visual design.

Correct Answer: A. To prioritize the most important learning before major commitment.