Company
Kodak
Kodak
The architecture generated $10 billion a year in film revenue. Pivoting meant dismantling it.
Company
Kodak
Failure layer
Architecture
Questions
2
$10B
Film revenue at peak
1975
Invented digital camera
2012
Bankruptcy filed
145,000
Employees at peak
Timeline
1975
Steve Sasson, a Kodak engineer, builds the first digital camera. Management shelves the project to protect film revenue.
1981
Internal Kodak research report concludes digital photography will replace film within 20 years. Leadership acknowledges the finding.
1996
Kodak launches early digital cameras but prices them high to avoid cannibalizing film sales. Revenue peaks near $16 billion.
2004
Digital camera sales overtake film cameras globally. Kodak's film revenue enters terminal decline.
2007
Kodak restructures, cutting 50,000 jobs. Still unable to build a profitable digital business on top of film-era infrastructure.
2012
Kodak files for Chapter 11 bankruptcy. Sells its patent portfolio for $525 million — a fraction of the IP's original value.
What happened
In 1975, Steve Sasson — a young engineer at Kodak — built the first digital camera. It was the size of a toaster, captured a 0.01 megapixel black-and-white image, and took 23 seconds to write to a cassette tape. When Sasson presented it to management, the reaction was immediate: this is fascinating, and we cannot let it see the light of day. Not because leadership was ignorant. Because they understood exactly what it meant. Digital photography would destroy the film business. And the film business was Kodak.
Kodak's entire architecture — factories, supply chains, distribution networks, chemical processing labs, retail partnerships — was built to produce and sell physical film. Margins on film and paper were extraordinary, often exceeding 60%. The razor-and-blade model was a cash machine: sell cameras cheap, profit on consumables forever. Every division, every bonus structure, every capital allocation decision optimized for this architecture. Pivoting to digital did not mean adding a product line. It meant dismantling the most profitable machine in the imaging industry.
Kodak did not fail because it missed the future. It failed because the architecture that generated $10 billion a year in film revenue could not be retooled without destroying itself first.
Leadership tried to thread the needle. They launched digital cameras in the mid-1990s but priced them high to avoid cannibalizing film sales. They invested in digital printing and online photo services. But every initiative was constrained by the same architecture: the infrastructure, talent, and incentives were all designed for a chemical business. By 2004, digital cameras had overtaken film globally. Kodak's decline was not gradual — it was structural. The architecture held the business hostage until the market moved without it. Bankruptcy came in 2012. A company with 145,000 employees and a century of dominance, dissolved because it could not dismantle its own profit engine.
Kodak is the definitive architecture trap. The business layer got it right — leadership saw digital coming decades before it arrived. The organization had talented engineers who could build in the new paradigm. But the architecture — the physical infrastructure, the supply chains, the revenue model — was load-bearing. You cannot renovate the foundation while the building is occupied.
This pattern recurs wherever architecture generates its own gravitational pull. The more profitable the existing system, the harder it is to replace. The architecture does not resist change through malice. It resists through economics. Every quarter, the film business generated cash that funded operations. Every digital initiative required destroying that cash flow first. No rational actor dismantles a $10 billion revenue stream on a bet. So the architecture wins by default, quarter after quarter, until the market makes the decision for you.
Failure pattern
What actually drifted
Invented the future. Could not dismantle the present. Architecture was a profit engine that only ran on yesterday's fuel.
Key takeaway
“The company writes memos about transformation while the architecture quietly enforces the status quo. ”
Related patterns
Architecture
Nokia
They saw the smartphone coming years before Apple. The architecture created civil war.
Architecture
BlackBerry
Every architectural decision optimized for IT departments, not end users.
For a cross-layer comparison, see Disney (Eisner Era) (Organization).
Diagnostic questions
Use these prompts to test whether the same failure mode is showing up in your own system review.
Question 01
Is your most profitable product the one you are trying to move away from? If yes, your architecture is funding its own resistance to change.
Question 02
How many initiatives died because "our platform does not support that"? Count them. That number is your architecture debt.
The diagnostic uses the same four-layer model. It is the fastest way to see whether the problem you are living with starts in the same place.