Managing Innovation in Entrepreneurial Organizations

Introduction

Innovation is not simply the generation of novel ideas. It is the disciplined process of identifying opportunities, developing and implementing new or improved products, services, processes, business models, or organizational practices that create value. In entrepreneurial organizations, innovation is especially strategic because limited resources, uncertain markets, and rapid competitive change make the quality of innovation decisions highly consequential.

Entrepreneurial innovation management connects opportunity recognition with execution. It requires leaders to decide which opportunities deserve investment, design processes that convert uncertainty into knowledge, assemble capable teams, and create conditions in which people can experiment without being careless. It also requires balancing exploration—searching for new possibilities—with exploitation—improving and scaling established activities.

A useful distinction is between an invention, which is a new idea or technical possibility, and an innovation, which is an implemented solution that produces recognized value. An innovation may be technologically novel, but novelty is not essential: a new application of an existing technology, a simpler distribution model, or a redesigned customer experience can also be innovative.

Learning Objectives

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

1. Explain the strategic role and major types of innovation in entrepreneurial organizations.
2. Design an innovation process suited to uncertainty, risk, and available resources.
3. Compare stage-gate, agile, lean startup, and ambidextrous approaches.
4. Design effective innovation teams and portfolios.
5. Evaluate the influence of leadership, culture, incentives, psychological safety, and collaboration.
6. Diagnose resistance to innovation and select appropriate change interventions.
7. Apply innovation-management principles to an entrepreneurial case.

1. Innovation as a Managed Organizational Capability

Innovation management is the coordinated direction of people, knowledge, resources, decisions, and learning toward valuable change. It is a capability rather than a single department or event. A firm may have creative employees but weak innovation management if ideas are not evaluated, funded, tested, or implemented.

Innovation can be classified in several overlapping ways:

Incremental innovation improves an existing offer or process. Radical innovation introduces a substantially different technology, market proposition, or operating logic. Architectural innovation rearranges existing components in a new system configuration. The term disruptive innovation should be used carefully: in its formal strategic sense, it describes a process in which a simpler or more accessible offering initially serves less-demanding customers or creates a new market and later challenges established firms. It does not mean any innovation that is merely dramatic or successful.

Innovation creates several forms of uncertainty:

• Technical uncertainty: Can the solution be built reliably?
• Market uncertainty: Do customers have the problem, and will they adopt the solution?
• Business-model uncertainty: Can the organization capture sufficient value?
• Regulatory and social uncertainty: Is the solution lawful, acceptable, and responsible?
• Execution uncertainty: Can the organization deliver and scale it?

The management response should match the uncertainty. Detailed plans are useful when requirements are stable; experiments and short feedback cycles are more appropriate when assumptions are unclear.

2. Designing an Innovation Process

A robust innovation process is a decision system, not merely a funnel that filters ideas. It should answer five questions:

1. What opportunities are strategically relevant?
2. What assumptions must be tested first?
3. What evidence is sufficient to continue, revise, pause, or stop?
4. Who makes each decision, and who is accountable for results?
5. How will learning be recorded and transferred?

A general process contains the following connected activities:

Opportunity framing

The organization defines a customer, societal, or operational problem rather than prematurely selecting a solution. Good opportunity statements identify the affected user, the context, the unmet need, and the strategic reason for acting. Design research, observation, interviews, market analysis, trend scanning, and internal data can contribute evidence.

Idea generation and concept development

Divergent methods such as brainstorming, design research, analogy, morphological analysis, and customer co-creation generate alternatives. Convergent methods then compare alternatives against criteria such as desirability, feasibility, viability, strategic fit, ethics, and sustainability. Brainstorming is most useful when separated from early criticism; later evaluation is essential.

Experimentation and validation

Teams convert uncertain assumptions into testable hypotheses. A hypothesis should specify what is believed, for whom, under what conditions, and what evidence would change the decision. Experiments can include prototypes, landing pages, simulations, concierge services, technical spikes, pilot programs, or controlled process trials.

Development and implementation

Once evidence supports continued investment, the organization develops the solution, establishes operating processes, secures resources, manages compliance, and prepares customers and employees for adoption. Innovation fails frequently at this transition because discovery work is not connected to implementation ownership.

Scaling and learning

Scaling involves capacity, quality, economics, supply, distribution, support, cybersecurity, and governance. Post-launch reviews should examine both outcomes and assumptions. A project that is stopped after disproving an important assumption may represent successful innovation management rather than failure.

