Retire features customers no longer need — measure usage, warn the few who depend on it, offer a migration path, and remove it cleanly.
PMs reducing surface area and maintenance cost without burning trust.
Quick answer
The Feature deprecation template is a ready-made workspace for PMs reducing surface area and maintenance cost without burning trust.
Feature deprecation template in short
Included when you apply it
Applying this template creates the 1 board below — with every list — and pre-loads 3 sample issues, all yours to edit. The automation rules further down are suggestions you can wire up next; they aren't created for you yet.
A preview of how this template lays out — the boards, their custom workflow states, and where the sample issues land. WIP caps show a badge.
Sunsets
Sunset the legacy list view — 0.3% weekly usage
Migration: the new table view covers every use case.
Notify the 40 accounts still using the old API export
Write the in-app migration banner + help doc
These rules aren't created when you apply the template — they're recipes you can wire up in Settings → Automations once your board exists.
When
Feature moves to 'Users notified'
Then
Show an in-app deprecation banner to remaining users of the feature
When
A user migrates off the feature
Then
Decrement the dependent-account count toward zero
Ready to spin this up?
Sign-up takes seconds. We build this template's boards, lists, and sample issues in your new workspace, all yours to edit.
FAQ
Product roadmap
A Now / Next / Later roadmap that flows discovery to ship, with initiative-level grouping and release notes at the end of the pipe.
View templatePRD tracker
Move specs from draft to approved with explicit review gates, so engineering never starts on a half-baked PRD.
View templateFeature requests
A single intake list for customer feature asks, deduped and labeled, so the loudest request isn't the only one you hear.
View template