Problem Framing and Opportunity Definition

Introduction

Entrepreneurial innovation rarely begins with a perfectly defined problem. It begins with an observation: customers abandon a service, employees create workarounds, a community remains underserved, or a new technology changes what is possible. The initial observation is not yet a problem definition. It may be a symptom, an isolated incident, an assumption, or an opportunity signal.

Problem framing is the disciplined process of deciding what situation deserves attention, for whom, under what conditions, and with what boundaries. Opportunity definition then translates a well-understood problem into a strategically relevant area for innovation. Together, these activities prevent teams from rushing into solution development before understanding the system that produces the difficulty.

For entrepreneurs, this distinction is critical. A weakly framed problem produces attractive but irrelevant products, while a well-framed problem can reveal several possible business models. For example, “students need a better transport app” frames a solution prematurely. “Students cannot reliably coordinate affordable travel to evening classes because information, payment, and trust are fragmented” defines a broader opportunity without prescribing a particular solution.

This chapter develops methods for diagnosing root causes, mapping systems, constructing point-of-view statements and design challenges, generating effective ‘How Might We’ questions, and prioritizing opportunities according to impact, urgency, and strategic fit.

Learning Objectives

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

1. Distinguish symptoms, proximate causes, root causes, problems, and opportunities.
2. Use systems maps and causal analysis to examine relationships among actors, events, structures, and feedback loops.
3. Apply the Five Whys critically rather than mechanically.
4. Construct evidence-based point-of-view statements, design challenges, and ‘How Might We’ questions.
5. Prioritize problem areas using impact, urgency, feasibility, and strategic fit.
6. Recognize ethical risks, framing biases, and limitations in problem-definition practices.
7. Convert a selected problem frame into an actionable entrepreneurial opportunity.

1. From Symptoms to Opportunity Areas

A symptom is an observable indication that something is not working as intended. Examples include high customer churn, long waiting times, repeated complaints, low employee adoption, or excessive waste. A cause is a condition that contributes to the symptom. A root cause is a deeper condition whose removal or alteration could substantially change the system’s behaviour.

The term “root cause” should be used carefully. Complex social and commercial problems rarely have one single root. They usually arise from interacting causes: incentives, rules, infrastructure, habits, power relationships, information gaps, and resource constraints. Root-cause analysis therefore seeks influential causal conditions, not a simplistic final answer.

A useful distinction is:

A problem statement describes an undesirable condition from the perspective of affected people or organizations. An opportunity statement describes a possibility for creating value by improving that condition. The two should not be confused with a solution statement. “Build an artificial-intelligence chatbot” is a solution hypothesis; “help first-time applicants understand requirements and recover from errors” is an opportunity direction.

Problem framing as a boundary decision

Every frame includes boundaries. It determines:

• whose experience is considered;
• which time period and location are included;
• what outcomes count as success;
• which constraints are treated as fixed;
• which causes are open to intervention; and
• which issues are excluded for the present inquiry.

Boundaries are useful because investigation without limits becomes unmanageable. They are also political and ethical because excluded stakeholders may bear the consequences of the proposed intervention. A responsible team makes its boundaries explicit and revisits them when evidence challenges the original frame.

2. Systems Thinking for Entrepreneurial Problems

Systems thinking examines a problem as part of a network of relationships rather than as an isolated event. A system contains actors, resources, processes, rules, technologies, incentives, and feedback relationships. A systems perspective is especially important when an intervention in one part of a system creates unintended effects elsewhere.

2.1 Elements of a systems map

A practical systems map may include:

• Actors: customers, suppliers, regulators, employees, partners, communities, and competitors.
• Resources: money, information, time, skills, infrastructure, materials, and trust.
• Activities: purchasing, producing, approving, delivering, monitoring, and repairing.
• Structures: policies, contracts, organizational hierarchies, platforms, and standards.
• Flows: movement of goods, data, payments, people, and decisions.
• Outcomes: revenue, access, safety, satisfaction, emissions, equity, and resilience.
• Feedback loops: processes through which an outcome reinforces or counteracts its own development.

A simple causal link can be represented as “A influences B.” A systems map should not imply that every relationship is certain. Teams should label links as evidence-based, hypothesized, or unknown. This prevents attractive diagrams from being mistaken for validated explanations.

Figure: An illustrative systems map showing how actors, platforms, regulation, trust, and outcomes interact.

2.2 Causal loops

