Architecture & practice·Legacy systems and migration
the replacement was blocked for two months on a report that four people run once a year.
Feature parity
The requirement that a replacement do everything the thing it replaces did. It is where most migrations go to die, because the last ten percent of features are used by the smallest number of people and take the longest, and nobody is empowered to say a feature will simply be dropped. The conversation that unblocks it is a usage-based one: name who uses each remaining feature, how often, and what happens if it goes.