Comment by BenWebbProject

Interesting article - most products are treated as “delivered” the moment they ship. A project manager hands over, success is declared, and the organisation moves on. But physical products with embedded software don’t stop being systems just because the project ends — they keep accumulating risk, cost, and user impact right through to end-of-life.

What usually gets missed is that end-of-life is still part of the project, even if it sits years downstream. When software support is withdrawn without a transition path, the hardware doesn’t just lose features — it loses trust. That’s not a technical failure, it’s a lifecycle planning failure.

Open-sourcing at sunset is interesting because it’s one of the few mechanisms that acknowledges this gap. It doesn’t help most users directly, but it at least hands control back instead of silently bricking capability.

I’m curious whether we’ll start seeing project managers and product teams treat “exit conditions” as a first-class deliverable — with explicit decisions about data, firmware, APIs, and ownership once commercial support ends — rather than treating end-of-life as someone else’s problem.