A reinforcing loop amplifies change. For example, better service reliability may increase customer use; increased use may generate revenue; revenue may fund further reliability improvements. A balancing loop counteracts change. For example, rapid growth may increase congestion, which reduces service quality and limits further growth.

Teams should ask four questions when reviewing a map:

1. What changes over time?
2. Which variables influence one another?
3. Where are delays between action and outcome?
4. Where could an intervention produce unintended consequences?

Systems maps are exploratory models, not proof of causality. They become stronger when supported by interviews, observation, operational data, experiments, and relevant research.

3. Causal Analysis and the Five Whys

Causal analysis investigates why an undesirable outcome occurs. It is most useful when the team distinguishes causal claims from correlations. If two variables change together, that does not establish that one causes the other. Alternative explanations, reverse causality, common causes, and measurement error must be considered.

3.1 The Five Whys method

The Five Whys is a structured questioning technique in which the team repeatedly asks why an observed problem occurred. The number five is a heuristic, not a rule. The process should stop when the team reaches a condition that is sufficiently deep, actionable, and supported by evidence.

Illustrative chain:

• Problem: A small retailer frequently runs out of essential products.
• Why 1: Replenishment orders are placed after stock is already low.
• Why 2: Staff do not have a reliable view of inventory across locations.
• Why 3: Sales and warehouse records are updated in different systems.
• Why 4: The organization adopted systems independently by department.
• Why 5: There was no ownership of end-to-end inventory information.

The final statement is not automatically the root cause. It is a hypothesis requiring investigation. Interviews may reveal that the deeper issue is an incentive structure, a budget constraint, or a supplier contract.

3.2 Strengths and weaknesses

The Five Whys is inexpensive, participatory, and easy to communicate. It can expose assumptions that remain hidden in routine operations. However, it has important limitations:

• It tends to produce a single causal chain when several causes operate together.
• The result depends heavily on the knowledge and power of participants.
• It may blame individuals for failures produced by system design.
• Different teams may generate different chains from the same event.
• It can confuse “why did this happen?” with “who is responsible?”

To improve reliability, use multiple evidence sources, create parallel branches where appropriate, distinguish facts from hypotheses, and ask what conditions would have prevented the event. A fishbone diagram, fault tree, process walk-through, or causal-loop map can complement the Five Whys.

3.3 Causal claims and intervention points

A useful intervention point has three properties: it influences an important outcome, it is accessible to the entrepreneur or partner, and changing it does not create unacceptable harm. A visible symptom may be easy to change but have little leverage. A structural cause may have high leverage but require regulatory, organizational, or cultural change.

A practical causal-analysis record can include:

4. Evidence Before Framing

Good framing combines empathy with analytical discipline. Teams should gather evidence from several perspectives rather than rely only on the loudest stakeholder or the founding team’s assumptions.

Useful methods include:

• contextual interviews;
• direct observation and shadowing;
• diary studies;
• customer-support and transaction-data analysis;
• journey mapping;
• review of policies and regulations;
• competitor and substitute analysis; and
• participatory workshops with affected communities.

Evidence should be recorded with source, date, context, and confidence. A quotation is evidence of what one person said; it is not automatically evidence of population-wide behaviour. Quantitative data may show frequency but not meaning. Qualitative data may reveal meaning but not prevalence. Triangulation combines these strengths.

Teams should also actively search for disconfirming evidence. If every interview is interpreted as support for the original idea, research becomes persuasion rather than inquiry.

5. Point-of-View Statements

A point-of-view (POV) statement expresses a meaningful, actionable insight about a particular user or stakeholder. A common structure is:

[User] needs [need] because [insight].

For example:

First-time micro-entrepreneurs need a simple way to understand business registration requirements because uncertainty about consequences, rather than unwillingness, causes them to postpone formalization.

A strong POV identifies a specific user, a genuine need, and an insight explaining why the need matters. It does not prescribe a product. “A user needs a mobile app” is weak because the app is a solution. “A user needs confidence that a registration decision is reversible and affordable” leaves room for multiple interventions.

Qualities of a strong POV

A strong statement is:

• human-centred: grounded in lived experience;
• specific: focused enough to guide design;
• generative: broad enough to permit several solutions;
• evidence-based: linked to research;
• tension-aware: recognizes competing needs or constraints; and
• actionable: suggests where innovation might create value.

POVs should be tested with stakeholders. A team must avoid representing vulnerable groups without giving them opportunities to correct, reject, or refine the interpretation.

6. Design Challenges and ‘How Might We’ Questions

