Key Principle
A value network is the context within which a firm identifies customers, solves problems, procures inputs, reacts to competitors, and strives for profit. It is defined by two properties: a unique rank-ordering of product performance attributes, and a characteristic cost structure. Mainframe networks valued capacity and speed; portable computing networks valued ruggedness, low power, and small size. The same disk drive is evaluated against entirely different criteria in different networks.
This is not a restatement of "firms serve their customers." It is a structural argument: a firm's position in a nested system of producers, customers, and competitive dynamics determines which innovations appear rational and which appear irrational. A firm built for 50-60% gross margins cannot profitably serve a market requiring 15-20% margins. This is economic reality, not organizational failure.
The value network concept explains why disruptive technologies appear worthless to established firms -- they are being evaluated against the wrong metrics within the wrong network. The technology is not inferior; the measurement system is mismatched.
Why This Matters
Without the value network framework, firms diagnose disruption as a technology problem ("they couldn't build it") or a management problem ("they didn't see it"). The value network reveals it as a structural problem: even motivated managers cannot simply choose to pursue disruption because their cost structure makes it unprofitable and their customers define what counts as progress.
The framework also corrects a dangerous misapplication of S-curve thinking. Conventional S-curve analysis asks whether the established technology is decelerating. Value network thinking asks whether the disruptive technology is improving along a trajectory that will intersect what the established market needs. These are different questions with different answers.
Good Examples
The six-step decision pattern formalizes how value networks cause failure:
- Engineers at incumbents build working disruptive prototypes before entrants do (Seagate had ~80 3.5-inch prototypes).
- Marketing shows them to existing customers, who reject them; forecasts are pessimistic; margins are lower.
- Resources flow to sustaining work -- known customers, known margins, known markets.
- Frustrated engineers leave and found startups. They sell to whoever will buy; dominant applications emerge through experimentation, not planning.
- Entrants ride the steeper trajectory upmarket, improving at ~50%/year against demand growing at ~25%/year.
- Incumbents respond too late. The disruptive architecture is performance-competitive and the entrant has a cost structure advantage. (Chapter 2)
Flash memory as predictive test: The S-curve framework predicted flash was no threat because magnetic recording had not inflected -- density was improving at an increasing rate. The value network framework predicted disk drive firms could build competitive flash products but would not lead, because flash creates value in different networks (palmtop computers, cameras, cash registers). Seagate and Quantum both built flash products, both withdrew with less than 1% market share by 1995. Only the value network framework correctly predicted both the capability and the strategic outcome. (Chapter 2)
Hedonic regression data: Mainframe customers paid $1.65/MB; portable computing paid $1.17/MB. But portable customers paid a premium for size reduction while mainframe customers paid zero for it. The same attribute -- physical smallness -- had different economic value in different networks. (Chapter 2)
Counterpoints
Day-to-day allocation defeats executive intent: Even when managers approved disruptive projects, daily resource allocation micro-decisions starved them. "Sustaining projects addressing the needs of the firms' most powerful customers almost always preempted resources from disruptive technologies with small markets and poorly defined customer needs." Engineers were pulled off to solve problems for "more important" customers. The process was both conscious and unconscious. (Chapter 2)
The pattern is self-reinforcing: At each step of the six-step sequence, the rational decision from within the firm's value network leads deeper into the trap. The incentive structure, cost structure, and customer structure all point the same direction -- away from the disruption. (Chapter 2)
Gross margins lock across layers: 14-inch drive makers (~60% margins) served mainframe makers (~56% margins); desktop drive makers (~25% margins) served PC makers (~25% margins). Cost structures match across the value network, making cross-network moves structurally unprofitable. (Chapter 2)
Key Quotes
"Sustaining projects addressing the needs of the firms' most powerful customers almost always preempted resources from disruptive technologies with small markets and poorly defined customer needs." — Clayton M. Christensen, Chapter 2
"The most formidable barrier the established firms faced is that they did not want to do this." — Clayton M. Christensen, Chapter 2, quoting Richard Tedlow
"If I had been suckered into telling Andy Grove what he should think about the microprocessor business, I'd have been killed. But instead of telling him what to think, I taught him how to think — and then he reached what I felt was the correct decision on his own." — Clayton M. Christensen, Foreword
Rules of Thumb
- When evaluating a new technology, ask which value network it serves -- not whether it is "good enough" by your current customers' metrics
- If your gross margins are structurally higher than the disruptive market requires, you cannot profitably compete there without a separate cost structure
- Do not trust S-curve analysis alone; ask whether the disruptive trajectory is intersecting your market's demand, not whether your own technology is decelerating
- The six-step pattern is the default organizational outcome; avoiding it requires deliberate structural intervention, not just awareness
- Watch for engineers building prototypes that marketing kills -- this is step 2 of the failure sequence in action
Related References
- The Innovator's Dilemma: Core Thesis - The overarching thesis that value networks structurally explain
- Asymmetric Mobility and the Northeast Pull - How value network cost structures drive upmarket drift
- Resources, Processes, and Values (RPV) Framework - How processes and values encode value network assumptions into the organization