Planned Versus Unplanned Obsolescence

Obsolescence is the state of being outdated. The word describes products, standards, languages, and institutions that lose their usefulness over time. The common assumption is that obsolescence is always a failure — a product that breaks too soon, a format that becomes unreadable, a standard that falls out of use. But obsolescence is not always a failure. Sometimes it is the point. Some systems are designed to stop working. Others stop working because no one maintained them. The difference matters more than the label.

This article examines the distinction between planned obsolescence — when a product is designed to become obsolete — and unplanned obsolescence — when a product becomes obsolete through neglect, changing standards, or shifting usage. It traces how the concept moved from industrial design into technology, law, and culture, and considers what the difference reveals about how we evaluate systems.

What planned obsolescence actually means

The term planned obsolescence was coined in 1954 by Brooks Stevens, an industrial designer who described it as “a strategy of planning and scheduling the obsolescence of products so that they become obsolete at a predetermined rate.” The strategy was not new. General Motors had been introducing annual model changes since the 1920s, under the leadership of Alfred P. Sloan, to encourage consumers to replace cars that were still functional but no longer fashionable. The concept had a name in 1954. The practice was decades old.

Planned obsolescence takes several forms. Functional obsolescence occurs when a product is designed to stop working after a certain period or usage threshold. Stylistic obsolescence occurs when a product is designed to fall out of favor through intentional aesthetic changes. Systemic obsolescence occurs when a product depends on an ecosystem — software updates, replacement parts, compatible accessories — that is discontinued. Each form achieves the same result: the product becomes unusable or undesirable. The mechanism differs.

The most famous example of functional obsolescence involves light bulbs. The Phoebus cartel, a consortium of light bulb manufacturers including Philips, Osram, and General Electric, met in 1924 and agreed to standardize bulb lifespans. Before the cartel, bulbs commonly lasted 2,500 to 3,000 hours. After the agreement, manufacturers reduced the lifespan to 1,000 hours. The limit was enforced through quality inspections. Bulbs that lasted longer than the standard were destroyed. The arrangement was revealed decades later and criticized as an explicit agreement to limit product durability.

The most famous example of stylistic obsolescence is the annual car cycle. GM’s practice of introducing new models each year — with updated styling, new colors, and minor feature changes — was designed to make the previous year’s model feel dated even though the underlying mechanical reliability had not changed. The strategy shifted consumer expectations. A car that was still mechanically sound was no longer socially acceptable because it did not match the current model year.

When obsolescence is unplanned

Unplanned obsolescence occurs when a product becomes outdated through forces external to its design. A software tool becomes obsolete when the operating system it depends on is discontinued. A file format becomes unreadable when the application that created it is no longer supported. A language becomes obsolete when its speakers die out and no new learners adopt it.

Unplanned obsolescence is not a single mechanism. It has several distinct causes.

Neglect occurs when no one maintains a product but no one actively disables it. A library of software that was free and unowned eventually becomes incompatible with new systems. Buyers encounter errors, find workarounds, and abandon the tool. The tool did not break. It aged.

Changing standards cause obsolescence when a product that once worked within a standard no longer matches the updated specification. A plug that fits a socket in one generation may not fit in the next. A data format that was valid under one version of a schema may be invalid under the next. The product was not designed to fail. The environment changed.

Compatibility cascades occur when one component’s obsolescence triggers the obsolescence of dependent components. A printer driver that works on Windows 7 may not work on Windows 11. An app that depends on a library that is no longer maintained may fail to install. The obsolescence spreads through the dependency chain. This is the same pattern that digital preservation researchers describe as format obsolescence: the data is intact, but the chain of tools required to read it has been broken.

The difference between the two

The critical distinction is intent. Planned obsolescence is a deliberate design choice. The manufacturer decides that the product will stop working and encodes that decision into the product’s architecture. Unplanned obsolescence is the result of inaction, changing conditions, or the passage of time. The manufacturer did not design the product to become obsolete. The product became obsolete because no one maintained it, or because the ecosystem around it changed.

The distinction is not always easy to observe. Apple’s practice of sealing iPhone batteries inside the device body — making replacement difficult and expensive without specialized tools — is widely described as planned obsolescence. But Apple has also stated that the batteries degrade over time due to chemical aging, which is a natural property of lithium-ion cells. The design decision (sealing the battery) makes replacement harder. The chemical property (battery degradation) makes replacement necessary. Which one is the cause? Both. The design amplifies the effect of the chemistry.

HP’s chip-locked ink cartridges are a clearer example. HP embedded a microchip in each ink cartridge that tracks usage. When the chip detects that the cartridge has reached its intended page count, it disables the cartridge even if ink remains. This is a deliberate design choice. The product stops working because the manufacturer decided it should. The obsolescence is encoded in firmware.

The legal response

Several jurisdictions have responded to planned obsolescence with regulation. France passed a law in 2015 that created an “obsolescence index” manufacturers must display on product packaging. The index rates a product’s durability based on factors including firmware update availability, repairability, and resistance to planned obsolescence. The law also introduced the crime of planned obsolescence, defined as “setting apart from the rest of one’s offerings of goods and services a range of products by deliberately adopting design choices that limit the lifespan of a product.” The maximum penalty is a fine of up to €300,000 and up to two years in prison.

The European Union has taken broader action. In 2019, the EU introduced a EuP ErP directive that requires certain products to be available for repair for at least ten years after placement on the market. In 2025, the EU adopted a Right to Repair regulation that requires manufacturers to make repair services and spare parts available for designated product categories, including washing machines, dishwashers, refrigerators, and smartphones.

