End of Life Is Not an Expiration Date

No physical product lasts forever.

Materials age.

Surfaces wear.

Bearings lose precision.

Seals become less effective.

Batteries lose capacity.

Insulation experiences heat, vibration, moisture and time.

Connections loosen.

Software eventually meets hardware, standards or services that did not exist when the product was designed.

The responsible engineering response is not to pretend that these changes will never happen.

It is to study them.

To estimate when they are likely to become important.

To warn the owner before inconvenience becomes danger.

To design maintenance, repair and recovery around the reality that every product has a lifecycle.

End-of-life engineering should predict the end of safe and useful service. It should never manufacture an artificial ending merely to create another sale.

Every Product Ages Differently

Two identical products can experience very different lives.

One may operate indoors at moderate temperature and light load.

Another may spend every day in heat, dust, humidity, vibration or repeated overload.

One owner may perform maintenance carefully.

Another may not know that maintenance is required.

One unit may operate for a few hours each week.

Another may run almost continuously.

For this reason, a product rarely has one exact birthday on which it suddenly becomes old.

Engineers usually work with probabilities, duty cycles, environmental assumptions, test results and known failure modes.

A rated lifetime is therefore not a prophecy.

It is an estimate based on defined conditions.

That estimate becomes useful only when the assumptions are communicated honestly.

Useful Life, Service Life and Safe Life

The phrase “end of life” can describe several different moments.

Useful life ends when the product no longer provides enough practical value for the owner’s needs.

Service life ends when normal maintenance and reasonable repair can no longer keep the product operating economically or reliably.

Safe life ends when continued operation creates an unacceptable risk, even if the product can still perform its basic function.

These moments are not always the same.

A battery may remain functional but no longer hold enough energy for its original application.

A machine may still run while a critical structural component approaches a fatigue limit.

A computer may remain physically healthy but become unable to use essential modern software.

A device may no longer satisfy one owner while remaining useful to another.

Responsible end-of-life planning should recognize these differences rather than treating every old product as waste.

Prediction Is a Form of Protection

When a company studies how its products age, the customer gains something valuable: time.

Time to inspect a component.

Time to plan maintenance.

Time to order a replacement part.

Time to transfer a workload.

Time to replace a safety-critical assembly before failure.

Time to budget for an upgrade instead of being surprised by a sudden loss.

Testing should therefore ask more than whether a new product works.

It should ask how performance changes after hundreds, thousands or millions of cycles.

Which parts age first?

Which symptoms appear before failure?

Which measurements reveal deterioration?

Which maintenance actions extend life?

Which components should be inspected rather than simply trusted?

How does the product fail when the expected life is exceeded?

Does it fail gradually, visibly and safely?

Or does it fail suddenly and unpredictably?

Understanding these answers is not pessimism.

It is responsible design.

A Date Should Not Replace Condition

Some products require firm retirement limits because hidden damage cannot be assessed reliably or because failure would create severe consequences.

In those cases, conservative replacement rules may be necessary.

But many ordinary products should not be declared worthless simply because a calendar date has passed.

Condition matters.

Usage matters.

Maintenance history matters.

Measured performance matters.

A lightly used product may remain healthy beyond an average estimate.

A heavily used product may require attention much earlier.

Where practical, lifecycle management should combine age with condition monitoring.

The objective should be to replace what has become unsafe or uneconomical—not everything that has become old.

The Historical Warning of the Light Bulb

The Phoebus light-bulb cartel is widely cited as an early warning about the commercial manipulation of product lifetime.

Manufacturers coordinated technical and market practices around incandescent lamps, and the episode became associated with the deliberate shortening of expected bulb life.

The industrial history contains technical and economic complexity, but the ethical lesson remains clear.

A lifetime standard can protect quality when it establishes honest minimum performance.

The same idea can become destructive when companies use coordination, design or support policy to prevent products from lasting as long as they reasonably could.

The danger is not only that one bulb fails sooner.

The danger is that engineering knowledge is used against the user.

The company understands how to extend life.

Instead of applying that knowledge, it applies the opposite.

Failure becomes a sales schedule.

Planned Obsolescence Is Not Always a Weak Component

Artificially shortened life can appear in many forms.

