There is No Automatic Reset for Engineering
Do you remember all those rushed changes that your developers implemented three years ago, and how they complained about the design damage they caused to make that happen? It's all still in the codebase. It never disappears. You may have forgotten it, but they still live with it every day. I'm not saying you were wrong to be in a hurry then; I'm only saying it's not over It Does Not Heal Itself In engineering, software or otherwise, whatever decision we make this month, we have to live with it from now on, or until someone invests additional time in reversing it. That hack is as permanent a part of the product as any well-considered change. It doesn't refresh with the next month, quarter, or planning period. it doesn't fade away. It doesn't heal. There is no end-of-period reset. Making new goals doesn't remove the baggage of prior goals. Do the other people have to live with January 2013 for the rest of their lives? Or is it only engineering that has...