Decision economics under uncertainty

Entrepreneurs often use expected monetary value to compare uncertain alternatives. The general form is:

where p_i is the probability of outcome i, V_i is the monetary value of that outcome, and C is the investment cost. The probabilities should represent the decision maker’s best estimates, and outcomes should be mutually exclusive and collectively exhaustive. EMV is a decision aid, not a prediction; it can conceal distributional, ethical, strategic, or irreversible risks.

For example, an experiment costing $20,000 has a 30% probability of producing a benefit valued at $100,000 and a 70% probability of producing no financial benefit. Its EMV is:

The positive EMV does not automatically justify the experiment. Management must also consider cash constraints, timing, legal exposure, opportunity cost, and whether the probabilities are credible.

3. Comparing Innovation Approaches

No single process is universally superior. The appropriate approach depends on uncertainty, interdependence, regulatory requirements, cost of failure, and the organization’s ability to learn.

Stage-gate

Stage-gate systems divide innovation into stages—often discovery, concept, business case, development, testing, and launch—with formal gates between them. At each gate, decision makers may continue, redirect, hold, or terminate the project.

Strengths include resource discipline, visibility, cross-functional review, risk control, and coordination for complex products. Weaknesses arise when gates become bureaucratic approvals, when forecasts are treated as facts, or when teams avoid risky but valuable ideas to protect their budgets. Stage-gate works best when technical and market requirements can be specified progressively and when regulatory or capital commitments require formal review.

Agile innovation

Agile approaches organize work into short cycles, small deliverables, frequent feedback, and reprioritized backlogs. Cross-functional teams collaborate closely, and working increments are valued over extensive documentation, although documentation remains necessary where safety, regulation, or knowledge transfer requires it.

Agile is effective when requirements evolve and customer or user feedback is available. It does not eliminate strategy, architecture, quality assurance, or leadership. A team can deliver increments rapidly while still building the wrong product if the underlying problem is misunderstood.

Lean startup

The lean startup approach emphasizes hypotheses, minimum viable products, validated learning, and the build–measure–learn cycle. A minimum viable product (MVP) is the smallest version of an offering that enables meaningful learning about a critical assumption. It is not necessarily a low-quality product and should not expose users to unacceptable risk.

Teams use evidence to decide whether to persevere, pivot, or stop. A pivot changes a core element of the strategy while preserving the learning gained. Useful measures should test behavior rather than enthusiasm; for example, payment, retention, repeat use, or referral is usually stronger evidence than positive interview comments alone.

Ambidextrous innovation

An ambidextrous organization manages exploration and exploitation simultaneously. Exploration involves experimentation, search, and uncertain new opportunities. Exploitation involves efficiency, reliability, standardization, and optimization of current operations.

These activities often require different structures and cultures. An exploratory team may need autonomy and tolerance for ambiguity, whereas an operating unit may require control and predictable performance. Senior leadership integrates the two by allocating resources, setting a common strategic direction, and creating pathways through which successful experiments can scale.

In practice, hybrid designs are common. A regulated medical-device venture may use lean experiments for customer discovery, agile methods for software components, and stage-gates for safety and regulatory decisions.

4. Innovation Teams and Collaboration

Innovation teams require more than technical expertise. They need problem understanding, customer insight, design capability, commercial judgment, operational knowledge, and the authority to act. A cross-functional team reduces handoff delays and exposes assumptions that a single-function group may overlook.

Important design choices include:

• Purpose: a clear problem and intended outcome.
• Membership: complementary expertise and constructive diversity.
• Decision rights: clarity about what the team can decide independently.
• Boundary access: direct contact with customers, suppliers, regulators, and operations.
• Time horizon: protection from constant reassignment to urgent operational work.
• Review rhythm: regular evidence-based decisions.
• Transition ownership: a named receiving unit for implementation and scaling.

Diversity is valuable when supported by inclusion. Differences in discipline, experience, culture, and perspective can improve problem framing and reduce groupthink, but only if team members can influence decisions and disagreement is treated as useful information.

Collaboration may be internal, interorganizational, or open. Universities, suppliers, customers, communities, and complementary ventures can provide knowledge and resources. Open innovation requires explicit agreements concerning intellectual property, data rights, confidentiality, publication, liability, and benefit sharing. Collaboration is not automatically beneficial: coordination costs, misaligned incentives, and knowledge leakage can outweigh its advantages.