These regulations treat planned obsolescence as a market failure. The assumption is that consumers would purchase more durable products if the information were available and the choice were genuinely optional. Manufacturers argue that durability increases costs, which increases prices, which reduces sales. The debate is not about whether products should last a certain number of years. It is about who decides how long they should last and who bears the cost.

When obsolescence is desirable

Not all planned obsolescence is harmful. Some products are designed to be disposable because the alternative is worse. A surgical mask that is designed to be discarded after one use is not a failure of durability. It is a feature. A firework that explodes after being lit is not defective because it does not last forever. It is functioning as intended.

The question is not whether products should be durable. It is whether durability serves the consumer’s interest in each specific case. A product that is too durable can be worse than one that is too fragile. A smartphone with a battery that lasts ten years might be impossible to replace when it eventually degrades, rendering the entire device useless. A smartphone with a battery that degrades in two years is replaceable. The trade-off is not between durability and fragility. It is between repairability and permanence.

Similarly, some planned obsolescence protects the buyer. Software that stops working when security updates are no longer available is not failing. It is preventing the buyer from running an insecure system. The product is obsolete because the environment has changed, and the manufacturer’s decision to stop supporting it prevents the buyer from continuing to use a vulnerable system. This is a form of protective obsolescence — the system becomes unusable to protect the buyer from a greater risk.

What unplanned obsolescence reveals about neglect

The more common form of obsolescence is unplanned. It is also the less studied form, because it does not involve a clear agent to blame. When a product becomes obsolete through neglect, the failure is distributed across a chain of actors: the original designer, the maintainers, the buyers, the ecosystem providers. No single decision causes the obsolescence. It accumulates.

The pattern appears in open-source software. A library maintained by a single volunteer eventually becomes obsolete when the maintainer stops working on the project. The library is not broken. It is unmaintained. But in a dependency graph that requires active maintenance, unmaintained and broken are functionally equivalent.

The pattern appears in digital archives. A collection of documents stored in a file format that no modern application supports is not corrupted. The bits are intact. The documents are unreadable. The obsolescence was not planned. It was the result of an ecosystem that moved on.

The pattern appears in infrastructure. A bridge designed for a specific traffic load eventually becomes obsolete when the traffic pattern changes. The bridge is still structurally sound. It is obsolete because its function no longer matches the environment.

Unplanned obsolescence is the default mode for most systems. Planned obsolescence is the exception. The reason planned obsolescence receives more attention is that it involves a clear agent and a clear motive. Unplanned obsolescence involves no one in particular. It is the result of a million small decisions not to maintain, not to update, not to adapt.

The role of maintenance

Maintenance is the activity that prevents unplanned obsolescence. It is also the activity that is most easily deferred. A system that requires regular maintenance is less appealing than a system that works without it. The appeal is rational: maintenance costs time, money, and attention. The cost is deferred until the system breaks.

Planned obsolescence shifts the cost of maintenance from the buyer to the manufacturer. The manufacturer builds the maintenance into the product’s lifecycle. When the product stops working, the buyer replaces it. The manufacturer profits from the replacement. The buyer pays for the replacement. The cycle continues until the product line is discontinued.

Unplanned obsolescence shifts the cost of maintenance to no one. The system continues to work until no one is maintaining it. At that point, the system becomes obsolete and the buyer must find a replacement. The cost of finding and adopting the replacement falls on the buyer, who did not choose the obsolescence and did not pay for the maintenance that would have prevented it.

This asymmetry is the core problem. Planned obsolescence externalizes the cost of replacement to the buyer but internalizes the benefit to the manufacturer. Unplanned obsolescence externalizes the cost of both maintenance and replacement to no one. Neither system provides a clear incentive for maintaining systems that outlast their immediate usefulness.

Why the distinction matters

The distinction between planned and unplanned obsolescence is not just semantic. It determines who is responsible, what remedies exist, and whether the obsolescence can be prevented.

Planned obsolescence is a design problem. It can be addressed through regulation, transparency, and market pressure. If consumers know that a product is designed to stop working, they can choose not to buy it. If manufacturers are required to disclose obsolescence mechanisms, they can be held accountable. If regulation penalizes planned obsolescence, manufacturers can factor the cost into their design decisions.

Unplanned obsolescence is a maintenance problem. It cannot be addressed through transparency or regulation alone. It requires sustained investment in maintenance, whether by the original manufacturer, a third party, or the community. The economic challenge is that maintenance is a public good: the benefits are distributed across all buyers, but the costs fall on a single maintainer. Without a mechanism for distributing those costs, maintenance eventually stops.

The distinction also matters for how we think about progress. Planned obsolescence implies that the new is always better than the old. Unplanned obsolescence implies that the new replaces the old whether the new is better or not. One is a market strategy. The other is an accident of time. Both produce the same result: the old is discarded.

What remains unresolved

No single approach solves the obsolescence problem. Regulation can limit planned obsolescence but cannot prevent unplanned obsolescence. Transparency can inform consumer choice but cannot make maintenance economically viable. The right to repair movements address one part of the problem — the inability to fix products — but not the broader question of why systems stop being maintained.

The fundamental uncertainty is structural: how do societies maintain systems that outlive the people who designed them? The answer varies by domain. Software is maintained by communities when it is valuable enough to sustain them. Hardware is maintained by manufacturers when the profit incentive exists. Infrastructure is maintained by governments when the political will exists. None of these mechanisms is universal. All of them require sustained investment that is easily deferred and hard to justify until the system fails.

The question is not whether obsolescence will happen. It is who decides when it happens and who pays for it. Planned obsolescence answers both questions: the manufacturer decides, and the buyer pays. Unplanned obsolescence answers neither: no one decides, and the cost falls on whoever encounters the broken system first.