A design challenge converts a POV into an innovation brief. It establishes the intended beneficiary, the desired change, and relevant boundaries. For example:

How might we help first-time micro-entrepreneurs understand and complete registration without increasing their financial or administrative risk?

The phrase “How Might We” is useful because:

• How signals that the team is seeking a way forward.
• Might preserves uncertainty and experimentation.
• We recognizes collective responsibility rather than placing the burden solely on the user.

6.1 Characteristics of effective HMW questions

An effective question is neither too broad nor too narrow. Compare:

• Too broad: “How might we improve entrepreneurship?”
• Too narrow: “How might we add a blue confirmation button to page three?”
• More useful: “How might we help applicants recover from registration errors without restarting the process?”

A good HMW question:

1. names or implies a meaningful user;
2. focuses on an important need or outcome;
3. avoids embedding one solution;
4. reflects a real tension or opportunity;
5. is feasible to investigate within the project scope; and
6. allows several promising answers.

Teams can generate multiple HMW questions from one POV by changing the emphasis: prevent the problem, reduce its severity, improve the experience, reach underserved users, change incentives, or redesign the surrounding system. They should then test whether the questions are sufficiently distinct and strategically relevant.

7. Defining the Opportunity

Opportunity definition links a human problem to value creation and strategic action. It asks not simply, “Can we solve this?” but also:

• Who experiences the problem and how often?
• How costly, risky, or frustrating is it?
• What alternatives do people currently use?
• Who pays, who benefits, and who may be harmed?
• What capabilities and assets can the venture access?
• What regulatory, technical, and ethical constraints apply?
• Why is this opportunity important now?

A useful opportunity statement has the form:

For [target group] who experience [important unmet need] in [context], there is an opportunity to create [desired outcome] because [evidence and enabling conditions].

This statement remains solution-neutral while identifying a plausible value proposition. It should be treated as a hypothesis to validate, not as a market fact.

Jobs, pains, and gains

A complementary approach is to identify the customer’s functional, emotional, and social jobs; the pains that make those jobs difficult; and the gains that customers value. Entrepreneurs should distinguish a stated preference from an underlying need. Customers may request faster delivery, but the deeper need may be predictability, control, or reduced coordination effort.

Opportunity definition also requires attention to non-customers and affected third parties. A service that creates convenience for paying customers but transfers costs to workers or communities is not automatically a responsible opportunity.

8. Prioritizing Problems and Opportunities

A team normally discovers more problems than it can address. Prioritization makes trade-offs explicit. The three required dimensions are impact, urgency, and strategic fit. Feasibility and ethical risk are also important decision factors.

8.1 Evaluation dimensions

• Impact: magnitude and breadth of value created by improvement. It may include financial, social, environmental, safety, or learning impact.
• Urgency: the cost of delay, including escalation, regulation, seasonal timing, customer loss, or irreversible harm.
• Strategic fit: alignment with the venture’s purpose, capabilities, assets, partnerships, positioning, and long-term direction.
• Feasibility: technical, operational, financial, and organizational ability to act.
• Evidence strength: confidence that the problem is real, important, and experienced by the defined users.
• Ethical risk: likelihood that the intervention produces discrimination, surveillance, exclusion, dependency, or other harm.

A simple scoring model can structure discussion. Let each criterion be scored from 1 to 5. If the team uses weights, the weighted score is:

Here, S is the total priority score, wᵢ is the weight assigned to criterion i, and rᵢ is the rating for that criterion. The ratings are ordinal judgements, not precise measurements; therefore, the score supports deliberation rather than replacing it. All criteria must use clearly defined scales, and weights must be agreed before scores are discussed.

For example, a team may assign impact 0.35, urgency 0.25, strategic fit 0.20, feasibility 0.10, and evidence strength 0.10. For a proposed problem rated 5, 4, 3, 4, and 3 respectively:

S = (0.35×5) + (0.25×4) + (0.20×3) + (0.10×4) + (0.10×3) = 4.05

The result is 4.05 out of 5. It does not prove that the problem is the best choice. A high ethical-risk rating, for example, may require mitigation or exclusion even when the priority score is high.

8.2 Prioritization matrix

A two-dimensional matrix can compare urgency and impact, while strategic fit is represented by colour, size, or a separate screen. Typical categories are:

Avoid false precision. A score difference of 4.1 versus 4.0 may not be meaningful if the evidence is weak. Sensitivity analysis is useful: change the weights or ratings and see whether the ranking changes. If it changes substantially, the decision is uncertain and should be treated as a learning priority.

