Creating value from change

There is a steadily increasing focus within organisations on managing change and maximising the opportunities change is supposed to generate through realised benefits and value creation.  The question this post asks is ‘What are the responsibilities of the project manager when it comes to managing these changes?’

In part, the answer to this question depends on what aspect of the change you are dealing with. At one level, projects are initiated to instigate change. When the project is complete there is a new ‘product, service or result’ created, which means things are different – there is a change in the environment affecting the way at least some people behave and work. This may be a new building for people to make use of, a new or upgraded road to travel on, a new process to assist in the accomplishing of a business process or an improved software application, to name a few. But these things are only artefacts the change that matters is in the behaviour of people and the way they choose to use the artefact or ignore it.

One way to consider the role of the project manager in change is to look at a Formula 1 racing team. The engineers and mechanics can engineer a ‘winning improvement’ in the car’s design, but they cannot win a F1 race on their own! The improved car needs all of the other people in the team, including the driver, to add their contribution to achieve success. But it does not matter how good the driver is, if he does not have a great car, he will not win. The project team’s role in creating success is very closely aligned to the ‘engineers and mechanics’ if we don’t do a great job, the probability of team success is reduced or eliminated!

In the world of projects and programs, ‘success’ is defined by creating the value the project (or program) was initiated to deliver. However, for the organisation’s investment in the project to realise its intended value, the output from the project needs to meet a need within the wider stakeholder community, and the people in that community need to be willing to buy, or make use of the product once it has been delivered.  Achieving this aspect of change is primarily the responsibility of the organisation, not the project manager.

The first aspect of this area of organisational responsibility is choosing the ‘right project to do’ and making sure there is a project sponsor[1] willing to champion the work. Defining the need that the project will be initiated to fulfil occurs before the project starts, and is largely the responsibility of the ‘performing organisation’ or the ‘customer’ and uses skills such as market research and business analysis to define what is required and to develop a viable business case[2]. The project starts once the business case is accepted, funded and the project manager appointed. There may still be work to do to refine the business case or define requirements but the project’s objectives are pre-set.

The only responsibility of project managers at this stage of the overall project lifecycle is to make sure they understand exactly what it is they are being asked to deliver and to highlight any omissions or issues to the sponsor.

The second aspect of this area of organisational responsibility is traditional change management, which involves preparing the affected stakeholders for the new ‘thing’, hopefully creating a desire to use it once delivered and supporting the transition from the ‘old way’ of working to the ‘new way’ so the intended benefits can be realised. Organisational change management[3] is a separate skill from project management.  The change manager may be part of an overall program of work, or may work for the sponsor. It is very unusual to see either the project manager working for a change manager or a change manager working for a project manager – the two disciplines have very different focuses and require very different skill sets.

But neither the project manger (PM), nor the change manager (CM), or the emerging role of ‘benefits manager’ can realistically have direct responsibility for the realisation of benefits; they do not have management authority over the people who will need to change behaviour to maximise the return from using the projects outputs. They each have a crucial (but different) role in proactively engaging with stakeholders to create the situation where the benefits can be realised, but the ultimate responsibility for realising benefits rests with the organisations operational or functional management.

The emerging role of a benefits manager[4] is largely advisory (and often incorporated within PMOs or ‘portfolio management’), and in many respects is similar to the PM and CM, the benefits manager supports the organisation’s ability to realise value. The role:

• Starts with the development of a benefits map for the project (typically as part of the business case),
• Provides advice during the implementation phase of the work to ensure project decisions do not unnecessarily compromise value by removing or preventing the realisation of benefits
• And continues after the project has delivered its outputs to measure the actual realisation of benefits achieved by the organisation’s management.

With, or without, the advice of a benefits manager, if the organisation is going to realise the maximum benefits from its investment in the project, the change manager and project manager need to be highly supportive of each other’s work and in combination put in place the capabilities needed to allow the organisation’s operational managers to realise value.  Some of the ways project management can facilitate the successful realisation of value, and support the change manger, include recognising:

• Most project stakeholders will be affected by the change and very often the project needs direct input from ‘end users’ and others to design its ‘outputs’.
• Project communications are communications to stakeholders and need to support the change management effort. Project communication will often pre-date change management communication and need to lay the foundations for the overall change initiative.
• It is a key responsibility of the project manager throughout the life of the project to be aware of the needs of the change manager (the change manager is a key stakeholder in the project) and adapt the work of the project (eg its communication strategy) to maximise the opportunity to realise benefits, where it is sensible to do so.
• It is very common for stakeholders to identify necessary or desirable changes in the product being produced during the course of the project. The project’s change management processes need to recognise the input from these stakeholders and manage them respectfully, with a view to maximising benefits (see below).

In summary, both the PM and the CM need to be aware of the needs and requirements of the other and work collaboratively to achieve the best overall outcome for the organisation, supported by the benefits manager (if one is in place) and coordinated by the sponsor[5].

Managing Project Change:

Organisational change, and change management benefit from the active support of the project manager, but are largely outside of the project managers direct responsibilities. Project change control is all together different. Whilst the project manager typically does not have the authority to approve most changes, managing the overall project change control process is the direct responsibility of the project manager.

Change control and its associated sub-disciplines such as configuration management form a core element of successful project management. The project manager, supported by the project team, is responsible for:

1. Identifying a change is required, requested or has already occurred (or is occurring).
2. Scoping the change and understanding its effect on project objectives
3. Preparing recommendations regarding the change
4. Identifying the appropriate person with authority to approve the change; this may be the project manager for internal changes, for all other changes it is usually either the sponsor, a change control board, the customer or the designated customer’s representative (eg, a superintending engineer).
5. Cooperating with and supporting the change authority in its decision making.
6. Managing the consequences of the change by implementing approved changes and ensuring rejected changes are not implemented.

The connection between overall organisational change management and project change control is that every change that is managed through the project’s change control processes affects some aspect of the project’s outputs and should be considered from the perspective the ultimate use of the projects deliverables, its stakeholder’s needs and the overall realisation of benefits through the organisation’s change management processes.

Conclusion

Managing the overall project life cycle from idea creation and project selection through to benefits realisation and value creation is increasingly being referred to as ‘the management of projects’ and is an organisational capability. The difficult bit in the middle focused on creating the project deliverables is ‘project management’. To successfully implement a change, both the overall ‘management of projects’ and the work of ‘project management’ need to be synchronised if the maximum value is to be realised by the organisation.

Doing the wrong project right or the right projects badly helps no-one. Realising value from an organisation’s investment in its projects requires the right projects to be done right, and then making sure the outputs are actually used to create value – this is a team effort that spans all aspects of project and organisational management.

[1] For more on sponsorship see:   http://www.mosaicprojects.com.au/WhitePapers/WP1031_Project_Sponsorship.pdf

[2] For more on developing a business case see:
http://www.mosaicprojects.com.au/WhitePapers/WP1018_Business_Case.pdf

[3] For more on organisational change management see:
http://www.mosaicprojects.com.au/WhitePapers/WP1078_Change_Management.pdf

[4] For more on the different roles associated with realising benefits see:
https://mosaicprojects.wordpress.com/2012/11/03/who-manages-benefits/

[5] For more on the responsibilities of a sponsor see:
http://www.mosaicprojects.com.au/WhitePapers/WP1031_Project_Sponsorship.pdf