The project leader is right. So are the senior leaders.

This is one of the most common tensions in any organisation running a significant program. And it rarely gets resolved well, because both sides are arguing from a legitimate position.

What the project leader needs

The project leader knows what they need. Clarity of scope. Stability of funding. Decision-makers who stay engaged but don't second-guess the plan every quarter. There's a body of serious research that backs this up. Give a capable team a clear mandate and get out of their way.

What the senior leaders need

The senior leaders know what they need too. Confidence that the portfolio is still pointed in the right direction. Visibility over which programs are performing and which aren't. The ability to shift priorities when the world changes around them. Because it always does.

Noise and signal

The problem isn't that either side is wrong. It's that most organisations haven't built the structures that let both be right at the same time.

The project team needs protection from noise. The leadership team needs signal. Those are different things, and they require different mechanisms. When organisations don't distinguish between them, every reporting request feels like interference and every pushback feels like obstruction.

Getting that balance right, between the stability a project needs to deliver and the visibility leadership needs to govern, is one of the harder design problems in major program delivery. And it's one most organisations are still working out. The ones that get it right tend to have designed for it deliberately, rather than hoping goodwill on both sides would be enough.