A practical team charter should state the challenge, hypotheses, scope, decision authority, success measures, meeting norms, escalation route, and expected behavior when evidence contradicts the preferred idea.

5. Leadership, Culture, Incentives, and Psychological Safety

Innovation leadership is the creation of direction, conditions, and learning discipline. Vision without resource allocation is symbolic; experimentation without accountability is wasteful; accountability without psychological safety encourages concealment.

Leadership behaviors

Effective innovation leaders:

• frame meaningful strategic problems;
• protect experimentation from unnecessary interference;
• ask for evidence rather than demanding certainty;
• distinguish intelligent failure from negligence;
• remove organizational barriers;
• connect experiments to customers and operations;
• make timely stop, continue, and pivot decisions;
• model curiosity and willingness to revise beliefs.

Leaders should also manage the tension between inspiration and evaluation. A compelling idea deserves serious testing, not automatic funding.

Culture

An innovation-supportive culture combines ambition with disciplined learning. Its norms may include respectful challenge, rapid information sharing, customer orientation, experimentation, reflection, and recognition of contribution beyond successful launches. Culture is reinforced by what leaders fund, tolerate, measure, and promote—not by slogans alone.

Incentives

Innovation incentives are difficult because outcomes are uncertain and often delayed. Rewarding only successful launches can discourage risk taking and encourage teams to hide negative evidence. Rewarding activity alone can generate many experiments with little learning.

A balanced system recognizes:

1. quality of problem framing;
2. rigor and speed of learning;
3. responsible collaboration;
4. useful knowledge transfer;
5. validated customer or operational value;
6. successful implementation and scaling.

Team-based rewards are often preferable to purely individual rewards because innovation is interdependent. However, collective rewards should not eliminate individual accountability for ethical conduct, quality, or delivery.

Psychological safety

Psychological safety is a shared belief that people can ask questions, report concerns, admit mistakes, and offer dissenting views without humiliation or retaliation. It is not permissiveness, low standards, or freedom from consequences. A psychologically safe team can maintain high performance standards while making it safer to surface weak assumptions and early warnings.

Leaders can strengthen psychological safety by inviting dissent, responding appreciatively to bad news, conducting blameless learning reviews, distributing speaking time, and separating the evaluation of an idea from the worth of the person proposing it.

6. Innovation Portfolios and Resource Allocation

An innovation portfolio contains projects with different risk, time horizons, strategic purposes, and resource requirements. Managing a portfolio is not equivalent to selecting the projects with the highest individual forecast return. Projects interact: they may share platforms, capabilities, customers, or regulatory dependencies.

Portfolio review should consider:

• strategic fit;
• customer and societal value;
• technical and commercial uncertainty;
• expected resource demand;
• time to evidence and time to value;
• dependencies and concentration risk;
• reversibility of investment;
• legal, ethical, and sustainability implications;
• balance between core improvements and new opportunities.

A simple portfolio map may classify projects as core, adjacent, or transformational, while also displaying uncertainty and investment. Such maps are discussion tools, not universal laws. The often-repeated recommendation that organizations allocate a fixed percentage of funds to each category should not be applied mechanically; the appropriate balance depends on industry economics, capabilities, and strategic position.

Portfolio governance should use different evidence standards at different stages. Early projects should be judged mainly by learning progress and strategic relevance; later projects should be judged increasingly by adoption, quality, economics, and scalability. A common failure is to apply mature-business financial metrics to early discovery projects, causing potentially valuable experiments to be rejected before their assumptions are tested.

7. Managing Resistance and Organizational Change

Resistance to innovation is not always irrational. Employees may fear job loss, loss of status, competence gaps, customer harm, workload increases, or the abandonment of valued practices. Managers may resist because innovation threatens budgets, authority, performance targets, or established identity.

A useful diagnosis asks:

• What perceived loss is producing resistance?
• Is the innovation technically or commercially credible?
• Who has not been consulted?
• What capabilities and resources are missing?
• Which current incentives reward the old behavior?
• Are leaders communicating a consistent rationale?

Change interventions should match the cause. Training addresses capability gaps; participation addresses ownership; redesigned incentives address conflicting signals; phased pilots reduce perceived risk; transparent communication addresses uncertainty; and negotiation may be necessary where interests genuinely conflict. Manipulation and forced enthusiasm are poor substitutes for trust.