9. Worked Application: FreshRoute Food Access

The following is a fictional illustrative case.

Background

FreshRoute is a proposed social enterprise serving low-income households in a rapidly growing city. The founding team observes that small retailers in peripheral neighbourhoods frequently have fresh produce shortages, while wholesalers discard unsold inventory. The initial idea is to create an app that connects wholesalers with consumers.

Problem diagnosis

Interviews reveal that consumers do not merely lack information. They face unpredictable supply, limited cash at particular times of the week, transport costs, and concerns about food quality. Retailers report that demand forecasts are unreliable and that accepting digital orders creates fulfilment work. Wholesalers are reluctant to deliver small quantities because route economics are poor.

A systems map identifies four interacting factors: uncertain demand, fragmented ordering, limited cold-chain capacity, and retailer cash-flow constraints. A Five Whys discussion about produce stockouts produces this chain:

1. Retailers order too little fresh produce.
2. They fear spoilage if demand is lower than expected.
3. Demand varies by day and household cash availability.
4. Retailers lack affordable demand signals and flexible replenishment.
5. The distribution system is designed for larger, predictable buyers rather than small neighbourhood outlets.

The fifth statement is a systemic hypothesis. It suggests that an intervention could involve pooled demand, flexible delivery, credit, storage, or forecasting—not only a consumer app.

POV and HMW question

A research-based POV is:

Neighbourhood retailers need a low-risk way to replenish fresh produce because uncertain demand and limited cash make spoilage more threatening than lost sales.

Possible HMW questions include:

• How might we help retailers test demand before committing cash?
• How might we coordinate small orders without making delivery uneconomic?
• How might we reduce spoilage while preserving affordable access?

The second question is selected for an initial experiment because it addresses a system bottleneck and fits FreshRoute’s partnership capability.

Prioritization

The team rates the opportunity using five criteria. The weighted score is 4.05 out of 5, as calculated above. However, a stakeholder workshop identifies a risk: a data-driven allocation system could favour retailers with better connectivity and exclude informal vendors. The team therefore adds an inclusion requirement: the pilot must accept orders through assisted telephone or in-person channels, and performance must be assessed by neighbourhood and retailer type.

Approach and pilot

FreshRoute pilots pooled ordering with three retailers and one wholesaler. Orders are collected twice weekly through a lightweight messaging channel and a community coordinator. The pilot measures stockout frequency, spoilage, retailer cash exposure, delivery cost, and consumer access. It does not assume that app adoption equals success.

Outcome and learning

The pilot shows improved availability but reveals that delivery costs remain high for very small orders. The team revises the opportunity from “build a marketplace” to “coordinate predictable neighbourhood replenishment through trusted local intermediaries.” This opens several possible models: scheduled distribution, retailer cooperatives, subscription baskets, or shared cold storage.

The case demonstrates five principles:

1. The initial solution idea may conceal the real system problem.
2. Root-cause analysis should include economic and institutional conditions.
3. A HMW question should open a solution space, not dictate a product.
4. Prioritization must include strategic and ethical considerations.
5. Experiments should test the opportunity logic and unintended effects, not merely user interface preference.

10. Ethics, Governance, and Responsible Framing

Problem framing is not neutral. The language used can define who is seen as deficient and who is seen as responsible. Describing people as “unbanked” may obscure the barriers created by product design, documentation rules, or institutional exclusion. A responsible frame examines both individual experience and structural conditions.

Important safeguards include:

• obtain informed consent for interviews and observation;
• protect personal and commercially sensitive data;
• avoid collecting data that are unnecessary for the decision;
• explain how research findings will be used;
• include marginalized and less visible stakeholders;
• test for discriminatory effects across groups;
• distinguish participation from endorsement; and
• provide channels for correction or withdrawal where feasible.

When AI is used to cluster complaints, summarize interviews, or identify patterns, human review remains essential. Automated analysis may reproduce biased sampling, misinterpret culturally specific language, or give a false appearance of objectivity. Teams should document data provenance, uncertainty, model limitations, and the consequences of error. AI may assist analysis, but it should not silently determine whose problem is prioritized.

11. Common Failure Modes and Best Practices

Failure modes

Solution-first framing: The team defines the problem around an existing technology. This narrows exploration prematurely.

Single-cause thinking: A complex problem is attributed to one person or one factor. This encourages blame and weak interventions.

Stakeholder omission: Non-paying users, workers, suppliers, regulators, or communities are excluded from the frame.

