1. Slow it all down. Jeff Bezos may not be a good person, but he understands how to run a business. If he calls himself, "Chief Slowdown Officer", then maybe it

1. Slow it all down. Jeff Bezos may not be a good person, but he understands how to run a business. If he calls himself, "Chief Slowdown Officer", then maybe it's good for other organizations to think things through before doing them. 2. Reduce churn, both in employer turnover and in re-organizations. 3. Teams just need to talk to each other. It doesn't have to be everyone-to-everyone all the time because that's a function of quadratic order, but people should have a chance to ask each other questions. 4. Reduce scope. My suggestions are mostly about avoiding the situation you're in. Legacy issues like yours are tough to tackle. The one obvious choice is a code freeze, then rewrite.