The Organizational-Change Frameworks

The problem these frameworks were built to explain

There is a pattern in business old enough to predate the computer: leading companies repeatedly lose position when the technology or the market underneath them changes.¹⁶ The intuitive explanation — that the incumbents were complacent, slow, or badly led — turns out to fit the cases poorly. The more durable explanation, developed across organizational theory from the 1960s onward, is that the organization is a system, and that systems built to do one thing well are structurally hostile to doing a different thing at the same time. The frameworks in this paper are the load-bearing statements of that idea.

They matter now because generative AI has reproduced the pattern at speed. By 2025, up to 88% of surveyed organizations reported using AI, and 70% reported generative AI in at least one business function.⁶ Yet a widely-cited MIT study of enterprise deployments found roughly 95% of organizations getting no measurable return, with only about 5% of integrated pilots extracting real value.⁵ The technology is adopted; the value is not captured. That gap is exactly the territory these frameworks map — and the reason this corpus treats organizational change, not model capability, as the binding constraint.

Leavitt’s Diamond: change one variable and the system compensates

The foundational statement belongs to Harold Leavitt, whose 1965 chapter “Applied Organizational Change in Industry” appeared in March’s Handbook of Organizations.¹ Leavitt modeled the organization as an interdependent socio-technical system of four interacting variable classes — task, structure, people (the human actors), and technology. His central claim is the one the whole corpus rests on: a change in any single variable produces compensatory or retaliatory change in the others, so the system tends to re-equilibrate around its prior state.¹ Effective change therefore requires acting on several variables at once; a technology-only intervention is structurally absorbed by the unchanged task, structure, and people around it.

March 1991: exploitation wins the short run and can destroy the long run

If Leavitt explains why a technology-only change gets absorbed, James March explains why the absorption is rational at every step. His 1991 Organization Science paper, “Exploration and Exploitation in Organizational Learning,” is the canonical statement.³ March defines exploration as “search, variation, risk taking, experimentation, play, flexibility, discovery, innovation,” and exploitation as “refinement, choice, production, efficiency, selection, implementation, execution.”³ Both are essential, both compete for the same scarce resources, and the organization must continuously choose between them.

The asymmetry is the heart of it. Returns from exploitation are “positive, proximate, and predictable”; returns from exploration are “uncertain, distant, and often negative.”³ Because feedback ties exploitation to its consequences more quickly and precisely, organizations improve at what they already do faster than they improve at anything new — and those advantages compound. Each gain in competence at an activity raises the reward for repeating it, which raises competence again.³ March’s stark conclusion is that “it is quite possible for competence in an inferior activity to become great enough to exclude superior activities with which an organization has little experience” — the mechanism later writers call the competency trap.³ A firm exploiting to the exclusion of exploration becomes “trapped in suboptimal stable equilibria.”³

This is the precise reason a capable organization underinvests in a genuinely new technology: not because management is foolish, but because the local feedback loops reward the safe, near-term refinement of the existing business over the uncertain, distant payoff of the new one. March’s models add a second-order point that bears directly on AI deployment: in the mutual learning between an organization and its members, fast convergence is dangerous. If individuals adapt to the organizational “code” before the code can learn from them, variety collapses and the organization’s long-run knowledge degrades. Slow socialization and moderate turnover, counterintuitively, preserve the exploratory variety that keeps the system intelligent.³

Ambidexterity: running exploitation and exploration as separate, aligned systems

If exploitation reliably crowds out exploration, the design question becomes: how can one organization do both? Tushman and O’Reilly’s answer is organizational ambidexterity — “the ability to simultaneously pursue both incremental and discontinuous innovation… from hosting multiple contradictory structures, processes, and cultures within the same firm.”⁸ They frame March’s trade-off as the adaptive challenge it implies: a firm must “engage in sufficient exploitation to ensure its current viability and, at the same time, devote enough energy to exploration to ensure its future viability,” against a standing “bias in favor of exploitation with its greater certainty of short-term success.”⁸