Metric substitution: A convenient measure, such as clicks or registrations, is treated as the outcome that matters.

Premature prioritization: Teams score ideas before agreeing on definitions and evidence standards.

Confirmation bias: Research is used to defend a preferred concept rather than challenge it.

False precision: Numerical scores are presented as objective despite subjective ratings and uncertain evidence.

Best practices

1. State the initial frame and its assumptions explicitly.
2. Separate observations, interpretations, hypotheses, and decisions.
3. Map causes at individual, organizational, market, and policy levels.
4. Use multiple research methods and seek disconfirming evidence.
5. Formulate several POVs before selecting one.
6. Write HMW questions that are focused but solution-neutral.
7. Include impact, urgency, strategic fit, feasibility, evidence, and ethics in prioritization.
8. Use small experiments to reduce the most consequential uncertainties.
9. Revisit the frame when new evidence changes the system understanding.
10. Document who benefits, who pays, who decides, and who may be harmed.

Contemporary Developments

Contemporary entrepreneurship increasingly addresses climate adaptation, public health, inclusive finance, platform work, circular production, and responsible digital services. These domains require opportunity definitions that account for externalities and long time horizons. For example, a circular-economy opportunity may need to frame material flows, repair incentives, customer convenience, producer responsibility, and recovery infrastructure together.

Data-rich organizations can identify patterns faster, but more data do not automatically produce better framing. Data may overrepresent digitally visible users and underrepresent people who avoid formal systems. Combining computational pattern detection with contextual inquiry and participatory design is therefore increasingly important.

In uncertain environments, the most valuable outcome of early problem framing may be not a final problem statement but a better question and a clearer learning agenda. Entrepreneurial teams should ask which assumption, if false, would most undermine the opportunity, and then design the least costly credible test.

Chapter Summary

Problem framing converts observations and symptoms into an evidence-based understanding of a situation, while opportunity definition identifies a promising and responsible space for value creation. Systems maps reveal actors, structures, flows, feedback loops, and unintended consequences. Causal analysis and the Five Whys help investigate contributing conditions, but they must be supported by evidence and must avoid reducing complex problems to one cause or blaming individuals.

Point-of-view statements express a specific user’s need and the insight behind it. Design challenges and ‘How Might We’ questions translate those insights into focused but solution-neutral innovation directions. Effective questions are specific enough to guide inquiry and open enough to support multiple solutions.

Prioritization should consider impact, urgency, strategic fit, feasibility, evidence strength, and ethical risk. Weighted scores can structure judgement, but they do not eliminate uncertainty or replace stakeholder deliberation. Finally, responsible entrepreneurs recognize that frames distribute attention and power. They include affected stakeholders, protect data, challenge assumptions, and use experiments to test both value creation and unintended consequences.

Key Terms

Problem framing: Defining the boundaries, stakeholders, context, and desired outcome of a problem.

Opportunity definition: Describing a potential area for value creation based on an important unmet need.

Symptom: An observable indication of an undesirable condition.

Root cause: An influential underlying condition that contributes to an outcome and may be actionable.

Systems thinking: Analysis of relationships, structures, flows, and feedback within a wider system.

Systems map: A visual representation of actors, elements, and relationships in a system.

Causal analysis: Systematic investigation of conditions that contribute to an outcome.

Five Whys: An iterative questioning method for exploring underlying causes.

Feedback loop: A relationship in which an outcome influences future system behaviour.

Point-of-view statement: A concise, human-centred interpretation of a user’s need and insight.

Design challenge: A focused brief that defines the change an innovation effort seeks to explore.

How Might We question: An open, solution-neutral question that frames a design opportunity.

Stakeholder: A person or organization affected by, involved in, or able to influence a system.

Impact: The magnitude and breadth of value or harm associated with a problem or intervention.

Urgency: The importance of acting now rather than later.

Strategic fit: Alignment between an opportunity and a venture’s purpose, capabilities, and direction.

Triangulation: Combining multiple sources or methods to improve confidence in an interpretation.

Confirmation bias: The tendency to favour evidence that supports existing beliefs.

Ethical risk: The possibility that an intervention produces unacceptable harm or inequity.

Opportunity hypothesis: A provisional claim about a valuable problem area that requires testing.

Review Questions

Short Answer Questions

1. Distinguish a symptom, a proximate cause, and a root cause.
2. What is the purpose of a systems map in problem framing?
3. Why should the Five Whys not be treated as a mechanical five-step formula?
4. State the basic structure of a point-of-view statement.
5. What are the meanings of “How,” “Might,” and “We” in an HMW question?

