Scope and System of Interest
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.
Why your project keeps getting stuck - and what to do about it
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:
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
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.
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.
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.
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.