If the scope does not change, budget and time are not up for negotiation. Whoever gives up that line ends up without a plan. They have a wish list.
As an external you have to stay open and still plan for the unforeseen. Budget rounds have more of the bazaar than you would expect, and in some organizations you prepare better with buffers for the next round of cuts. Exactly such a moment came: economic crisis, tariffs, competition from the Far East, industry in a sour mood. The consequence was foreseeable. Cancel projects, trim the running ones.
I could give a little, on insistence a little more, around twenty percent from buffers and the reinterpretation of existing effort. Then it was over. That is part of it too: to say clearly that it will not work with less, and that whoever cuts further stops the program. That was accepted, with gritted teeth, because in this area I had the largest budget. My line for it: this budget is not large because we indulge ourselves, but because it is a complex undertaking with many partners.
What happens when you give in too far
Whoever gives in too far wrecks themselves. Under weak leadership everything lands in the team, under the motto „we will manage“. I have seen the consequence often: at first people are motivated, want to show what they can do, push past their limits. Then they notice that the fire does not let up. It grows. There is no one-time push-through with praise at the end. Over-performance is expected, not valued. After a few years the good ones leave, and the others withdraw.
Large corporate programs make this mistake too, often worse. They plan over-optimistically under real or perceived pressure from above, while the levels below, region and country, are not even at the table. At some point board, external consultant and headquarters agree, and the execution cannot possibly deliver it. The smart consultant therefore calculates across all levels, not only with headquarters. And a good program lead reacts to feedback, instead of waving it off with „the board approved it“.
Making the coupling tangible
For the board I make the iron triangle tangible with scenarios. Faster first means more resources, which carries a stretch, but not indefinitely. Beyond that limit I couple scope reduction to time savings, three or four examples that show how it all connects. That way I have so far come through every critical question, and the demand „this has to go faster“ came afterwards less often and more mildly.
Hold the line: more speed or less budget is available only through less scope. Whoever gives it up does not protect the budget. They shift the gap into the team, where it stays invisible until the good ones leave.