Three skills needed to land a big refactor

A little while ago I was part of a discussion about big hairy refactoring efforts. You know, those somewhat common multi-month efforts to untangle a big ball of code, or rip out an old crufty system, or pay down a few years of technical debt. As the discussion went along, someone raised an interesting question:
Do you think that it is possible to drive these bigger technical endeavors…