Recent from talks
Nothing was collected or created yet.
Benefits realisation management
View on WikipediaBenefits realization management (BRM), also benefits management, benefits realisation or project benefits management, is a project management methodology, often visual, addressing how time and resources are invested into making desirable changes. BRM is used to manage the investment by organizations in procurement, projects, programmes and portfolios, and has been shown to increase project success across different countries and industries.[1][a]
The popularity of BRM began in 1995 in the UK, when Scottish Widows created a Benefits Realisation Management method[3] as part of its Project Management Handbook , (then titled Benefits Realisation), and rolled its use out across the entire firm. It grew in the UK with the inclusion of BRM by the UK Government in their standardized approach to programmes, Managing Successful Programmes (MSP).[4]
Definitions
[edit]Benefits realization management has four main definitions.[citation needed]
The first definition is to consider benefits management as an organisational change process. It is defined as "the process of organizing and managing, such that the potential benefits arising from the use of IT are actually realized".[5]
The second definition perceives it as a process. Benefits management is defined by the Association for Project Management (APM) as the identification, definition, planning, tracking and realization of business benefits.[6]
The third definition is to apply this concept on project management level. Project benefits management is defined as "the initiating, planning, organizing, executing, controlling, transitioning and supporting of change in the organisation and its consequences as incurred by project management mechanisms to realize predefined project benefits".[7]
Finally, benefits realization management is perceived as a set of processes structured to "close the gap" between strategy planning and execution by ensuring the implementation of the most valuable initiatives.[1]
Process
[edit]| BRM process[8] |
|
BRM practices aim to ensure the alignment between project outcomes and business strategies:
"If value is to be created and sustained, benefits need to be actively managed through the whole investment lifecycle. From describing and selecting the investment, through programme scoping and design, delivery of the programme to create the capability and execution of the business changes required to utilise that capability, and the operation and eventual retirement of the resulting assets. Unfortunately, this is rarely the case."
Under BRM, outcomes are changes identified as important by stakeholders and can be strategic or non-strategic. A benefit is a measurable positive impact of change. A dis-benefit is a measurable negative impact of change.[8] Successful BRM requires accountable people, relevant measures and proactive management.
As with all project management methodologies, BRM has clear roles and responsibilities, processes, principles and deliverables. The main roles are Business Change Managers (BCMs) who help the Benefits Owners (i.e. the main beneficiaries) identify, plan and review the expected benefits from the change and project managers who deliver the reliable capability on time and within budget.[10] A generic BRM process is then as aside.
To identify the investment outcomes, pictorial views of the outcomes of interest on an outcome map (also called a results chain,[8] benefits dependency network[11] or benefit map[12]) can be created. See next section. This technique supports agreement of the outcomes sought as it shows the outcomes and relationships between them on a single page. They can be agreed upon and communicated clearly as a result.
Data can then be captured either separately or within a suitable modelling tool for each outcome that will include the benefit measures used for each, ownership and accountability information and information to support realisation management.
Benefit mapping
[edit]This section needs additional citations for verification. (June 2023) |
Constructing benefits maps or graphs is usually done from right to left, with what is attempting to be achieved (often called objectives, strategic outcomes etc.) being the start point, then moving through intermediate outcomes to the things required to cause these to happen at the very left.
Benefits dependency networks
[edit]
The benefits dependency network (BDN) has five types of object within maps.
- Investment objectives: A small number of statements that define the focus of the project and how it links to investment drivers.
- Benefits: Advantages to specific individuals or groups of individuals.
- Business changes: Changes required in the business to hit the Benefits.
- Enabling changes: Changes required to allow the business changes to happen.
- IS/IT enablers: "The information systems and technology required to support the realization of identified benefits and allow the necessary changes to be undertaken."[11]
Benefits dependency map
[edit]
The benefits dependency map (BDM) also has five types of object on the maps
- Bounding objective: Measurable end goals which support the vision of what is being attempted.
- End benefit: Independent benefits (not interlinked) that achieve the objective.
- Intermediate benefit: "An outcome of change which is perceived as positive by a stakeholder".[12]
- Business change: Changes to the business or environment of the business.
- Enabler: Something developed / purchased to enable the realisation of benefit.
Results chain
[edit]
The results chain has four types of object on the maps.[8]
- Outcome: The results being aimed at.
- Initiative: An action or activity that contributes to outcomes.
- Contribution: A measurable description of how an initiative is expected to contribute to an outcome.
- Assumption: Something believed to be required to realize outcomes or initiatives which the organisation has no or little control over.
See also
[edit]Notes
[edit]- ^ Although the Project Management Institute (PMI) identified that only one in five organizations report high maturity in benefits realization.[2]
References
[edit]- ^ a b Serra, C. E. M.; Kunc, M. (2014). "Benefits Realisation Management and its influence on project success and on the execution of business strategies". International Journal of Project Management. 33 (1): 53–66. doi:10.1016/j.ijproman.2014.03.011.
- ^ Project Management Institute, Pulse of the Profession, PMI, Newtown Square, PA, 2014. http://www.pmi.org/Learning/Pulse.aspx
- ^ Love, Gordon; Luxon, Charles (1995). "Benefits Realisation". Scottish Widows Project Management Handbook.
- ^ OGC (2003) Managing Successful Programmes, London, The Stationery Office.
- ^ Ward, John; Elvin, Roger (1999). "A new framework for managing IT-enabled business change". Information Systems Journal. 9 (3): 197–221. doi:10.1046/j.1365-2575.1999.00059.x. S2CID 36031754.
- ^ "What is benefits management? | Association for Project Management". Archived from the original on 2016-03-15. Retrieved 2016-03-14.
- ^ Badewi, Amgad (2016). "The impact of project management (PM) and benefits management (BM) practices on project success: Towards developing a project benefits governance framework". International Journal of Project Management. 34 (4): 761–778. doi:10.1016/j.ijproman.2015.05.005.
- ^ a b c d Thorp, J. (1998) The Information Paradox – realizing the business benefits of information technology, Toronto, Canada, McGraw-Hill.
- ^ APM Winning Hearts Brochure (PDF). Association for Project Management - Benefits Management Special Interest Group. 2011. p. 3.[permanent dead link]
- ^ Badewi, Amgad; Shehab, Essam (2016). "The impact of organizational project benefits management governance on ERP project success: Neo-institutional theory perspective". International Journal of Project Management. 34 (3): 412–428. doi:10.1016/j.ijproman.2015.12.002.
- ^ a b Ward, J. and Murray, P. (1997), Benefits Management: Best Practice Guidelines. Cranfield School of Management, Information Systems Research
- ^ a b Bradley, G. (2006), Benefit Realisation Management – A practical guide to achieving benefits through change, Gower, Hampshire.
Benefits realisation management
View on GrokipediaFundamentals
Definition
Benefits realisation management (BRM) is a collective set of processes and practices for identifying benefits, aligning them with formal strategy, ensuring their realization during and after project implementation, and sustaining them post-completion.[1] It originated in the early 1990s as a response to the frequent failures of IT projects to deliver expected value, but has since expanded to address broader organizational change initiatives.[4] Central to BRM is the concept of benefits, defined as measurable improvements resulting from an outcome and perceived as an advantage by one or more stakeholders, which contribute to organizational objectives.[5] These can be financial, such as cost savings, or non-financial, like enhanced customer satisfaction, provided they are quantifiable. In contrast, disbenefits represent measurable declines resulting from an outcome perceived as negative by stakeholders, such as increased operational complexity, and require proactive management to mitigate.[5] Outcomes refer to the results of change that affect real-world behavior or circumstances, such as improved decision-making processes, while outputs are the tangible or intangible deliverables produced by projects, like software systems or reports, which enable but do not guarantee outcomes or benefits.[5] BRM applies across project, program, and portfolio levels to ensure initiatives deliver sustained value aligned with strategic goals, extending beyond its IT origins to encompass diverse sectors like healthcare and infrastructure.[6][4]Importance
Benefits realisation management (BRM) plays a pivotal role in bridging the gap between organizational strategy and execution, ensuring that projects and programs deliver tangible value rather than merely completing outputs. By systematically identifying, tracking, and optimizing benefits throughout the project lifecycle and beyond, BRM addresses a common shortfall where many initiatives fail to achieve their intended outcomes; for example, only 17% of organizations reported high BRM maturity as of 2016, leading to inefficiencies in value delivery.[7] This structured approach aligns investments with strategic objectives, preventing the dissipation of potential gains and enabling organizations to realize up to 50% more projects that meet original goals and business intent compared to those with low maturity as of 2016.[7] For organizations, BRM delivers multifaceted benefits, including enhanced return on investment (ROI), improved resource allocation, and effective risk mitigation for potential disbenefits. High-maturity BRM practices result in 69% more projects meeting or exceeding forecasted ROI as of 2016, as resources are directed toward high-value activities rather than isolated project deliverables.[7] Additionally, by incorporating risk management and change control into benefit tracking, BRM minimizes threats to sustained value, including negative impacts or disbenefits that could undermine strategic gains.[1] This leads to better financial performance, with mature organizations wasting US$112 million less per US$1 billion invested due to poor project outcomes as of 2016.[7] Ultimately, these outcomes foster sustained competitive advantage through measurable, long-term improvements in efficiency and market positioning. Unlike traditional project management, which emphasizes on-time, on-budget, and on-scope delivery, BRM extends focus to post-project value realization, ensuring benefits are not only planned but actively sustained to drive organizational success.[8] Studies confirm that organizations employing mature BRM processes achieve higher overall project success rates, with benefits realization serving as a key differentiator in strategic alignment and performance.[7]Historical Development
Origins
Benefits realisation management (BRM) emerged in the early 1990s within the information systems and technology (IS/IT) sector, primarily as a response to the persistent underperformance of IT projects in delivering sustained business value. At the time, IT initiatives frequently succeeded in producing technical outputs—such as software systems or infrastructure—but failed to translate these into long-term organizational benefits, prompting the development of structured approaches to track and optimize value post-implementation.[4][3] This evolution was driven by the recognition of alarmingly high IT project failure rates during the decade, with studies indicating that approximately 70% of such projects did not meet their intended objectives, often due to inadequate monitoring beyond project delivery phases. Influential reports, including the 1994 CHAOS Report by the Standish Group, highlighted that only 16.2% of IT projects were fully successful in terms of time, budget, and functionality, while 31.1% were outright failures and the remainder were challenged, underscoring the gap between project completion and benefit achievement. These shortcomings revealed the limitations of traditional project management, which focused on outputs rather than outcomes, necessitating BRM to bridge this divide.[9][10] Early BRM practices drew from established disciplines in finance and public sector management, particularly investment appraisal techniques and program management methodologies. Concepts like cost-benefit analysis, long used to evaluate the economic viability of investments, provided a foundational framework for quantifying and measuring benefits against costs in IT contexts. Additionally, program management practices from the finance sector and public administration influenced BRM by emphasizing the orchestration of multiple projects to achieve broader strategic outcomes, evolving ad-hoc tracking into more systematic benefit realization processes.[3]Key Frameworks
One of the earliest formalized frameworks for benefits realisation management emerged from the Cranfield School of Management in the 1990s, known as the Cranfield Benefits Management Framework. Developed by John Ward and colleagues, this model emphasizes a structured process for identifying and structuring potential benefits from IT investments, assigning stakeholder ownership to ensure accountability, and creating detailed realization plans that link changes to measurable outcomes.[11] The framework's four key stages—benefits identification, benefits planning, benefits execution, and benefits evaluation—highlight the importance of ongoing review to adapt to changing business contexts, drawing from empirical studies of UK organizations.[12] In 2018, the Project Management Institute (PMI) introduced its Benefits Realization Management Framework as part of a dedicated practice guide, providing a comprehensive approach tailored to portfolio, program, and project management. This framework organizes activities into three primary stages: identify benefits (aligning with organizational strategy), execute and deliver (using tools like the Benefits Register to track progress and the Benefits Roadmap to sequence realization), and sustain benefits (monitoring post-delivery to ensure long-term value).[13] Core principles include strategic alignment, where benefits must support broader objectives, and measurability, requiring quantifiable metrics from the outset to enable evidence-based adjustments.[1] The UK Office of Government Commerce (OGC) integrated benefits realisation into its methodologies during the early 2000s, particularly through Managing Successful Programmes (MSP) and PRINCE2. In MSP, benefits management focuses on creating detailed benefits profiles that outline expected outcomes, ownership, and measurement criteria, alongside regular realization reviews to assess progress against baselines during and after program delivery. This approach ensures benefits are embedded in program governance, with PRINCE2 complementing it by incorporating benefits considerations into project initiation and closure stages.[14] Subsequent developments have further standardized BRM through international and professional bodies. The ISO 21500:2021 standard on project, programme and portfolio management — context and concepts explicitly addresses benefits realisation, assigning it as an organizational responsibility that extends beyond project delivery to leverage outputs for sustained value, influencing global practices in public and private sectors.[15] Similarly, the Association for Project Management (APM) Body of Knowledge, updated in its 8th edition (2025), positions BRM as a core competency, integrating it with governance and stakeholder management to emphasize identification, planning, and tracking of benefits across project lifecycles. The 2025 edition continues to highlight BRM's role in enhancing project success through value delivery.| Framework | Key Stages | Primary Tools/Elements | Emphasis |
|---|---|---|---|
| Cranfield (1990s) | Identification, planning, execution, evaluation | Stakeholder ownership assignments, benefits maps | Benefits identification and adaptive planning for IT investments[11] |
| PMI (2018) | Identify, execute/deliver, sustain | Benefits Register, Roadmap | Strategic alignment and post-delivery measurability[13] |
| OGC/MSP (2000s) | Profile creation, delivery, review | Benefits profiles, realization plans | Program governance and ongoing reviews |
| ISO 21500 (2021) | Planning, delivery, organizational realization | Integration with project processes | Organizational accountability beyond projects[15] |
| APM BoK (2020s) | Identification, planning, tracking, realization | Governance linkages, metrics tracking | Core integration with project success factors |
