Sometimes a token, pattern, or process has outlived its usefulness. Retiring and replacing outdated work keeps the system lean, avoids duplication, and directs teams toward better solutions. Use this when existing work no longer meets requirements, when a new version makes it redundant, or when redundant duplication is surfaced during an Audit or System Health Check.
How to
-
Identify candidates Find tokens, patterns, or processes that are outdated, duplicated, or failing checks. These are often uncovered during an Audit or System Health Check.
-
Decide on replacement Choose the best solution with the least friction. Decide if the item can be updated, merged, or fully replaced.
-
Plan migration Set a clear timeline for adoption. Provide Migration Guides to make the switch easy, whether by deprecating the old item, flagging it in your Guidance Setup, or running it side by side until adoption is complete.
-
Communicate changes Announce the retirement and explain why. Highlight the benefits of moving to the new version. Share as part of your Release and System Updates.
-
Remove and clean up Phase out the old work once adoption of the replacement is high. Update documentation, code references, and guidance so teams are not relying on outdated items.