Long Answer Questions

1. Explain how systems thinking can reveal unintended consequences of an entrepreneurial intervention. Use an example.
2. Discuss the strengths and limitations of the Five Whys and explain how it can be combined with other causal-analysis methods.
3. Compare a weak and a strong point-of-view statement. Explain how the wording affects the solution space.
4. Explain the difference between a problem statement, an opportunity statement, and a solution statement.
5. Discuss the ethical responsibilities involved in framing problems experienced by marginalized stakeholders.

Analytical / Application Questions

1. A university observes that many students do not complete financial-aid applications. Construct a causal chain, identify at least three stakeholders, write one POV statement, and formulate two HMW questions.
2. A venture has three opportunity areas: reducing delivery delays, improving accessibility for disabled users, and lowering packaging waste. Design a prioritization framework using impact, urgency, strategic fit, feasibility, evidence strength, and ethical risk. Explain how you would handle conflicting scores.
3. Select a familiar service and create a systems map in written form. Identify one reinforcing or balancing feedback loop, one possible unintended consequence, and one low-cost experiment that would test the opportunity hypothesis.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes an opportunity from a solution?

A. An opportunity identifies a valuable unmet need without prescribing one product.

B. An opportunity is always a technology specification.

C. An opportunity is a list of features selected by the founder.

D. An opportunity is the same as a completed business plan.

Correct Answer: A. An opportunity identifies a valuable unmet need without prescribing one product.

Question 2

What is the primary purpose of a systems map?

A. To calculate a venture’s exact market share.

B. To display relationships among actors, structures, flows, and outcomes.

C. To replace all forms of customer research.

D. To guarantee that a proposed solution will succeed.

Correct Answer: B. To display relationships among actors, structures, flows, and outcomes.

Question 3

Why is the number five in the Five Whys method considered a heuristic?

A. The method must always use exactly five questions.

B. Five questions are required by statistical law.

C. The appropriate depth depends on the complexity and evidence of the problem.

D. The fifth question is always the correct root cause.

Correct Answer: C. The appropriate depth depends on the complexity and evidence of the problem.

Question 4

Which point-of-view statement is strongest?

A. Users need our mobile app to manage appointments.

B. Customers need more features because competitors have them.

C. First-time applicants need confidence that they can recover from errors without restarting because uncertainty causes abandonment.

D. Everyone needs a faster and better service.

Correct Answer: C. First-time applicants need confidence that they can recover from errors without restarting because uncertainty causes abandonment.

Question 5

What characteristic should an effective HMW question have?

A. It should prescribe a single technical solution.

B. It should be broad enough to ignore the target user.

C. It should focus on a meaningful need while allowing several possible solutions.

D. It should contain a completed implementation plan.

Correct Answer: C. It should focus on a meaningful need while allowing several possible solutions.

Question 6

In the weighted scoring model, what does wᵢ represent?

A. The rating of a problem on criterion i

B. The weight assigned to criterion i

C. The number of stakeholders in criterion i

D. The total priority score

Correct Answer: B. The weight assigned to criterion i

Question 7

Using weights 0.5 and 0.5, a problem rated 4 for impact and 2 for urgency receives what weighted score?

A. 2

B. 3

C. 4

D. 6

Correct Answer: B. 3

Question 8

Which practice best reduces confirmation bias during problem framing?

A. Interviewing only people who agree with the initial idea

B. Seeking disconfirming evidence and recording alternative explanations

C. Ignoring evidence that conflicts with the business model

D. Scoring opportunities before defining criteria

Correct Answer: B. Seeking disconfirming evidence and recording alternative explanations

Question 9

What does strategic fit primarily assess?

A. Whether the opportunity aligns with the venture’s purpose, capabilities, and direction

B. Whether every customer will immediately purchase the product

C. Whether the problem has only one cause

D. Whether the team can avoid stakeholder participation

Correct Answer: A. Whether the opportunity aligns with the venture’s purpose, capabilities, and direction

Question 10

Why should ethical risk be considered in opportunity prioritization?

A. It ensures that high-revenue opportunities are always selected.

B. It identifies possible harms, exclusion, discrimination, or unintended consequences.

C. It eliminates the need for feasibility analysis.

D. It converts qualitative judgements into objective facts.

Correct Answer: B. It identifies possible harms, exclusion, discrimination, or unintended consequences.