A change plan can proceed through four linked tasks: establish the case for change, involve affected stakeholders in design, run a bounded pilot with explicit evidence criteria, and institutionalize successful practices through systems, roles, metrics, and routines. Leaders should also preserve valuable existing practices rather than treating all resistance as an obstacle.

8. Metrics and Innovation Accounting

Innovation metrics should reflect the stage and purpose of the work. Input metrics include funding, team time, and number of experiments. Activity metrics include prototypes built or customer tests completed. Learning metrics include the percentage of critical assumptions tested and the number of decisions changed by evidence. Outcome metrics include adoption, retention, margin, process quality, social impact, and return on investment.

For a simple investment, return on investment may be expressed as:

ROI is dimensionless, often reported as a percentage. It is meaningful only when benefit and investment are defined consistently, measured over a stated period, and adjusted appropriately for uncertainty. It is less suitable as the sole measure for early experiments whose primary output is information.

A product team might track activation rate:

The numerator and denominator must use the same population and time window, and the activation action must be defined before examining results. Otherwise, teams may change definitions until the metric looks favorable.

Good governance combines quantitative indicators with qualitative evidence, customer narratives, safety reports, and expert judgment. Metrics can be gamed; therefore, leaders should examine how a measure could be improved without creating real value.

9. Ethics, Governance, and Technology

Innovation can create benefits and harms. Responsible management considers privacy, cybersecurity, accessibility, worker impact, environmental effects, discrimination, safety, intellectual property, and truthful communication. Ethical review should occur during problem framing and experimentation, not only immediately before launch.

Entrepreneurial organizations using artificial intelligence should validate data provenance, consent, security, model performance across relevant groups, explainability appropriate to the use, human oversight, and mechanisms for appeal or correction. An AI prototype that performs well on average may still produce unacceptable harm to a minority group. Teams should document intended use, limitations, testing conditions, and responsibility for decisions.

Governance should define who can approve experiments, what risks require specialist review, how incidents are reported, and when an experiment must stop. Compliance is a minimum standard; responsible innovation also asks whether the solution is fair, sustainable, and aligned with the organization’s purpose.

10. Illustrative Case: GreenCrate’s Reusable Delivery System

Background

GreenCrate, a fictional early-stage venture, supplied reusable containers to urban meal-delivery businesses. Its founders believed restaurants could reduce packaging waste while maintaining delivery convenience. The team initially planned to build a sophisticated tracking platform and manufacture a large inventory of containers.

Problem

Interviews revealed enthusiasm for sustainability but uncertainty about three issues: whether customers would return containers, whether restaurants would tolerate the operational work, and whether reverse logistics would cost more than disposable packaging. The original plan therefore contained substantial market and business-model uncertainty.

Analysis

The founders created a cross-functional team including a logistics specialist, a software developer, a restaurant operator, a sustainability analyst, and a customer researcher. They separated assumptions into categories:

• customer willingness to return containers;
• restaurant handling time;
• collection-route feasibility;
• cleaning and safety requirements;
• willingness to pay;
• actual reduction in environmental impact.

Rather than build the full platform, the team used a concierge MVP. For four restaurants in one district, staff manually recorded container distribution and return using simple labels and a shared database. The team measured actual returns, collection time, restaurant workload, customer complaints, cleaning costs, and repeat participation.

Approach and solution

The team used lean startup experiments for the uncertain business model, agile cycles for improving the tracking workflow, and a stage-gate review before expanding beyond the pilot. The gate required evidence of safe cleaning, acceptable restaurant workload, a viable collection route, and repeat customer participation. The founders also consulted local health authorities and documented data-protection practices.

Early results showed that customers returned containers more often when reminders were timed to the next order, but restaurants struggled when collection occurred during peak periods. The team pivoted from restaurant-managed collection to scheduled neighborhood pickup points. It also rejected the idea of collecting precise customer location data when aggregated route information was sufficient.

Outcome

The pilot did not immediately prove a profitable model, but it reduced uncertainty and prevented a large premature investment. GreenCrate gained evidence about operational constraints, redesigned its service, and established clearer criteria for scaling. Some proposed features were stopped because they did not improve return rates or customer value.

Learning points

