Skip to content

Planned obsolescence

A product strategy that intentionally limits useful life, durability, compatibility, or perceived fashionability to accelerate replacement demand.

Version
v2 · 2026-09-06 · History
Domain-specific #
2495
Origin domain
industrial economics and product design
Subdomain
durability and replacement strategy
Aliases
Built-in obsolescence, Premature obsolescence

Core Idea

Planned obsolescence is a product strategy that intentionally limits useful life, durability, compatibility, or perceived fashionability to accelerate replacement demand.

Planned obsolescence is a producer strategy that intentionally limits or accelerates the economically relevant life of a product—through physical durability, repairability, compatibility, software support, parts, fashion, or upgrade design—in circumstances where earlier replacement is expected to benefit the producer. Short life alone is insufficient: recognition requires evidence connecting an avoidable design or policy choice to a replacement incentive or strategy.

Scope of Application

The abstraction recurs literally within durable goods, electronics, software-dependent products, appliances, vehicles, fashion systems, and repair ecosystems where producers influence replacement timing. The following habitats preserve the same recognition machinery; they are not invitations to extend the name metaphorically.

  • Physical durability. components are designed for a bounded wear life.
  • Repair restriction. parts, tools, or pairing make restoration uneconomic.
  • Compatibility. interfaces or consumables are changed to strand complements.
  • Software support. updates or services end while hardware remains functional.
  • Perceived obsolescence. style and marketing shorten acceptable use despite physical function.

Clarity

Separate observed lifespan from intentional strategy. Specify the controlled mechanism, technically and economically feasible alternative, safety and innovation tradeoffs, expected replacement response, and evidence of producer benefit or intent. Do not infer planning solely from frustration or correlation.

A practical identification audit begins with the typed roles rather than the title: establish the producer, verify the product and installed base, then test the remaining conditions and exclusions.

Manages Complexity

The abstraction joins engineering, market incentives, support policy, consumer behavior, and environmental effects. It makes competing explanations testable rather than treating any short-lived product as self-evident misconduct.

The compression remains accountable because each simplification has a named failure condition. Disagreement can be localized to a missing role, an invalid assumption, an ambiguous measurement, or a neighboring abstraction instead of being hidden inside an unanalyzed label.

Abstract Reasoning

R1. Measure the product's failure, support, compatibility, and replacement pattern. R2. Identify which life-limiting choices the producer actually controlled. R3. Construct a feasible longer-life counterfactual including cost, safety, and performance tradeoffs. R4. Test whether the chosen limitation predictably advances a replacement or lock-in incentive. R5. Seek strategy evidence and evaluate consumer welfare, competition, and environmental consequences.

Knowledge Transfer

The term transfers among producer-controlled durable-product systems only when intentional life limitation and replacement incentive are established. Incentive and constraint are parents; biological aging or accidental fragility is not planned obsolescence.

The transfer boundary is explicit: DOMAIN-SPECIFIC PASS / PRIME FAIL: The strategy recurs across product categories through frail design, fixed service horizons, incompatibility, and fashion cycles. Literal recognition retains the specialist vocabulary and validity conditions of industrial design and product economics; outside that setting only broader parent operations transfer.

Relationships to Other Abstractions

Local relationship map for Planned obsolescenceParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Planned obsolescenceDOMAINPrime abstraction: Incentive — presupposesIncentivePRIMEPrime abstraction: Temporal Decay and Degradation — is a kind ofTemporal Decayand DegradationPRIME

Current abstraction Planned obsolescence Domain-specific

Parents (2) — more general patterns this builds on

  • Planned obsolescence is a kind of Temporal Decay and Degradation Prime

    The accepted reference-grade review places Planned obsolescence under Temporal Decay and Degradation because the child instantiates or depends on the parent's broader structure while retaining its own constitutive identity.

  • Planned obsolescence presupposes Incentive Prime

    Incentive (prime:incentive).

Hierarchy paths (3) — routes to 3 parentless roots

Neighborhood in Abstraction Space

Planned obsolescence sits in a sparse region of the domain-specific corpus (66th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Startup Learning & Innovation Strategy (16 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08