A part may be designed with an unnecessarily low durability margin.

A battery may be permanently trapped inside an otherwise functional product.

A small wear component may be unavailable separately.

A software service may be discontinued while the hardware remains capable.

A diagnostic function may be hidden.

A repair manual may be withheld.

A connector or communication protocol may be changed without a meaningful technical reason.

A product may be sealed with adhesive where ordinary fasteners would have allowed service.

Obsolescence can therefore be mechanical, electrical, digital, commercial or informational.

It does not always look like something breaking.

Sometimes the product still works, but the company has removed the practical path to continue using it.

Not Every Short Life Is Planned Obsolescence

It is equally important not to accuse every limited-life product of deception.

Longer life can require greater mass, more expensive materials, larger safety margins, additional maintenance or reduced performance.

A component selected for a portable product may not be appropriate for industrial service.

A low-cost product may have real design constraints.

A lighter structure may experience more wear than a heavier one.

A high-performance system may operate closer to material limits.

An affordable medical, educational or energy product may create enormous social value even if it cannot be engineered for unlimited life.

The ethical question is not whether every product lasts forever.

The question is whether the company made honest trade-offs, communicated them clearly and supported the product as responsibly as the design allowed.

End-of-Life Information Belongs to the Owner

A company should not keep all lifecycle knowledge inside its laboratory.

The owner should receive understandable information about:

Expected wear items.

Inspection intervals.

Symptoms that require attention.

Parts with limited service life.

Conditions that accelerate aging.

Maintenance that meaningfully extends use.

Safe storage.

Available replacement parts.

Repair and refurbishment options.

Responsible return or recycling routes.

This information should not be written only for specialists.

A simple product may need only a short maintenance guide.

A complex system may need a service record, diagnostic history and condition indicators.

The owner does not need every engineering calculation.

The owner does need enough information to make responsible decisions.

The Product Should Prepare for Its Own Future

End-of-life planning begins during design, not after sales decline.

Engineers should ask:

Can the high-wear component be replaced?

Can the product be opened without destroying it?

Can stored data be exported?

Can the battery or power module be renewed?

Can the owner identify deterioration?

Can a technician obtain parts and documentation?

Can useful modules be reused?

Can materials be separated?

Can the product enter a second application when it no longer satisfies the first?

A product designed without these questions reaches old age unprepared.

Its value disappears faster because the route to preserve that value was never created.

Safety-Critical Retirement Must Be Honest

There are situations where longevity must surrender to safety.

Pressure-containing parts, lifting components, structural elements, protective equipment, high-energy systems and other critical assemblies may require defined inspection or retirement rules.

Those rules should be conservative, evidence-based and easy to understand.

They should not be extended casually when human life depends on the result.

But safety should also never be used as a vague marketing excuse to force replacement of unrelated parts.

The company should explain which component creates the limitation, why it cannot be inspected or restored, and what safe alternatives exist.

Human life deserves strict boundaries.

Customers deserve truthful boundaries.

End of One Life Can Begin Another

A product that no longer fits its original role may still contain useful value.

A battery with reduced capacity may serve a lower-demand application after proper evaluation.

A computer retired from professional design work may remain valuable for education or basic administration.

A returned device may be refurbished.

Functional modules may become service parts.

Materials may be recovered.

Failure records may improve the next generation.

End of life should therefore be a decision tree, not a trapdoor.

Inspect.

Maintain.

Repair.

Upgrade.

Repurpose.

Refurbish.

Recover components.

Recycle materials.

Dispose only when meaningful recovery is no longer responsible or practical.

The Answer

Should companies estimate when products will wear out?

Yes.

They should test aging honestly.

They should identify the parts most likely to deteriorate.

They should communicate uncertainty.

They should establish inspection and safe-retirement rules where necessary.

They should support repair, refurbishment and value recovery.

They should improve the next generation using evidence from the previous one.

But they should never confuse prediction with permission.

Knowing when a product may fail does not give a company the ethical right to make it fail sooner.

Understanding a lifecycle should help protect the owner.

It should not be used to control the owner.

Engineers should predict the end of a product’s safe life. They should never manufacture the end of its useful life merely to create another sale.