1. Customer enthusiasm is weaker evidence than observed behavior.
2. A low-cost MVP can test operations, not only software.
3. Different methods can be integrated: lean discovery, agile development, and formal gates.
4. Ethical data minimization can reduce risk and simplify implementation.
5. Stopping features is part of disciplined innovation.

Challenges and Limitations of Innovation Management

Innovation frameworks simplify reality. Stage-gates can exclude unconventional ideas; agile methods can neglect long-term architecture; lean experiments can overemphasize measurable short-term behavior; and ambidextrous structures can create political conflict between exploratory and operating units. Portfolio models depend on uncertain forecasts and may privilege projects that are easy to quantify.

Organizational power also matters. Senior sponsorship can accelerate innovation but can create confirmation bias. Cross-functional teams can improve knowledge integration but may experience conflict and slow decisions. Psychological safety can be claimed rhetorically while promotion systems still punish dissent. Finally, innovation can produce negative externalities that are invisible in conventional financial metrics.

The appropriate response is not to abandon frameworks but to treat them as adaptable management instruments. Leaders should make assumptions explicit, use multiple forms of evidence, review consequences, and revise the process when it is producing defensive behavior rather than useful learning.

Best-Practice Checklist

• Begin with a strategically relevant problem, not only a preferred technology.
• Match process formality to uncertainty, risk, and reversibility.
• Give cross-functional teams clear purpose and decision rights.
• Test the riskiest assumptions early and cheaply where responsible.
• Use stage-appropriate metrics and document decision criteria in advance.
• Protect psychological safety while maintaining high standards.
• Reward learning, responsible collaboration, and implementation—not only launches.
• Maintain a portfolio that balances current performance with future options.
• Plan the transition from experiment to operating ownership.
• Integrate ethical, regulatory, environmental, and data governance from the beginning.

Chapter Summary

Innovation management is the strategic capability of converting opportunities into implemented value under uncertainty. Effective organizations distinguish invention from innovation, classify the type and uncertainty of an opportunity, and design a process that links problem framing, experimentation, development, implementation, and learning.

Stage-gate provides formal investment discipline; agile emphasizes iterative delivery; lean startup emphasizes hypothesis testing and validated learning; and ambidextrous management balances exploration with exploitation. These approaches are complementary when their purposes and limits are understood.

Innovation depends on cross-functional teams, clear decision rights, collaboration, leadership, supportive culture, appropriate incentives, and psychological safety. Portfolios should balance risk, time horizon, strategic fit, and resource constraints rather than relying only on individual project forecasts. Resistance should be diagnosed as a response to perceived losses, capability gaps, or conflicting incentives. Metrics must evolve with the innovation stage, while ethical and governance considerations must be integrated throughout the process.

For entrepreneurial organizations, the central managerial discipline is to learn quickly and responsibly, allocate resources progressively, and create the conditions in which promising ideas can become valuable, scalable, and legitimate innovations.

Key Terms

Innovation: Implementation of a new or improved offering, process, business model, or practice that creates value.

Invention: A new idea, discovery, or technical possibility before demonstrated implementation and value.

Incremental innovation: Improvement to an existing product, service, process, or model.

Radical innovation: Innovation involving a substantial departure from existing technologies, markets, or operating logic.

Architectural innovation: Reconfiguration of existing components into a new system arrangement.

Disruptive innovation: A process in which a simpler or more accessible offering develops from a new or lower-end market and later challenges established offerings.

Technical uncertainty: Uncertainty about whether a solution can be built and operated reliably.

Stage-gate: A process that divides innovation into stages separated by formal investment decisions.

Agile: An iterative approach based on short cycles, working increments, collaboration, and adaptation.

Lean startup: An approach based on hypotheses, MVPs, experimentation, and validated learning.

Minimum viable product: The smallest responsible version of an offering that enables meaningful learning about a critical assumption.

Pivot: A substantive change in strategy based on evidence while retaining useful learning.

Ambidextrous organization: An organization that manages exploration and exploitation simultaneously.

Innovation portfolio: The set of innovation initiatives managed as an interdependent collection.

Psychological safety: A shared belief that people can speak up, ask questions, and report concerns without interpersonal punishment.

Open innovation: Use of internal and external knowledge flows to advance innovation.

Innovation accounting: Use of stage-appropriate measures to track learning, progress, and value creation.

Change resistance: Opposition or hesitation arising from perceived losses, uncertainty, capability gaps, or conflicting interests.

