Most of the teams I've worked on weren't stuck because somebody wrote bad code. They were stuck because something everybody trusted had gradually stopped being true: an estimate, a metric, a process that worked fine back when we were smaller. I've found I'm pretty good at noticing when that's happened, and that it goes down a lot better when I turn up with a replacement rather than just the bad news.
These days I work at the intersection of tech and finance. Before that I spent thirteen years at Airship, most of them leading engineering on Journeys, the part of the product marketers use to decide which messages their customers get and when. I worked alongside product and design to figure out what was worth building before we built it, and picked up a couple of patent filings along the way. Outside of work it's open source, which is where I get to try things out at a size where being wrong is cheap.