Taking things away.
WHY IT IS NECESSARY
Every feature costs testing, support, documentation and complexity forever.
WHAT TO IDENTIFY
Features almost nobody uses.
HOW
Usage data, per account.
WHAT TO CHECK BEFORE REMOVING ANYTHING
Who uses it, specifically.
WHY
A feature used by two per cent may be essential to your largest customer.
WHAT TO DO
Contact every account using it, individually.
WHAT TO OFFER
An alternative, or help moving.
WHAT NOTICE TO GIVE
Substantial, and more for anything customers built process around.
WHAT TO COMMUNICATE
What is being removed When Why What to do instead
WHY THE REASON MATTERS
Removal without explanation reads as neglect.
WHAT TO AVOID
Removing things silently Removing something customers pay specifically for Removing without an alternative
WHAT TO DO IF SOMEONE CANNOT MOVE
Consider keeping it for them, or helping them leave gracefully.
WHY THAT SECOND OPTION IS LEGITIMATE
Retaining a customer you cannot serve properly benefits nobody.
WHAT TO MEASURE AFTERWARDS
Whether complexity actually reduced.
WHAT TO RECORD
The decision and its reasoning.
