Feature Deprecation & Sunsetting

Usage evidence, a written deprecation policy, customer notice schedules, migration paths and exports, a calm removal day and an honest review afterwards, for product teams and managers retiring features or whole products.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Feature Deprecation & Sunsetting, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

204

Starter tasks

🧩 Product Management

Feature Deprecation & Sunsetting

Retiring features or products responsibly, with usage evidence, customer notice, migration paths and support for the people affected.

  1. Feature inventory with owners and usage
  2. Written deprecation policy with notice periods
  3. Lifecycle stages from announced to removed
  4. Usage evidence pack for a retirement candidate
  5. Carrying cost estimate for a legacy feature
  6. Contract and promise check before retiring
  7. Retire, keep or rebuild decision record
  8. Affected account list by segment and exposure
  9. Named sunset owner and working group
  10. Quarterly retirement candidate review
  11. Monthly usage watch on deprecated features
  12. Weekly sunset stand-up during active retirements
  13. Register of active deprecations and dates
  14. Customer notice schedule for each retirement
  15. Support ticket tagging for deprecation contacts
  16. Monthly briefing for account teams
  17. Internal dependency check on deprecated code paths
  18. Annual review of the deprecation policy
  19. Post-removal clean-up tracker
  20. Writing deprecation notices customers act on
  21. Reading usage data for retirement decisions
  22. Handling hard conversations about a removed feature
  23. Case studies of well and badly handled sunsets
  24. Estimating customer migration effort
  25. Spotting sunk cost thinking in keep decisions
  26. Data retention and export basics for retirements
  27. Migration path to the replacement feature
  28. Self-serve data export for the retiring feature
  29. Migration guide in the help centre
  30. Choosing hard removal, read-only or hidden
  31. Extension and exception rules for holdout accounts
  32. Credit or concession decision for paying customers
  33. Hiding the feature from new accounts first
  34. Deprecation announcement day
  35. Final reminder push a month before removal
  36. Brownout test before switch-off
  37. Sunset readiness review before removal
  38. Removal day runbook and switch-off
  39. Thirty-day post-removal review
  40. Retiring a feature your own team built
  41. Leadership case for retiring a revenue feature
  42. Inheriting a half-finished deprecation
  43. Small-team retirement without dedicated support
  44. Migration support for a critical enterprise account
  45. Sequencing several retirements as a manager
  46. API version sunset with deprecation headers
  47. Minimum app version for removed mobile features
  48. End-of-life plan for a whole product
  49. Retirement outcome scorecard across past sunsets
  50. Reusable deprecation playbook for the organisation

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Feature inventory with owners and usage

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most products carry features nobody owns any more: a report built for one customer years ago, a legacy editor kept behind a setting, an integration with a tool that has since shut down.

First tasks

  • List every menu item and settings screen in the product in one sheet
  • Add the owning team for each feature from the engineering team list
  • Ask the analytics lead for monthly active accounts per feature
  • Flag every feature used by fewer than 2 percent of active accounts
  • Refresh owners and usage figures in the feature inventory @recurring(yearly)

Written deprecation policy with notice periods

When each retirement is negotiated from scratch, the loudest customer sets the notice period and sales promises exceptions nobody can keep. A short written policy stating minimum notice by feature type, who approves a retirement and what affected customers are always offered makes every later sunset faster and easier to defend.

First tasks

  • Collect the notice periods used in the last three retirements, if any
  • Draft minimum notice periods for three categories of feature
  • Ask legal which notice terms already appear in customer contracts
  • Circulate the draft policy to support, sales and engineering leads
  • Publish the agreed policy on the internal product wiki

Lifecycle stages from announced to removed

Words like deprecated, legacy, end of life and sunset mean different things to different teams, and customers hear them differently again. Defining four or five named stages, each with what still works, what support covers and what the product shows, lets everyone describe a retirement in the same terms.

First tasks

  • Write down every term your teams currently use for retiring features
  • Draft a one-line definition for each proposed lifecycle stage
  • Agree with support what help is offered at each stage
  • Add the stage definitions to the policy and the help centre glossary

Make it yours.

Install Feature Deprecation & Sunsetting, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.