Scope creep is a decision-rights problem.

When a program bloats, the usual diagnosis is a discipline problem. The team was too accommodating, the change control process too loose, the requirements too soft. The prescribed cure is more rigor: tighter gates, stricter documentation, a more forceful project manager.

The rigor rarely holds, because scope creep is not fundamentally a discipline problem. It is a decision-rights problem. Scope expands because at the moment a new request arrives, no one in the room has the clear, uncontested authority to say no and make it stick.

How the expansion actually happens

Watch a request enter a program and you will see the mechanism. A senior stakeholder wants one more capability. The team knows it will cost time and money, but they do not have the standing to refuse a senior stakeholder, and it is not clear who does. The project manager can object but cannot decide. The sponsor is not in the room. So the request is absorbed, quietly, because absorbing it is the path of least resistance for everyone present.

Multiply that moment across a program and the budget is gone, not to one bad decision, but to a hundred small ones that no one was empowered to prevent. The team did not lack discipline. It lacked an owner of the tradeoff.

Every unmanaged addition is a decision that got made by default because no one had the authority to make it on purpose.

The tell: no one can name the decider

The diagnostic question is simple. For a given scope decision, who decides? Not who advises, who escalates, or who documents. Who actually holds the authority to approve or refuse, and does everyone in the program accept that they hold it?

In programs that creep, the answer is a shrug, or a committee, or a name followed by the word "but." A decision right that is shared among a committee is a decision right that belongs to no one, because a committee can defer and a committee can be lobbied. Clear decision rights are singular and known. When they are absent, scope is decided by whoever pushes hardest, and the people who push hardest are rarely optimizing for the program.

Governance is the fix, not process

More change-control paperwork does not solve this, because the paperwork still routes to the same undefined authority. What solves it is governance in the real sense: a clear map of which decisions belong to whom, at what threshold, with the sponsor owning the ones that trade scope against time and cost.

When the decision rights are explicit, the request that used to get absorbed now meets an owner. That owner can weigh it against the program's objectives and say no with authority, or say yes with eyes open and the budget adjusted to match. Either outcome is a decision made on purpose. The creep stops not because people became more disciplined but because someone was finally empowered to hold the line.

Why this sits inside the execution gap

Scope creep belongs to the same family as faltering sponsorship and unclear priorities. All of them are failures of the leadership system that turns intent into execution, and all of them show up as a distance between what was approved and what gets delivered. A program that was scoped to deliver a specific outcome ends up delivering something larger, later, and less focused, and the value case that justified it quietly erodes.

The organization then concludes that the estimate was wrong or the team underperformed. Usually neither is true. The scope was governed by default instead of by design, and default governance always expands to fill the available budget.

Fix the authority, not the accommodation

If your programs consistently deliver more than they promised and less than they intended, resist the urge to demand more discipline from the team. Ask instead who holds the authority to refuse a request, whether that authority is clear to everyone, and whether the person who holds it is actually in the room when requests arrive. Fix that, and the discipline takes care of itself.