Product Lifecycle and Sunsetting

Product lifecycle and sunsetting is the practice of managing a product from introduction through growth and maturity to retirement. It covers how teams decide when to deprecate or end-of-life a product or feature, and how they plan the shutdown so customers can migrate without disruption.

itEngineering leadership and delivery management

Don't Panic: Product Lifecycle and Sunsetting

Product lifecycle and sunsetting is the practice of walking a product to the door on purpose. Every product eventually reaches the quiet part of the curve: introduction, where nobody has heard of it; growth, where everybody wants a piece; maturity, where the accountants take over; and decline, where the interesting question stops being "how do we grow this?" and becomes "what now?". The "what now" is the actual subject here, and it turns out to be a whole discipline, not a farewell post.

The core idea is the deprecation ladder: active, then deprecated, then end of support, then end of life. Each rung is a promise. Deprecation says "we stopped building this; plan your exit." End of support says "it still runs, but you are on your own for updates." Removal says what it says. Teams that skip rungs do not save time; they simply deliver the entire migration bill to every customer on the same afternoon, which is a memorable way to be remembered.

Before the rungs, someone has to decide the product is actually in decline, and that is a measurement job: a new-customer trend over years rather than quarters, revenue against the cost of keeping the thing patched, and what the freed team could build instead. One bad quarter is a slump. Three years of downward curve with a rising support queue is decline, and no amount of wishful roadmap entries will fix it.

The part that surprises people: notice periods vary enormously, and the variance is a choice. Google Cloud's terms promise at least twelve months before discontinuing a service. GitHub supports the previous REST API version for at least twenty-four months after a new one ships. Heroku's free tier got roughly three months. Google Reader got about three and a half. The short ones are not accidents; they are the vendor keeping the option to be quick. Read the deprecation policy before you adopt, not before you panic.

Sunsetting done well is unglamorous logistics: align sales before the announcement, stop marketing a product you are about to remove, name the migration path, then watch migration completion instead of complaint volume. The loud letters come from people with time to write letters; the stuck ones show up in the completion numbers, which is why the numbers are the ones to watch.

Read the intro for the full stage model and the evidence rules. The slides compress the ladder and the promises. The cheatsheet holds the notice-period comparators and the execution sequence, and the practice reference turns it into a sunset review you can run. None of it requires a towel, but a migration plan serves the same purpose.

Don't Panic: Product Lifecycle and Sunsetting

Relevant careers