Clayton Christensen

In the [YOU] on AI Field Guide

The cycle that began with [YOU] on AI opens with a moment Christensen would have recognized immediately: a principal engineer at Google sat down with Claude Code in December 2025, described in three paragraphs of plain English a problem her team had spent a year solving, and received a working prototype in an hour. The moment is not, in Christensen's framework, a productivity story. It is a disruption story. The technology did not make existing developers faster at doing existing work. It made the translation between human intention and working software available to people who had never translated before—the non-consumers who had ideas and lacked the skills to realize them, the largest market in the world by the logic of his analysis.

Christensen's theory of asymmetric motivation explains why the incumbents of the SaaS industry—Salesforce, Adobe, Workday—are responding to AI by integrating AI features into their existing products rather than making their existing products unnecessary. This is not a failure of intelligence or vision. It is the structurally correct response within the value network they inhabit: their best customers do not need custom-built tools, their cost structures cannot support the low-margin opportunities that disruption creates, and their resource allocation processes correctly direct investment toward the customers who pay the most. The response that would protect them—dismantling the architecture that produced their success—is not a response their organizations can execute. This is overserving meeting its reckoning.

The jobs-to-be-done lens reframes the entire pattern of AI adoption. The job is not "write code." If it were, AI would be a sustaining innovation for the existing developer tools market—making the existing fifty million developers more productive. The job is to close the gap between what a person can imagine and what they can build: the imagination-to-artifact ratio. This job has been waiting, unfilled, for the entire history of computing. Every previous tool partially filled it but left a translation gap. The language interface closed that gap so completely that adoption occurred at the speed of recognition—the adoption speed Christensen predicts when a product perfectly fills a job that a large population has been struggling to do for a long time.

Christensen would have pressed hardest on what the cycle calls the dams: the institutional structures that redirect disruptive capability toward broadly distributed benefit rather than narrowly captured gain. His historical evidence, accumulated across every industry he studied, is that the dams are almost never built in time. The incumbents are too committed to the existing structure. The regulatory institutions are too slow. The educational institutions are too calcified. And the individuals caught in the transition—the senior architect who feels like a master calligrapher watching the printing press arrive, the engineer who oscillates between excitement and terror, the parent who does not know what to tell her child—are left to navigate a structural shift with inadequate guidance. He was not a pessimist about this. He insisted that it is not inevitable. But the historical pattern is consistent, and understanding it is the precondition for breaking it.

Origin

Christensen was born in 1952 in Salt Lake City, studied at Brigham Young University, Oxford, and Harvard Business School, and returned to Harvard as a faculty member after a decade in business and consulting. His doctoral research focused on the disk drive industry, chosen precisely because its technological changes were fast enough and its historical records complete enough to test structural theories against empirical data with unusual rigor. What he found in the disk drive industry was a pattern so consistent across eight generations of disk drive transitions that it could not be explained by individual company failures: the best-managed companies, the ones most responsive to their best customers, were destroyed first. He subsequently found the same pattern in steel minimills, mechanical excavators, retail, and healthcare. The consistency across such diverse contexts was the signal that the mechanism was structural rather than contingent.

The Innovator's Dilemma, published in 1997, introduced disruptive innovation to a business audience. The Innovator's Solution, with Michael Raynor in 2003, extended the framework from diagnosis to prescription. The jobs-to-be-done insight, refined in collaboration with Bob Moesta and developed most completely in Competing Against Luck (2016), provided the complementary customer-level theory. His late-career work on education and healthcare in The Innovator's Prescription and Disrupting Class applied the framework to sectors with the greatest potential for social impact. He died of leukemia in January 2020, eight months before the public release of GPT-3 began demonstrating the technology that would provide the most comprehensive single instantiation of every structural dynamic he had spent his career documenting.

Key Ideas

Disruptive Innovation. Innovations enter markets from below, with products inferior to incumbents along the dimensions incumbents' best customers value most. Incumbents rationally ignore them because they do not serve their most profitable customers at adequate margins. The innovation improves. It reaches adequacy for a larger market. By the time incumbents recognize the threat, the basis of competition has shifted and the capabilities that sustained their dominance are no longer what the market values. This is not a management failure. It is a structural trap. Disruptive innovation is the mechanism, and the AI transition to the SaaS industry is its most comprehensive single instance.

Jobs to Be Done. People hire products to make progress in specific circumstances, and the competitors for any job are not necessarily the products in the same category. The job that AI fills is not "write code"; it is "close the gap between imagination and artifact." Understanding this job explains why non-developers are the most intense adopters, why the productivity story misses the transformation story, and why every professional role that bundles translation with judgment is being unbundled—with translation automating and judgment elevating. Jobs to be done is the lens that shows where the value migrates when the tool changes.

The Value Network. The ecosystem that surrounds any organization defines what performance means, which cost structures are viable, and which capabilities command a premium. When disruption occurs, the value network shifts, and the capabilities that sustained dominance in the old network become the constraints that prevent adaptation. The pre-AI software value network rewarded execution. The post-AI value network rewards judgment. Organizations that continue investing in execution-centered capabilities while the value network shifts to judgment-centered capabilities will find their position increasingly precarious.

New-Market Disruption and Non-Consumption. The form of disruption most consequential in the AI moment is new-market disruption—the creation of a market that did not previously exist by serving people who were excluded entirely. Non-consumption is the largest market in the world: the billions of people who have ideas and cannot build software, who have needs that fall below the threshold of commercial software viability, who were excluded from the production economy by the cost of the translation skill. The language interface serves this market, and the aggregate size of the need it serves dwarfs every existing software market.

The Disruption of Disruption. Christensen's late-career work addressed what happens when the disruptor becomes the incumbent. The integrated architecture that produced the frontier AI companies' dominance will eventually modularize as the technology matures and the median user's needs are served by smaller, more accessible systems. The AI companies that ride the current disruption to dominance will face the same structural dynamics they are now imposing on SaaS: the value network will shift, the cost structure will be challenged, and the correct response for the new incumbent will be structurally impossible for the organizations that built their empires on the old architecture.