Why your project keeps getting stuck - and what to do about it

The difference between the work Scope and the System of Interest... and why confusing the two is one of the most common reasons complex projects derail.


You're mid-project. Decisions that seemed straightforward a month ago now require "escalation." Stakeholders from different parts of the business are pulling in different directions. Progress has slowed to a crawl — not because of a technical problem, but because no one can quite agree on who owns what.

Sound familiar? There's usually one root cause hiding beneath all of this: a poorly defined — or silently assumed — Scope.

"On simpler projects, Scope and System of Interest tend to coincide. On the hard ones — they rarely do. And that gap is where projects get stuck."

Three terms, three very different things

Most project professionals are comfortable with the word "scope." Fewer stop to distinguish it from two related but distinct concepts: System of Interest and Wider System of Interest. Using them interchangeably might feel harmless on a straightforward project — but on anything complex, that casual overlap quietly creates risk.

Scope

Your mandate

The formal boundary of your project — defined by remit, authority, and budget. Usually handed to you by the commissioning body.

System of Interest (SoI)

What actually needs to change

Everything that must be delivered, fixed, or materially changed to achieve the required outcomes. Agreed with stakeholders — not given.

Wider System of Interest (WSoI)

The surrounding context

Factors outside the SoI that shape it — constraints, dependencies, assumptions. Changes here are influencing factors, not project-stoppers.

The gap is the problem

On simpler, self-contained projects — delivering a new tool within a single team, for example — Scope and System of Interest are effectively the same thing. The organisation commissioning the work has authority over everything that needs to change. Easy.

But as soon as a project crosses organisational boundaries — whether that's departments, business units, or external partners — the picture changes. The SoI expands. The Scope, constrained by someone's budget and authority, often doesn't stretch as far.

That gap isn't just uncomfortable. It's a risk register item. Visualised simply:

Scope
Authority boundary
System of Interest
What needs to change
Wider SoI
Full context & constraints

The space between Scope and SoI is where risk lives. Everything in that gap needs active management.

When the gap appears, you have three options

1

Enlarge the scope. Negotiate for the authority, budget, or remit needed to cover the full System of Interest. Difficult, but sometimes achievable — especially early on.

2

Design around the gap. Architect the solution to insulate itself from — or compensate for — what sits outside your control. Clever engineering, but it requires knowing the gap exists in the first place.

3

Create cross-organisational agreements. Build formal (or at least explicit) commitments across the organisations that span the required scope. Slower, but often the most realistic path on complex programmes.

Scope isn't binary - think in three grades

One of the most useful mindset shifts for anyone managing a complex programme: scope isn't simply "in" or "out." It exists on a spectrum of control. Before you finalise your delivery approach, map where each element of your system sits:

⚙️ Control

You can mandate decisions and changes directly.

📡 Influence

You can persuade and shape — but not mandate.

🌬️ Respond

You can only react — no scope to direct changes here.

A team that is clear on where each element of their system sits within these tiers is a team that can have honest conversations about risk — rather than discovering problems mid-implementation when the cost of change is high.

The most important thing you can do early

Both Scope and System of Interest will shift during the discovery and design phases of any genuinely complex project. That's not a failure of planning — it's a feature of complexity. The danger comes from treating Scope as fixed too early, which leads to excluding things that later turn out to be essential.

What gives teams the best chance of navigating this well? A clear, compelling, shared answer to one question: why does this need to happen? When the "why" is understood and agreed — across organisations, not just within one — teams gain the credibility and momentum to work through the hard conversations about where the edges really are.

"Any team that can clearly establish the 'why' of their endeavour puts themselves in a good position. In business change terms, this is the burning platform — the reason everyone has to get in the same room."

Getting Scope and System of Interest right won't make a complex project easy. But it will ensure you're spending your energy on the real problems — not firefighting the ones that were always hiding in the gap.