Engineered to Expire: How Planned Obsolescence Is Shortening British Hardware Lifespans

The average British business replaces its desktop and laptop hardware on a three-to-four-year cycle. The average British consumer replaces a smartphone every two to three years. In both cases, the prevailing justification is that the existing device has become too slow, too incompatible, or too unsupported to remain productive. What is rarely examined is whether those conditions arose naturally or were deliberately cultivated.

Planned obsolescence—the practice of designing or positioning products to become functionally inadequate within a commercially convenient timeframe—is not a new concept. What has changed is the sophistication with which it is now applied to computing hardware, and the degree to which software publishers, operating system vendors, and peripheral manufacturers coordinate, whether explicitly or structurally, to shorten the productive life of equipment that could otherwise serve for considerably longer.

The Software Compatibility Mechanism

The most effective tool in the planned obsolescence arsenal is not physical degradation but software incompatibility. When an operating system vendor announces minimum hardware requirements for a new release, the decision is framed as a technical necessity. The reality is frequently more nuanced.

Windows 11's TPM 2.0 requirement is an instructive case. The security argument for the requirement is legitimate in isolation—Trusted Platform Module functionality does provide meaningful security benefits. However, the implementation decision to exclude hardware that lacks TPM 2.0 at the firmware level, rather than providing a pathway for compatible devices to enable the feature, rendered millions of otherwise capable machines ineligible for upgrade. Many of those machines were three or four years old and performing without issue on Windows 10.

The consequence for British organisations is a procurement obligation that the hardware's physical condition does not justify. A machine running Windows 10 on a quad-core processor with sixteen gigabytes of RAM and a solid-state drive is not a slow machine. It is, however, a machine that will be classified as end-of-life when Windows 10 support concludes in October 2025, regardless of its actual performance characteristics.

Performance Degradation Through Updates

Software updates present a second mechanism through which hardware lifecycles are compressed. Operating system and application updates accumulate over time, and successive releases are typically optimised for current-generation hardware rather than the installed base. The result is a gradual degradation of performance on older devices that mirrors physical decline but originates in software.

This phenomenon is not always inadvertent. Several major smartphone manufacturers have faced regulatory scrutiny and legal action in multiple jurisdictions—including the UK—following evidence that software updates introduced throttling mechanisms on older devices. The ostensible justification was battery management; the practical effect was to make older devices feel significantly slower and to increase the perceived need for replacement.

On the desktop and laptop side, the mechanism is less overt but structurally similar. Bloated update packages, background telemetry processes, and increasingly resource-intensive browser architectures all consume processing and memory headroom that was previously available for productive work. A machine that ran comfortably four years ago may feel sluggish today not because its components have degraded, but because the software environment in which it operates has expanded to fill and exceed its available resources.

The Peripheral Compatibility Cycle

Hardware obsolescence is also driven by deliberate changes to peripheral interfaces and connectivity standards that render existing equipment incompatible with new products. The transition from USB-A to USB-C is a legitimate technological progression with genuine benefits in terms of throughput and versatility. The pace at which manufacturers removed legacy ports from devices—forcing the purchase of adapters or entirely new peripherals—was, however, a commercial decision as much as a technical one.

Similar dynamics apply to display standards, wireless connectivity protocols, and storage interfaces. Each successive generation introduces improvements, but the withdrawal of backward compatibility is rarely technically mandated. It is a choice, and that choice consistently benefits manufacturers' revenue cycles at the expense of buyers' existing investments.

Identifying Genuine Upgrade Need Versus Manufactured Demand

The following framework assists in distinguishing between a legitimate upgrade requirement and one that has been artificially created.

Assess actual performance, not perceived performance. Before concluding that a machine is too slow, benchmark it against the specific tasks it is required to perform. A device that struggles with video editing may be entirely adequate for document processing and communications. Replacement should be scoped to the workload, not the marketing cycle.

Separate software from hardware limitations. If performance has declined following a software update, the cause is software, not hardware. Reinstalling the operating system, removing unnecessary background processes, or rolling back a specific update may restore performance without any hardware expenditure.

Evaluate compatibility claims critically. When a software vendor declares a device incompatible, investigate whether the incompatibility is technical or commercial. In some cases, community-developed workarounds or alternative software products provide equivalent functionality on hardware that has been officially designated as unsupported.

Quantify the productivity cost of not upgrading. If a device is genuinely impeding productivity, the cost of that impediment should be calculated and weighed against the cost of replacement. In many cases, targeted component upgrades—additional RAM, a faster storage drive—deliver the majority of the performance benefit at a fraction of the cost of full replacement.

Consider the total lifecycle cost. A device purchased for £800 and replaced after three years has an effective annual cost of approximately £267. The same device retained for five years, with a £150 storage upgrade in year three, delivers a meaningfully lower total cost of ownership and produces less electronic waste.

The Strategic Response for British Businesses

Organisations that approach hardware procurement strategically—rather than reactively responding to manufacturer refresh cycles or software end-of-life announcements—consistently achieve better outcomes. This means establishing internal criteria for replacement that are based on measurable productivity impact rather than vendor timelines, investing in component-level upgrades where they deliver genuine benefit, and procuring hardware with specifications that provide adequate headroom for the anticipated software environment over a realistic operational period.

The hardware refresh cycle is not immutable. It is, to a considerable degree, a commercial construct. Recognising it as such is the first step towards a procurement strategy that serves organisational needs rather than manufacturer revenue targets.