Their structural prescription is specific. Because exploitation and exploration require opposite alignments — efficiency, control and incremental improvement on one side; flexibility, autonomy and experimentation on the other — the firm should establish “autonomous explore and exploit subunits that were structurally separated, each with its own alignment of people, structure, processes and cultures,” joined by “targeted integration” at the senior level.⁸ The exploratory unit is protected from the parent’s resource-allocation and management logic precisely so that the competency trap cannot reach it. Their 2013 review is careful to add that this is “at heart, a leadership issue more than a structural one” — the structural separation is necessary but not sufficient.⁸

The evidence base is substantial. The 2013 review reports that ambidexterity is positively associated with sales growth, innovation, market valuation (Tobin’s Q), and firm survival across studies at the firm, business-unit, project, and individual levels.⁸ Among the saved quantitative anchors: a study of more than 500 firms over four years found ambidexterity had a positive effect on firm growth; a 500-company, ten-year study found firms with greater technological capabilities benefited more; and a study of 605 technology companies found an inverted-U relationship between ambidexterity and performance.⁸ Most telling for the AI moment: across a separate large sample, an estimated 80% of firms under-emphasized exploration and over-emphasized exploitation — the competency trap, measured in the field.⁸

Christensen disruption: good management as the cause of failure

Christensen’s disruption thesis is the same mechanism viewed through resource allocation. “Disruptive Technologies: Catching the Wave” (Bower & Christensen, HBR 1995) opens on the now-familiar observation that “one of the most consistent patterns in business is the failure of leading companies to stay at the top of their industries when technologies or markets change.”¹⁶ The Innovator’s Dilemma (1997) sharpens the paradox: “even the most outstanding companies can do everything right — yet still lose market leadership.”¹⁷

The cause is not error but discipline. Resources flow to the sustaining innovations demanded by existing high-value customers, which systematically starves disruptive bets that initially serve small, low-margin, or non-existent markets.¹⁶ Christensen’s Resources–Processes–Values framework makes the point structural: the very resources, processes, and values that make a firm excellent at its current business actively disqualify it from pursuing a disruptive one.¹⁷ The integrated steel mills that earned only 7% margins on rebar were behaving rationally when they ceded that segment to minimills — and that rationality is exactly what let the disruptor climb upmarket.¹⁷ The remedy Christensen and Bower observed was the same one Tushman and O’Reilly reached independently: pursue the disruptive business through an autonomous unit freed from the mainstream organization’s resource-allocation logic.¹⁶¹⁷ Three frameworks, three vocabularies, one prescription.

Raffaelli: incumbents can re-engage a legacy technology — through cognition, not inevitability

Ryan Raffaelli’s work is often loosely cited as another “incumbents are doomed” argument. It is the opposite, and the corpus is deliberate about the attribution.¹³ Raffaelli studies technology re-emergence: how a field given up for dead can recover. His primary case is Swiss mechanical watchmaking. After Japanese quartz watches arrived in the 1970s, the Swiss share of global watch export value fell from 55% to roughly 30% within a decade, and export volume collapsed from 45% to 10% of watches produced globally; by one industry account, employment fell from about 90,000 to 33,000, and roughly two-thirds of Swiss watch companies were lost.¹¹ The quartz watch was cheaper to make — Swatch’s production costs ran about 80% lower, using roughly 55% fewer components.¹¹ On a pure disruption reading, mechanical watchmaking should have died.

It did the reverse. By 2008 Switzerland was again the world’s leading watch exporter, having reclaimed 55% of total export value.¹¹ Raffaelli’s explanation is not that the incumbents out-engineered quartz. They stopped competing on the dimension quartz had won — precision — and redefined the value and identity of the mechanical watch as craftsmanship, heritage, and emotional meaning.¹³ In his words, “successful companies may be able to reposition a ‘dying’ technology by redefining its identity and value for the customer.”¹³ The mechanism is sociocognitive: re-emergence required institutional guardians (collectors and loyal employees who preserved the legacy technology and its meaning) in productive tension with institutional entrepreneurs (leaders who pursued new markets).¹¹ Raffaelli calls the firm-level version identity ambidexterity — preserving legacy capabilities while adapting to new markets — and notes that “a lot of companies fail because they cannot do both things simultaneously.”¹³

