https://www.amazon.com/Phoenix-Project-DevOps-Helping-Busine...
So no, I didn't jump. I had to be persuaded to take the job in the first place. Life is too short for bullshit. I delivered what I said I would, and when they didn't live up to their end of the bargain, they faced the consequences I told them they would when I was hired.
Resources as a leg also lines up with the observation from The Mythical Man-Month that adding resources to a late project makes it later. (I have experienced this directly.) So resources are rarely mutable to a significant degree; you have the team you have and the budget you have - and you really do not want to see what happens when you suddenly get an unlimited budget!
So I tend to phrase it as every project is either scope-bound or schedule-bound. One of those can flex - which one? If you can't flex either, you will probably fail.
Not surprisingly the hacked together new website (which went live months late and $100s of Ks over budget) was a train wreck. Unreliable and constantly causing errors/issues.
The first thing I did was said the only person that can talk to the development team is me. It took about 2 months to get all the software processes in place that were non-existent, to get the entire website working and stable, and to get our task/goal list under control.
The cocksucker owner comes to me and says "I want these 4 project you quoted that would take 6 months done in the next 3 months". So I quit (so did their lead developer that was doing 90% of the heavy lifting).
IT Management is a mess everywhere I've ever been, just to varying degrees. Maybe this is because most my career has been as a consultant or contractor, but it's really discouraging.