> This is stuff that will - by definition - Never be a priority in management's eyes. I'm not sure why you think that is "by definition" not a priority. Of cou

> This is stuff that will - by definition - Never be a priority in management's eyes. I'm not sure why you think that is "by definition" not a priority. Of course it is if it's impacting being able to do new work that adds value. The question is, is that a priority at the moment it's noticed, or something that should be added to a backlog to be addressed later? If it's a small amount of code clean-up, it's usually easy to squeeze into current work without disruption. We always try to refactor as we go along. If it's "This 3000 lines needs to be redesigned and rewritten", it really amounts to feature work and should be added to a backlog and prioritized along with all the other work. The phenomenon I'm talking about is ICs seeing something for the first time, and then deciding that must be the priority because it's so bad, and dropping everything else to fix that thing even if it's weeks worth of work. They see what's in front of them as the thing that's most important.