Monday, 9 March 2015

A benefits map shows the relationship between outputs, capabilities, outcomes, benefits and the objectives. i.e. Illustrates the sequential relationship between benefits. A benefits map is important because benefits do not typically happen in isolation, and there are cause-and-effect relationships between the elements. Failure to deliver a specific output or capability may appear to have a minor effect from the project perspective but have a massive impact on benefits realization. The map illustrates a total ‘picture’ of the changes, shows the inputs for each benefit and how they fit into this total picture. The benefits map should include any dependencies that are outside the boundary or control of the programme, as they may affect the realization of benefits. The benefits map can be created working from right to left, from corporate objectives to longer-term and short-term benefits. It should then define the project outputs and organizational changes required. Where the outputs are a given, for example in an emergent programme, the benefits map may need to be developed from both ends and joined in the middle. Benefit maps are excellent ways of providing a high-level view of what the programme must achieve, and should be considered for inclusion in the programme brief (prepared by the Senior Responsible Owner in Identifying a Programme Transformational Flow process).

Typical structure and composition of a Benefits Map in tabular format is as shown below. It is advisable to create a Map structure for better stakeholder engagement and for a clear line of sight.

Author - Vijayakumar Reddy, CTO & Lead Trainer, A2A IMTCS Pvt. LTD.

© Copyright 2015 A2A - IMTCS. All rights reserved.
The Swirl logo is a trade mark of AXELOS Limited.
ITIL® is a Registered Trade Mark of AXELOS Limited.
PRINCE2® is a Registered Trade Mark of AXELOS Limited.
MSP® is a Registered Trade Mark of AXELOS Limited.
Copyright © AXELOS Limited 2007, 2009 & 2011. Reproduced under license from AXELOS