Responsible innovation: Innovation governed with attention to safety, fairness, privacy, sustainability, and wider social consequences.

Review Questions

Short Answer Questions

1. Distinguish invention from innovation.
2. What is the purpose of a minimum viable product?
3. Identify two differences between stage-gate and agile innovation.
4. Define psychological safety and explain why it matters for innovation.
5. What is meant by an ambidextrous organization?

Long Answer Questions

1. Explain how an entrepreneurial organization can design an innovation process from opportunity framing through scaling.
2. Compare stage-gate, agile, and lean startup approaches, including the conditions under which each is most useful.
3. Discuss how leadership, incentives, culture, and psychological safety influence innovation performance.
4. Explain how an organization should construct and govern an innovation portfolio.
5. Analyze the ethical and governance responsibilities associated with AI-enabled innovation.

Analytical / Application Questions

1. A startup has strong customer interest but no evidence of repeat use or willingness to pay. Design two experiments, identify the assumptions they test, and specify decision rules for continuing or pivoting.
2. An established manufacturer has efficient core operations but very few exploratory projects. Diagnose the ambidexterity problem and propose structural, leadership, and portfolio interventions.
3. Employees resist a new digital workflow because they fear job loss and have not been trained. Develop a change-management response that addresses both the emotional and capability dimensions of resistance.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes innovation from invention?

A. Innovation is always technologically radical, whereas invention is incremental.

B. Innovation involves implementation and value creation, whereas invention may remain an unimplemented idea.

C. Innovation occurs only in large firms, whereas invention occurs only in startups.

D. Innovation is a research activity, whereas invention is a marketing activity.

Correct Answer: B. Innovation involves implementation and value creation, whereas invention may remain an unimplemented idea.

Question 2

Which approach is primarily organized around hypotheses, minimum viable products, and validated learning?

A. Stage-gate

B. Lean startup

C. Total quality management

D. Scientific management

Correct Answer: B. Lean startup

Question 3

What is a common strength of a stage-gate process?

A. It eliminates the need for customer research.

B. It guarantees that every project will succeed.

C. It provides formal points for investment and continuation decisions.

D. It requires all requirements to remain unstable.

Correct Answer: C. It provides formal points for investment and continuation decisions.

Question 4

A team changes its target customer after evidence shows that its original segment has little interest, while retaining useful learning from its experiments. This is an example of:

A. A pivot

B. Exploitation

C. Architectural innovation

D. A sunk-cost decision

Correct Answer: A. A pivot

Question 5

Which condition most strongly indicates psychological safety?

A. Employees avoid disagreement to preserve harmony.

B. Employees can report problems and question assumptions without humiliation or retaliation.

C. Managers remove all performance standards.

D. Teams make decisions without accountability.

Correct Answer: B. Employees can report problems and question assumptions without humiliation or retaliation.

Question 6

An ambidextrous organization seeks to balance:

A. Marketing and accounting only

B. Exploration and exploitation

C. Centralization and outsourcing only

D. Invention and patenting only

Correct Answer: B. Exploration and exploitation

Question 7

An experiment costs $20,000 and has a 30% probability of producing a $100,000 benefit and a 70% probability of producing no benefit. Using EMV = ∑(p_i × V_i) − C, what is its EMV?

A. $10,000

B. $30,000

C. $80,000

D. −$10,000

Correct Answer: A. $10,000

Question 8

Which is generally the strongest evidence of customer validation for a new paid service?

A. Customers say the idea sounds interesting.

B. A large number of employees attend an internal presentation.

C. Target customers repeatedly use and pay for the service.

D. The founding team believes the market is large.

Correct Answer: C. Target customers repeatedly use and pay for the service.

Question 9

Why can applying mature-business ROI standards to early discovery projects be harmful?

A. Early projects always have positive cash flow.

B. Early projects may primarily create information rather than immediate financial returns.

C. ROI cannot ever be calculated for established products.

D. ROI measures only employee satisfaction.

Correct Answer: B. Early projects may primarily create information rather than immediate financial returns.

Question 10

Which response best addresses resistance caused by employee capability gaps?

A. Ignore the resistance until employees comply.

B. Use training, participation, and a bounded pilot with clear support.

C. Remove all decision rights from employees.

D. Reward only employees who already possess the new skills.

Correct Answer: B. Use training, participation, and a bounded pilot with clear support.