Hardware & Smart Home

Planned Obsolescence

Also known as: product obsolescence, built-in obsolescence, software obsolescence, e-waste, device lifecycle, end of support

Planned obsolescence is the business strategy of designing products to become outdated or non-functional after a predictable period, encouraging consumers to purchase replacements sooner than necessary.

In technology, it appears in several forms: physical obsolescence (non-replaceable batteries, soldered components that fail without repair options), software obsolescence (dropping OS support for older hardware that is still physically functional), feature obsolescence (marketing new features to make current products feel outdated), and systemic obsolescence (accessories and peripherals made incompatible with new product generations). Planned obsolescence generates recurring revenue for manufacturers but contributes significantly to electronic waste (e-waste) and consumer frustration.

Planned Obsolescence, explained at three levels

At home

Planned obsolescence means a company designs a product so that you'll want or need to replace it sooner than you should. Some forms are obvious: a phone battery that can't be replaced means you'll replace the whole phone when the battery dies. Some are more subtle: a company might stop releasing software updates for a device that still works fine physically, meaning it can no longer run current apps or security patches. Or they might release a 'new' product with features that make your current device feel old, even when your current device works perfectly. The result: you buy new things more often than you would if products were designed to last longer.

At work

Planned obsolescence is relevant to enterprise technology procurement because it directly affects total cost of ownership and device lifecycle planning. If a manufacturer typically drops OS support for hardware at 5 years, enterprise refresh cycles should account for this: devices aren't usable indefinitely regardless of physical condition. Conversely, recognizing planned obsolescence helps challenge vendor claims: a device marketed as needing replacement due to 'end of support' may be physically capable of longer service with alternative OS options (Linux for retired Windows hardware, for example). Understanding the difference between genuine obsolescence (hardware limitations) and manufactured obsolescence (software support decisions) informs procurement and lifecycle strategy.

Real-world examples

At home

Aisha had a 7-year-old Intel MacBook that ran perfectly for her needs (browsing, email, documents). Apple dropped support for her model in a macOS update: it could no longer run the current OS, meaning it would stop receiving security updates and some apps would eventually drop support. Her MacBook wasn't slow or broken; it was artificially obsoleted by software support ending. She installed Linux (Ubuntu) on it, which gave the MacBook another 3-5 years of security updates and modern software compatibility. Physical device, still functional: software decision, not hardware limitation, drove the obsolescence.

At work

Marcus managed IT for a school district with a limited budget. Hundreds of its 6-year-old Windows laptops could not run Windows 11, and free Windows 10 security updates ended in October 2025. Rather than replacing every device, he checked which machines had real hardware failures and whether ChromeOS Flex (Google's free version of ChromeOS for older PCs and Macs) could extend the life of the rest, since classroom work ran almost entirely in the browser. He moved 60% of the laptops to ChromeOS Flex, getting about 2 more years from them, deferring a $180,000 replacement cycle and reducing e-waste.

Common confusions

  • Many consumers assume that manufacturers intentionally slow down all older devices as a deliberate obsolescence strategy — Apple's Batterygate (slowing iPhones with degraded batteries) was a real and documented case of software behaviour that accelerated perceived obsolescence, but not all device slowdowns are intentional. Software updates designed for current hardware often perform worse on older hardware due to genuinely increased computational requirements (higher resolution assets, more ML processing, more complex security operations). Bloatware accumulation, storage fragmentation, and legitimate security overhead also slow devices over time without manufacturer intent. The distinction matters for evaluating when a slowdown is a feature (enabling throttled performance to extend battery life when needed) versus a design choice that prioritizes sales over user experience: the Apple case was problematic because the behaviour was not disclosed, not because performance management of degraded batteries is inherently wrong.
  • Some assume that buying the most expensive or premium products guarantees longer product support and freedom from planned obsolescence — Price does not reliably predict product longevity or support duration. Some premium products have shorter software support than mid-range alternatives: Samsung's premium Galaxy S-series (7 years of updates, announced in 2024) has longer committed support than many premium Windows laptops, whose makers may stop providing driver and firmware updates well before Windows itself stops supporting the hardware. Apple's devices receive iOS updates for 5-7 years; Google's Pixel line now offers 7 years. Checking the manufacturer's committed software support duration for a specific product (not its price) is the reliable way to assess expected useful software lifetime before purchase.

For analysts

Planned obsolescence is a strategic lens for technology lifecycle and vendor management advisory. Practical applications: advising on device refresh cycles should distinguish between genuine hardware obsolescence (performance insufficient for required workloads) and manufactured obsolescence (software support ending while hardware is capable); procurement decisions should include software support commitment duration as a specification alongside hardware specs; ESG-focused clients should assess device repairability scores and right to repair compliance as part of sustainable procurement policies; and vendor contracts should include software support minimums that align with the client's device lifecycle expectations. The cost of premature device replacement due to planned obsolescence is often far higher than the premium for devices with better longevity credentials.

History & origin

The term 'planned obsolescence' dates to Bernard London's 1932 pamphlet and was popularized by industrial designer Brooks Stevens in 1954, who defined it as 'instilling in the buyer the desire to own something a little newer, a little better, a little sooner than is necessary.' General Motors in the 1920s pioneered annual model changes in automobiles to make prior models feel outdated, countering Ford's 'one car for everyone' philosophy. In consumer electronics, planned obsolescence gained scrutiny through Apple's iPhone 'Batterygate' (2017): Apple acknowledged slowing down older iPhones with degraded batteries to prevent unexpected shutdowns: a practice consumers felt was designed to encourage upgrades. Apple paid $500M in a class action settlement and introduced iPhone battery health transparency. Right to repair advocates argue that restricted repairability (non-replaceable batteries, software parts pairing) is a form of planned obsolescence that accelerates the replacement cycle beyond what hardware longevity alone would dictate. The EU's Ecodesign for Sustainable Products Regulation (2024) directly addresses planned obsolescence by requiring manufacturers to support software updates and provide spare parts for defined periods.