In recent years, the term value has become increasingly popular in project and portfolio management. Boards demand value for money, executives seek value creation, and PMOs talk about value realisation. But somewhere along the way, we observe that the term value has started being used interchangeably with the term benefits. This raises an important question: are benefits management and value management the same thing? And if not, does the difference really matter?
The Rise of ‘Value’ in Organisational Language
We recently noted that one of our long-standing clients has almost completely stopped using the term benefits. The organisational language has now changed to ‘value’. The practices around documenting, tracking and realising benefits have not changed. Only the language has changed. This shift in terminology may seem minor. However, it reveals a deeper issue: confusing two related but distinct disciplines can lead to strategic misalignment. This prompted some research by our team into the terms that other customers are using. Broadly speaking, it seems that if the organisation is operating in an environment of traditional project management or even in a hybrid type of organisation the standard thinking and language around benefits still holds. In Agile or scaled Agile environments, it’s more likely value will be used. Sometimes as well as benefits and sometimes instead of.
What Is Benefits Management?
Benefits management is a well-established discipline that focuses on the identification, planning, realisation, and sustainment of specific benefits arising from a project or program. Benefits are measurable improvements resulting from change, such as reduced processing time, increased customer satisfaction, or improved staff capability. In frameworks like MSP (Managing Successful Programmes) and PMI’s PMBOK, benefits management is typically situated within the program or project domain. Its purpose is to ensure that investments deliver tangible outcomes aligned with business objectives. Benefits management not only supports delivery assurance, it also helps organisations justify investment, prioritise initiatives, and hold delivery to account over time.
Understanding Value Management
Value management, by contrast, is broader and more strategic. The Axelos MoV (Management of Value) guidance defines value as the optimal balance between benefits, costs, risks, and resources to meet stakeholder needs. Value management is not limited to realising predefined benefits. It involves actively questioning whether the right projects are being selected, whether they are delivering the right outcomes, and whether the approach taken is the most efficient and effective. Value is subjective and contextual, shaped by stakeholder perspectives and long-term goals. For example, a project delivering modest cost savings may be prioritised over a more expensive digital initiative if the latter aligns better with long-term customer expectations and public value.
Agile, SAFe and the Allure of ‘Value’
Where organisations have embraced more Agile ways of working, particularly SAFe, the term value often becomes all pervasive. Value is an important concept in SAFe. Indeed, the whole philosophy works around the fact that value delivery is continuous. The term value is built into the very fabric of the method. Still, what value actually means can be somewhat subjective. The intent in SAFe is that ‘flow of value’ is about speed, continuity, and transparency. It asks questions like:
- How long does it take to deliver something useful to the customer?
- Where are we getting stuck?
- Are we delivering frequently and reliably?
These are important metrics that can directly lead to an increase in delivery performance, but they do not directly relate to benefits management. In fact, SAFe doesn’t talk about benefits at all. The question is though, do organisations who deliver work using SAFe or other scaled Agile methods still need to worry about traditional benefits realisation? The answer would still seem to be yes, certainly if the leadership team want to assess if their delivered work represents the required value for money.
What is clear is that flow of value and benefits realisation are not the same thing. Flow-based metrics focus on how efficiently work is delivered, while benefits realisation focuses on why the work matters once delivered. Flow answers questions about delivery performance. Benefits answer questions about strategic effectiveness. Confusing the two risks measuring speed without questioning direction.
Why Benefits Realisation Still Matters in Agile Settings
This distinction is important because a team can have excellent flow but still deliver limited or even negative benefits if they are working on the wrong things. Conversely, a team may have slower flow but still deliver high-value outcomes if their work is well aligned to strategic goals. This is where benefits realisation remains crucial, particularly for leadership, finance, and governance functions trying to answer questions like:
- Did this investment deliver what we hoped it would?
- Have we achieved the outcomes we set out to?
- Is this still the best use of organisational resources?
In SAFe and other scaled agile frameworks, cost forecasting is typically handled by assigning stable budgets to long-lived value streams, rather than individual projects. These budgets are managed through lean governance models and are tied to team capacity and delivery cadence. In theory, this makes cost more predictable and aligned to flow. But without active benefits realisation practices, there is a risk that funding becomes decoupled from actual impact. Teams may be busy and delivering frequently, but not necessarily delivering the right outcomes. Without mechanisms to measure whether value is actually being realised, even the most efficient delivery teams can end up solving the wrong problems or continuing to invest in initiatives that no longer serve the business strategy.
Language Shapes Thinking, and Practice
So, while the language may be evolving in some contexts, the underlying need remains. Organisations still need to define what success looks like, articulate the outcomes they expect from their investments, and track whether those outcomes have been achieved, whatever the delivery method. If benefits realisation practices disappear entirely under the guise of ‘value delivery’, then organisations may lose sight of whether they are achieving value for money or just maintaining velocity.
Ultimately both disciplines serve important purposes. Benefits management provides the rigour needed to track and deliver intended improvements. Value management ensures that those improvements are worth pursuing in the first place. One is about doing things right. The other is about doing the right things.
Language shapes thinking. If we use the term value without the rigour of benefits management or the strategic lens of value management, the risk is that we dilute both.
