Review status
This summary is based on the full article text, read from scanned article pages.
The source URL has been verified through the official Harvard Business Review article page. No verified DOI was identified.
The article is a practitioner-oriented conceptual article. It develops a managerial framework for diagnosing organizational capabilities and choosing the right organizational structure for disruptive change. It does not report a formal empirical study, statistical test, regression model, or sample.
Research question
How can established companies respond successfully to disruptive change when their existing organization is built to serve the current business?
More specifically, the article asks how managers can diagnose whether their organization has the right capabilities for a new challenge and how they should structure innovation efforts when existing resources, processes, or values do not fit the opportunity.
Hypotheses
Not specified.
This is a conceptual article rather than an empirical hypothesis-testing study.
Method
The article develops a managerial framework based on the authors’ research on why established firms struggle with disruptive innovation.
The framework argues that managers should diagnose an organization’s capabilities and disabilities by examining three factors:
- resources;
- processes;
- values.
Resources include people, equipment, technologies, product designs, brands, information, cash, relationships with suppliers and customers, and other tangible or intangible assets that can be used to respond to opportunities.
Processes are the patterns of interaction, coordination, communication, and decision-making through which work gets done. Examples include product development, market research, budgeting, employee development, manufacturing, logistics, and planning. Processes are valuable because they allow organizations to perform recurring tasks reliably, but they can become barriers when a new task requires different ways of working.
Values are the criteria employees and managers use to set priorities. They shape which customers, margins, markets, and opportunities are considered attractive. Values are especially important because they determine how resources are allocated.
The article also distinguishes between sustaining and disruptive innovation. Sustaining innovations improve performance along dimensions that mainstream customers already value. Disruptive innovations initially perform worse on mainstream measures but introduce new value propositions, often through lower cost, simplicity, convenience, or access to overlooked customers.
The article uses examples from companies and industries such as Digital Equipment Corporation, Merrill Lynch, Dayton Hudson, Chrysler, Cisco, IBM, and Hewlett-Packard. These examples are illustrative rather than part of a formal case-study research design.
A central visual tool is the “Fitting the Tool to the Task” matrix on page 10. The matrix maps innovation responses according to whether the new task fits the organization’s existing processes and values.
Results / key findings
The article’s core argument is that established companies often fail at disruptive change because the very capabilities that make them successful in one context become disabilities in another.
The first major finding is that capabilities are not located only in people. Managers often assume that if they assign smart, successful employees to a new challenge, the organization will adapt. Christensen and Overdorf argue that this is incomplete. Capabilities are embedded in resources, processes, and values. Talented people may fail if the surrounding processes and values are wrong for the task.
The second major finding is that resources are usually the easiest capability to move. People, money, technology, and brands can often be reassigned. Processes and values are harder to change because they are embedded in routines, decision rules, priorities, and organizational expectations.
The third major finding is that the same process can be both a capability and a disability. A process designed for high-quality, predictable product development may be excellent for sustaining innovation but poor for disruptive innovation. For example, processes that screen projects by mainstream customer needs, high margins, or large near-term markets may reject disruptive opportunities because they initially look small, unattractive, or technically inferior.
The fourth major finding is that values strongly shape resource allocation. Mature firms often develop values that favor large markets, high margins, and existing customers. These values can make disruptive opportunities appear unattractive. A project that needs only $5 million in revenue may excite a small firm but appear irrelevant to a large corporation that needs billion-dollar opportunities to move the needle.
The fifth major finding is that sustaining and disruptive innovations require different organizational responses. Established firms are usually good at sustaining innovations because these projects fit existing customers, profit formulas, sales channels, and operating processes. Disruptive innovations are harder because they often require new customers, lower margins, different cost structures, and different business models.
The article’s examples show this distinction. Digital Equipment Corporation had the resources to succeed in personal computers, but its processes and values were built around minicomputers. The article argues that Digital’s mainstream organization was not well suited to the personal computer business because the new market had different margins, sales channels, cost structures, and customer priorities.
The article also uses Merrill Lynch and Charles Schwab to illustrate disruptive innovation in brokerage. Schwab’s discount brokerage model initially looked unattractive to full-service firms because it offered simpler, lower-margin services to customers who did not need the full-service model. But as the model improved, it became a serious competitive threat.
The article argues that managers should not ask only whether the organization has enough resources. They should ask whether the new task fits the organization’s processes and values. This distinction is the foundation of the article’s main framework.
The “Fitting the Tool to the Task” matrix on page 10 gives the practical logic.
If the new task fits the organization’s existing processes and values, it can be managed inside the existing functional organization. This is the appropriate response for many sustaining innovations.
If the task fits the organization’s values but does not fit existing processes, managers should use a heavyweight team inside the existing organization. A heavyweight team gives members enough authority and cross-functional responsibility to create new ways of working while still operating within the parent organization’s values.
If the task fits existing processes but not existing values, development may occur in-house through a heavyweight team, but commercialization often requires a spinout. This is because the parent organization may be technically capable but unwilling to prioritize a low-margin, small-market, or unfamiliar opportunity.
If the task fits neither existing processes nor existing values, a separate spinout is usually needed. The new unit needs its own processes, priorities, cost structure, and business model.
The article also argues that acquisitions can help firms acquire capabilities, but only if managers understand what they are buying. If the acquired company’s value lies mainly in resources, integration into the parent can make sense. If the value lies in the acquired company’s processes and values, integration can destroy the very capability the buyer needed.
The Cisco example is used positively. Cisco acquired small companies and often preserved the resources it needed while integrating them into its broader organization. The IBM-Rolm example is used as a warning. IBM bought Rolm for its telecom capabilities, but integration into IBM’s processes and values damaged the capabilities that made Rolm valuable.
The article’s overall finding is that managers need organizational fit, not just managerial effort. Disruptive change requires matching the task to the right organizational form.
Practical implications
For managers, the article provides a clear diagnostic tool: before launching an innovation project, examine whether the project fits the organization’s resources, processes, and values.
The first practical lesson is that successful employees are not enough. Strong people can fail when they are placed inside an organization whose processes and values reject the new task. Managers should therefore design the organizational setting around the innovation challenge rather than assuming talent alone can overcome structural misfit.
The second practical lesson is that established firms should separate sustaining and disruptive innovation. Sustaining innovation often belongs in the mainstream organization because it serves existing customers and fits existing priorities. Disruptive innovation often needs protection because it may start with smaller markets, lower margins, less demanding customers, or a different business model.
The third practical lesson is that managers should be careful with resource allocation systems. Processes that ask for large market size, high near-term margins, and evidence from mainstream customers may systematically reject disruptive opportunities. If a company wants disruptive innovation, it needs a place where small, uncertain, low-margin opportunities can be taken seriously.
The fourth practical lesson is that heavyweight teams are useful when the organization’s values fit but its processes do not. A lightweight team may coordinate across functions, but it usually does not have enough authority to build new processes. A heavyweight team gives people the responsibility and decision rights needed to create a new way of working.
The fifth practical lesson is that spinouts are not just fashionable startup theater. They are necessary when the parent organization’s values make it impossible to prioritize the new opportunity. If the mainstream business cannot value the market, margin, or business model, the disruptive initiative needs a separate home.
The sixth practical lesson is that acquisitions require discipline. Managers should ask whether they are acquiring resources or processes and values. If the acquired firm’s true value lies in its processes and values, heavy integration into the parent can destroy the acquisition’s purpose.
For practitioners, useful diagnostic questions include:
- Does the new opportunity fit the organization’s existing customers, margins, and cost structure?
- Are existing processes designed for this task, or for a different kind of work?
- Would the resource allocation process naturally fund this opportunity?
- Does the opportunity look too small or too low-margin to the mainstream business?
- Does the project need a lightweight team, heavyweight team, spinout, or acquisition?
- If acquiring a company, is the goal to obtain resources or to preserve distinct processes and values?
- Are managers asking people to succeed inside a structure that makes success unlikely?
Theoretical implications
The article contributes to innovation management by explaining why established firms can be capable and incapable at the same time.
Its resources-processes-values logic shows that organizational capabilities are context-specific. A firm may have strong resources and talented people but still be unable to respond to disruptive change because its processes and values are built for a different task.
The article also contributes to organizational inertia theory. Inertia is not presented simply as laziness or resistance. It is embedded in routines, priorities, business models, customer relationships, and resource allocation processes that once made the company successful.
The article also strengthens the distinction between sustaining and disruptive innovation. Sustaining innovation fits existing performance measures and mainstream customers. Disruptive innovation introduces a different value proposition and often requires different organizational arrangements.
For strategy implementation, the article shows that choosing a strategy is not enough. The organization must have processes and values that allow the strategy to be executed. If not, managers need to create a separate structure or acquire capabilities without destroying them.
The article also contributes to corporate entrepreneurship by clarifying when internal ventures can remain inside the parent and when they need separation. The decision depends not on whether managers like entrepreneurship, but on whether the new opportunity fits existing processes and values.
Limitations
The article is practitioner-oriented and conceptual. It does not report a formal empirical test, sample, statistical analysis, or systematic case-selection design.
The examples are illustrative. They help explain the framework but should not be treated as a comprehensive empirical dataset.
The article focuses strongly on processes and values. It pays less attention to other factors that may influence disruptive change, such as leadership politics, capital market pressure, ecosystem dependencies, regulation, employee identity, or cultural conflict.
The article was published in 2000, so several examples reflect the technology, internet, and corporate strategy context of that period. The framework remains influential, but modern platform markets, artificial intelligence, software ecosystems, and digital business models may require updated applications.
The article gives strong guidance on when to use spinouts, heavyweight teams, and acquisitions, but it does not provide detailed implementation steps for managing conflicts between the parent organization and the new unit.
The article assumes managers can diagnose process and value fit with reasonable accuracy. In practice, this diagnosis may be difficult because values are often implicit and processes may be hard to see until they fail.
Future research
Future research could test whether firms that match organizational structure to process and value fit perform better in disruptive innovation contexts.
Researchers could examine when heavyweight teams are sufficient and when spinouts become necessary.
Future studies could investigate how organizations can identify hidden values that bias resource allocation against disruptive opportunities.
Another useful direction would be to study how spinouts can later reconnect with the parent organization without losing the processes and values that made them successful.
Researchers could also examine acquisitions through the resources-processes-values framework and test when integration creates value versus destroys acquired capabilities.
Future research could apply the framework to contemporary disruptions such as artificial intelligence, electric vehicles, platform ecosystems, digital health, renewable energy, and software-defined manufacturing.
Finally, future studies could examine how middle managers translate or block disruptive opportunities when the parent organization’s values conflict with the new business model.