His companion paper, “Frame Flexibility,” locates incumbent resistance one level deeper still — not in the technology, the structure, or the economics, but in cognition. It asks why incumbent firms reject non-incremental innovations and answers with the top management team’s frame flexibility: the capability “to perceptually expand an innovation’s categorical boundaries and to cast the innovation as emotionally-resonant with the organization’s identity, competencies, and competitive boundaries.”⁹ Forces of inertia generally constrict how leaders perceive an innovation; frame flexibility relaxes the usual assumption that cognitive frames are static and shows how reframing increases the likelihood of adoption.⁹

The synthesis applied to AI: adoption is not the constraint; rewiring is

Read together, the frameworks make a single prediction about any general-purpose technology: the organization will adopt the tool quickly and capture its value slowly, because the surrounding task, structure, people, and incentives re-equilibrate around the existing business (Leavitt), because exploitation’s fast feedback starves the exploratory reconfiguration the tool requires (March), and because the fix is not more technology but a differently-aligned organization (Tushman–O’Reilly, Christensen).¹³⁸¹⁷

The generative-AI evidence tracks the prediction. The MIT GenAI Divide study attributes the failure not to model quality but to integration and learning: generic tools “don’t learn from or adapt to workflows,” and the firms that succeed “pick one pain point, execute well, and partner smartly.”⁵¹⁵ In its sample, purchasing specialized vendor solutions succeeded about 67% of the time versus roughly one-third for internal builds, and mid-market top performers moved from pilot to full implementation in about 90 days while enterprises took nine months or longer.⁵ The Stanford AI Index supplies the independent macro picture: 88% organizational adoption, 70% generative-AI-in-one-function, and a population-level adoption curve faster than the PC or the internet — alongside the recognition gap that inaccuracy rose to the top-cited AI risk, named by 74% of respondents.⁶⁷

There is a final theoretical reason to expect the value lag and not to panic at it. Brynjolfsson, Rock, and Syverson’s “Productivity J-Curve” shows that general-purpose technologies like AI require large intangible complementary investments — new processes, skills, and business models — that are poorly captured in standard accounts.¹⁰¹² Because those investments are made before their benefits are harvested, measured productivity is underestimated early in a GPT’s diffusion and only later overestimated as the intangibles pay off — a J-shaped curve.¹² Their intangibles-adjusted total factor productivity ran 11.3% above official measures at the end of 2004 and 15.9% above by the end of 2017, quantifying the hidden complementary capital from the prior computing wave.¹⁰ The organizational rewiring the change frameworks demand is, in macroeconomic terms, exactly the intangible investment the J-curve says must precede the payoff.

What the frameworks tell a strategist to do

The operational reading is consistent across all four frameworks and the AI evidence. First, expect a technology-only intervention to be absorbed; budgeting for the tool without budgeting for the change to task, structure, and people is a Leavitt-category error.¹ Second, do not run the exploratory work on the exploitation business’s metrics and cadence — fast, certain near-term feedback will starve it, by design (March).³ Third, the durable structural answer is a separately-aligned exploratory unit with senior-level integration, treated first as a leadership problem (Tushman–O’Reilly, Christensen).⁸¹⁷ Fourth, incumbency is not destiny: re-engagement is possible where leaders can reframe what the technology is for and hold legacy and new identities at once (Raffaelli).¹¹⁹ And fifth, the value lag is expected, not anomalous — the intangible reorganization is the investment that precedes the return (the J-curve).¹⁰¹² The 95%-zero-return finding, read through these frameworks, is not evidence that AI does not work. It is evidence that most organizations have bought the technology and skipped the reorganization.⁵

References