94. What would you check before switching off a legacy process after launching its replacement?
HardChange & outcomes
Case
Show model answer
I'd verify actual adoption, remaining users, exceptions, data access, retention needs and external dependencies. A successful launch or declining traffic does not prove no one still relies on the old path for a consequential task or unusual but legitimate service scenario.
I'd agree support, communications and authorized retirement criteria. Preserve required residual routes; silence is not consent, and removing an interface does not erase underlying obligations or external dependencies.
What interviewers listen for
- Identify residual legitimate use
- Verify data and operational obligations
- Retire through accountable criteria and support