Projects are not the point: Why benefits-led thinking matters

Many projects meet their milestones, control their costs and produce the outputs they promised. But a few months later we ask: so what actually changed?

This isn’t unique to [insert your favourite commercial sector here]. It’s familiar across public and private sectors alike. Was it weak execution, poor planning, or insufficient capability? Usually it’s a deeper issue: not how projects are delivered, but why they exist in the first place.

The most dangerous assumption in project management

One of the most persistent – and damaging – assumptions in project environments is that the project itself is the primary unit of success.

When this assumption takes hold, attention naturally gravitates towards:

completing the scope
meeting the schedule and budget
closing the project cleanly

These things matter, but they are not the point. Projects are temporary. Organisations, services, alliances and nations are not. Treating the project as an end in itself is such a short-sighted perspective that it has earned itself a benefits management “deadly sin” category – a mindset that almost guarantees disappointment.

Projects as interventions in a wider system

Every project sits within a wider system:

an organisation and its operations
a network of partners or suppliers
or, in the public sector, a whole national system of policy, regulation and service delivery

Projects do not create value directly. Value only arises when people use what the project produces – when behaviours change, processes adapt and decisions are made differently. Those changes usually occur after the project has delivered its outputs, often long after the project team has disbanded. There are outputs delivered during project delivery which can start to generate benefits (low-hanging fruit, quick wins), and a lot of my work is about the impact that “confidence” can have, but in general benefits don’t even start until the project has handed over its outputs and closed.

Which brings us to systems thinking. Understanding the wider context is not an optional extra for project professionals. It is essential to make the right decisions to optimise the benefits.

A project that is perfectly delivered but poorly absorbed by the system is not a success; it is a missed opportunity.

Activity-led versus benefits-led projects

Some of the most successful projects managers we know are outputs-led. That is, they are focused on what the project has been told to deliver. However, there are projects which are process-led (“if we’re following the process, then we’re doing a good job”), and even more basic than this, there’s activity-led (“if we’re busy, that means we’re doing the project”). I’ve certainly joined projects, even worked in organisations, where these are the predominant approaches. Progress is measured in tasks completed or hours worked. Governance focuses on delivery assurance.

Projects can be outcomes-led, where the project leadership team understands that they need to go beyond deliverables and create a change. But even that change might no longer be appropriate. That’s where we go further.

A benefits-led perspective asks a different set of questions:

What problem is this project trying to address?
What outcomes must change for that problem to be reduced?
Who needs to do something differently once the project finishes?
How will we know whether the intended benefits have actually materialised?

This shift in thinking reframes good project management – it doesn’t replace it. Delivery discipline remains vital but aligned to a larger goal: helping the organisation succeed.

Shared responsibility across roles

Benefits-led thinking does not belong to a single role.

Project managers do not “own” benefits realisation, but we have enormous influence. Choices about scope, design, sequencing, communications and engagement all affect how usable the outputs will be, and how likely to be adopted.
Sponsors and Senior Responsible Owners are accountable for ensuring that the project remains aligned to the organisational need it was set up to address – not just that it is well governed.
Benefits managers (where formally appointed) maintain clarity about why the project exists and what success really looks like beyond delivery.
Benefit owners are the representative of the business and should directly ensure that the changes in processes and behaviours happen so that benefits are realised.

When benefits thinking is treated as someone else’s problem, it usually becomes nobody’s priority.

Keeping sight of purpose

The greatest risk to benefits realisation is not at the start of a project, but during delivery.

As projects progress:

delivery pressures mount
compromises are made
scope is adjusted
and attention narrows to what is immediately controllable

Without an explicit benefits focus, it is easy for the original purpose to fade into the background.

Benefits management is even more important at transition points: implementation, handover, and the move into business-as-usual. Many benefits are lost not because projects fail, but because nobody actively stewards the change.

Maturity means knowing when a project is no longer the answer

Perhaps the hardest implication of and benefits-led thinking with a systems thinking focus is this: sometimes the right decision is to stop, pause, or reshape a project.

If the underlying problem or opportunity changes or disappears, throwing good money after bad (keeping “in flight” projects because they’re in flight) is not good governance. It’s value erosion – the resource could be better deployed in a different way, and spreading the resource too thinly is a recipe for activity-led work which loses its focus.

This requires confidence and good leadership. It also means moving away from a culture where projects are judged solely on delivery performance rather than on the value they enable.

A shift in mindset, not a new methodology

Benefits-led project management is not about adding more paperwork or inventing new processes. It is about changing the mental model.

Projects are means, not ends. They exist to serve the system they sit within – the organisation, the alliance, or the nation. When project professionals consistently hold that perspective, delivery improves, decisions become clearer, and the likelihood of real, lasting benefit increases.

In the end, successful project management is not about doing more projects well. It is about doing the right projects, for the right reasons, and never losing sight of why they exist.