View source for The Role of Program Management in an Organisational Change

'''Written by Sebbe Sidenius Bull (2018)'''

'''Revised by Cirkeline Bräuner (2023)'''

''This article builds upon an existing piece of work, utilising its structure as a framework to present a new, more comprehensive analysis of the subject matter. In addition to all content being new, the article is brought to a higher level by creating a clear thread, using recently published references and redesigning the visuals.''

== Abstract ==
Organisations in today's rapidly changing society face constant changes due to evolving market conditions, shifting customer demands and emerging technology, to mention a few examples. To remain competitive, organisations must adapt through process optimisation, cost reduction and technology adoption, among other changes that affect the entire business. Therefore, successful management of these changes is crucial for organisational success <ref>''https://www.prosci.com/change-management'' ''Change Management'', last visited 03-03-2023</ref>.

'''Organisational change''' is a huge alteration for any organisation and can be a daunting task if not managed properly. In the context of '''project management''', it refers to any significant alteration in an organisation that affects the way projects are planned, executed and managed. Managers must be able to identify the potential impact of changes in their projects and adapt their project management approach accordingly to ensure successful project delivery <ref name=hayes/><ref>PMBOK (2017). ''A Guide to the Project Management Body of Knowledge Sixth Edition'', Project Management Institute, United States</ref>.

In this regard, '''program management''' can serve as an effective tool for managing organisational change. With its comprehensive toolbox of evaluative methods, program management offers a structured approach to assess each potential change project. This toolbox supports managers in providing an overview of the change project, ensuring efficient project execution, promoting project alignment, evaluating risks, mapping stakeholders and identifying potential benefits. All of these elements work together to facilitate a more efficient and effective '''change management''' process <ref>''https://www.prosci.com/blog/change-management-and-project-management-comparison'' ''Change Management and Project Management: A Side-By-Side Comparison', last visited 06-03-2023</ref>.

This article provides a comprehensive introduction to change management, encompassing its definition, diverse examples and the fundamental models proposed by Kurt Lewin and John Hayes. In addition, the four core perspectives of this course - '''purpose''', '''people''', '''complexity''' and '''uncertainty''' - are used to describe the difficulties and challenges of going through an organisational change. Afterwards, an introduction to program management is given. Then, the two management fields are combined into one common understand of how program management can be applied in organisational change. Lastly, the limitations and benefits of organisational changes using program management are discussed.

Summarised, this article seeks to provide the reader with a comprehensive understanding of how program management can be used to successfully manage organisational change in today's continuously evolving business environment.

= Change management =
Change management is an approach of transitioning individuals, groups, teams or organisations from one state to another state. This article considers this management field from the point of view of organisations. To understand what change management is, it is necessary to understand what a change is. This definition will be further elaborated in the section below.

== What is change? ==

Change is a fundamental part of life and business. It refers to any modification, alteration or transformation in something from its previous state to a new state. Changes can be temporary or permanent, positive or negative and gradual or sudden. They can be a source of growth and development, as well as a source of challenges and difficulties <ref>''https://www.igi-global.com/dictionary/chaos-and-complexity-approach-in-management/3646'' ''What is Change'', last visited 06-03-2023</ref>. 

Changes are defined as either '''incremental''' or '''radical'''. Incremental change involves making small adjustments of an already existing system to improve efficiency, effectiveness and performance, such as refining an organisation's strategy. Radical change, on the other hand, involves making a significant change, such as introducing a completely new business strategy <ref>''https://www.oxfordlearnersdictionaries.com/definition/english/change_2'' ''Definition of Change'', last visited 02-03-2023</ref>. 

Both types of changes can be beneficial for different purposes and choosing the right approach depends on the context. For instance, incremental change may be more suitable for organisations looking to make small, steady improvements over time, while radical change may be more appropriate for organisations facing a crisis or significant external pressure to adapt <ref>Hodges, J (2016), ''Managing and Leading People Through Organisational Change'', Kogan Page, England</ref>.

== What is change management? ==

In the section above, the definition of a change was briefly described. This leads to the next topic, which deals with what a change is seen from a management point of view.

A simple way to describe change management is by using an example. An example of a company which went through a radical organisational change in response to the COVID-19 pandemic is the Danish jewellery brand Pandora. The company recognised the need to adapt to changing customer behaviour and preferences through new technology adoption. The need for the change arose as more customers were shopping online during the pandemic. As a result, the company introduced a video chat to enable that socially distanced customers could chat online with staff members. Other new digital features included the possibility to try on jewellery through virtual simulation and allowing customers to buy products online and collect them in physical stores <ref>''https://d3.harvard.edu/platform-digit/submission/how-pandora-the-jewelry-retailer-managed-to-win-during-the-pandemic/'' ''How Pandora, the Jewelry Retailer, Managed to “Win” During the Pandemic'', last visited 03-03-2023</ref>.

Although Pandora went through a successful organisational change process, there is unfortunately not a single recipe for applying change management in organisations, as there is no one-size-fits-all approach. The process has to be tailored to the specific needs and circumstances of the organisation. 

However, back in 1951 the psychologist Kurt Lewin represented a simplified way of viewing a change process. This process is illustrated in Figure 1 and is divided into three distinct stagers; '''freeze''', '''change''' and '''refreeze''' <ref name=hayes>Hayes, J (2010). ''The Theory and Practice of Change Management'', Palgrave Macmillan, New York</ref>. 

[[File:kurt_lewis.png|380px|thumb|'''Figure 1''': Lewin's three step change management process (created by Cirkeline, inspired by <ref>''https://expertprogrammanagement.com/2021/09/unfreeze-change-refreeze/'' ''Unfreeze, Change, Refreeze'', last visited 02-03-2023</ref>)]]

=== Unfreeze ===

The first stage of the change management process characterises the starting point, where the organisation prepares for the change. This involves creating awareness about the need for the change, identifying current behaviours and to get people to let go of their old ways of thinking and working <ref>Kotter J. P (1996). ''Leading Change'', Harvard Business School Press, Boston</ref>.

=== Change ===

The second stage involves implementing the change through planning, communication and execution. The objective is to create new ways of thinking and working. During this phase, people must be trained and educated to adopt new methods and behaviours and to overcome any obstacles that may arise <ref name=hayes />.

=== Refreeze ===

The third and last stage addresses making the change permanent. The objective is to reinforce the new behaviours, ensuring that they become a part of the organisation's culture. During this phase, the focus is on stabilising the new ways of thinking and working and creating a sense of ownership among people <ref name=hayes />.

== What are the steps in an organisational change process? ==

[[File:hayes.png|260px|thumb|'''Figure 2''': Hayes' five step change management process (created by Cirkeline Bräuner, inspired by <ref name=hayes/><ref>''http://unchange.pbworks.com/w/page/26958422/Generic%20Process%20Model%20of%20Change'' ''Generic Process Model of Change'', last visited 03-03-2023</ref>)]]

As mentioned above the change management process does not follow a specific recipe, and different models such as Lewin's model can be used to describe the process. However, the author John Hayes proposed another model for change management in his book ''The Theory and Practice of Change Management'' from 1998 <ref name=hayes />. Opposite Lewin's model, this model is presented as a more iterative process emphasising, that change management is a process with each stage informing and building on the previous stage. Moreover, this model does also include the people perspective, and it is more detailed, as it contains more clearly defined stages.

As can be seen in Figure 2, the model is divided into five stages; '''recognising and starting''', '''diagnosing''', '''planning''', '''implementing''' and '''sustaining'''.

=== Recognising and starting ===

The first stage corresponds to the unfreeze stage in Lewin's model. It involves recognising the need for change and acknowledging the specific challenges that drive the need for change within the organisation.

=== Diagnosing ===

The next stage covers diagnosing what needs to be changed and formulating a vision for the desired future state. 

=== Planning ===

Once the diagnosis is complete, the organisation develops an appropriate plan for implementing the change. This plan should consider various factors, including resource allocation, budget estimation, timelines and potential risks.

=== Implementing ===

After the change has been planned, the organisation starts implementing it in its operations.

=== Sustaining ===

During the last stage, the change is sustained and reviewed ensuring that it is fully integrated in the organisation. 

In addition to the five phases, the model does also include reviews and managing people issues during all five phases. The involvement of the people perspective in this model highlights the importance of people in an organisational change process. People are a critical component of organisational change processes, as they are the ones who must ultimately implement and adopt the change <ref name=hayes />.

== Why is organisational change a difficult task? ==
To better understand and visualise the challenges of managing organisational change, the topic is examined from the point of view of the four core perspectives introduced in the course; purpose, people, complexity and uncertainty <ref name=perspectives>''https://www.doing-projects.org/perspectives'' ''Project Management Perspectives'', last visited 02-03-2023</ref>. Each of these perspectives presents unique challenges to change management, which are briefly described below. Figure 3 illustrates the four perspectives, with a central question describing the core of each perspective.

[[File:perspectives.png|380px|thumb|'''Figure 3''': The four perspectives of project management (created by Cirkeline Bräuner, inspired by <ref name=perspectives/>)]]

=== Purpose: ''Why are we doing it?'' ===

Defining the purpose of the change can be a difficult task, as it requires careful consideration of the organisation's current state, its desired future state and the potential benefits and risks of the change. It is important to involve key stakeholders in this process to ensure that their perspectives and concerns are taken into account. Clear communication of the purpose is also critical to ensure that employees and other stakeholders who may be affected by the change are working towards the same goals and objectives.

=== People: ''Who is doing it and for whom?'' ===

It is human to make mistakes, and as change processes are driven by people, mistakes are also likely to occur. However, people are a necessity to create awareness of the need for the change in the first place. Furthermore, it is also people who are affected by the change. Therefore, it is important to understand the needs and concerns of the people involved, and to provide adequate support and training to ensure a smooth transition.

=== Complexity: ''How are we doing it?'' ===

A change process can be complex to implement successfully in an organisation. This is for instance due to the fact that the process involves difficult tasks such as important decisions, multiple stakeholder, clear communication and effective leadership. Additionally, the complexity of the change process can increase if there is resistance from employees or if the change requires a significant shift in the organisation's culture or way of doing things.

=== Uncertainty: ''What if?'' ===

Organisational change processes do often involve uncertainty. While the organisation may have a clear purpose of what it wants to achieve, there may be limited information, unforeseen challenges or unintended outcomes that cannot be predicted in advance.

In summary, examining organisational change through the lens of the four perspectives can help organisations better understand the challenges it presents and develop effective strategies for managing it.

= Program management =
Changes are often managed less efficiently than they could be. This causes, that those responsible for managing the change may fail to handle some of the critical factors of the process, as presented above. Failing to manage the change process successfully can have a negative impact on the entire organisation and ultimately result in the organisation not surviving. In this context, program management and its comprehensive toolbox can be applied to facilitate a more successful change management process <ref>''http://wiki.doing-projects.org/index.php/Kotter%27s_8-Step_Change_Model_as_a_tool_in_Program_Management'' ''Kotter's 8-Step Change Model as a Tool in Program Management'', last visited 03-05-2023</ref>.

== What is program management? ==
Program management is a discipline which involves managing a collection of related projects that are designed to achieve a specific goal or objective. Program managers are responsible for ensuring that all projects within a program are aligned with the organisation's common strategy and goals, also when changes occur <ref>''https://www.pmi.org/learning/featured-topics/program'' ''Definition of Program Managment'', last visited 02-03-2023</ref>.

Program management does often use a framework to keep track of the related projects within the program. An example of a framework is the '''program management stage mapping''', which is divided into four stages; '''identification''', '''planning''', '''delivery''' and '''closure'''. The stage model provides a structured approach to program management, ensuring that each phase is completed before moving on to the next. Moreover, it facilitates effective communication, decision making and risk management throughout the program life cycle <ref>''https://www.projectsmart.com/articles/framework-for-programme-management.php'' ''A Framework for Program Management'', last visited 02-05-2023</ref>. 

Programs are defined by '''benefits''' and '''projects'''; programs attend to achieve benefits, where the benefits are achieved through execution of projects within the program. The success of a program is measured on to what extend the benefits are achieved. As defined by the Project Management Institute (PMI), programs aim to achieve benefits through the application of five performance areas below <ref name=5parts>''https://www.projectengineer.net/the-5-parts-of-program-management/'' ''The 5 Parts of Program Management'', last visited 02-03-2023</ref>.

=== Strategy alignment ===

Strategy alignment refers to the process of ensuring that the programs and projects being implemented within an organisation are fully aligned with the overall strategy.

=== Benefits management ===

Benefit management refers to the management of the benefits a program is aiming to achieve. The purpose of this area is that the program delivers the intended outcomes to the organisation.

=== Stakeholder engagement ===

All programs contains stakeholders and the various stakeholders have different interests and requirements. This area refers to the process identifying and engaging with the relevant stakeholders who are affected by the program.

=== Governance ===

Governance includes to the set of policies, procedures and practices that are put in place to ensure that programs are managed effectively and efficiently.

=== Life cycle management ===

Lastly, life cycle management covers the process of managing the program and maximising the benefits throughout the entire life cycle.

Each of these five areas serves tools within program management. The areas will later be used to create the connection between program management and an organisational change process presented in Figure 2 earlier in the article.

= Application of program management in organisational change =

[[File:hayes v2.png|260px|thumb|'''Figure 4''': Performance areas mapped onto the change management process (created by Cirkeline Bräuner)]]

''"Program management is a structured framework for defining and implementing change within an organisation"'' - James J. Leal <ref>''http://www.projectsmart.co.uk/programme-management.php'' ''Project Smart Programme Management a Structured Framework for Implementing Change'', last visited 06-03-2023</ref>.

As Leal points out, program management serves as a structured framework to help implementing changes successfully in organisations. This means that change management and program management often work in parallel with each other.

In Figure 3 the connection between these two management fields is illustrated. The five performance areas for measuring program success are mapped onto Hayes' change management process presented in Figure 2 earlier. However, it is important to mention that these areas can be mapped in different ways, and this is an example of one of the ways it can be done.

# The first performance area, strategy alignment, fits well into the diagnosing and planning stages. During these stages, the strategy for the desired change is formulated. Without strategy alignment, the program may fail to achieve the desired outcomes of the change or may even create conflicts with other organisational initiatives. 
# The second performance area, benefits management, is an important part of the recognising and starting stage. This stage includes identifying the desired benefits for implementing the change. 
# The third performance area, stakeholder engagement, is placed above the process, as this stakeholders and people in general are crucial for all stages in the change process. 
# The fourth performance area, governance, is placed next to the reviewing stage. This is due to the fact that the set of policies, procedures and practices needs to be reviews throughout the entire process. 
# Lastly, the fifth and last performance area, life cycle assessment, is also placed above the process. This area includes managing the program and maximising benefits throughout all steps in the change process.

By combining the performance areas and the change management process it is seen that there are a lot of similarities in how the two management fields initiate projects within a program. Moreover, the change management process becomes even stronger by applying the program management performance areas. For instance, the original change management process in Figure 2 does not include the governance perspective, which is very crucial when going through an organisational change. However, the combined model does also show where gaps remain when change management and program management are combined. For instance, the model neglects the financial part such as financial management, procurement management, resource management and risk management <ref name=5parts />.

= Limitations and benefits =

Throughout the article, an understanding of what change management and program management entail has been created. In addition, the two areas have been combined in a unified model in Figure 4. Finally, the limitations and benefits of the two fields and this model will be discussed.

== Limitations ==
The following limitations are identified in relation to the analysis:

'''No one-size-fits-all approach'''

:: As explained in the beginning of the article, different models can be used to describe the process of implementing organisational change (Lewin's and Hayes' models have been provided as examples). The fact that there is no one-size-fits-all approach for implementing change can make it difficult for organisations to create a procedure for the change, as there are many ways of approaching it.

'''Potential gaps in unified model'''

:: The unified model presented in Figure 4 addresses that there remain financial management gaps when combining the two management fields. The fact that gaps exist, and there is not defined a general approach for using program management in organisational change can challenge the organisations and make them afraid of even planning a change.

'''Increased complexity'''

:: Combining the two management fields can increase complexity among the organisation's employees and make the change process even more difficult to navigate.

== Benefits ==
In addition, the following benefits are identified in relation to the analysis:

'''Enhanced communication and collaboration'''

:: By combining the change management process and the program management performance areas, the communication and collaboration between these fields are streamlined. Moreover, it helps to identify and resolve potential conflicts, dependencies and risks.

'''Improved visibility and control'''

:: Program management tools and practices provide a comprehensive view of all the projects involved in the change process. This allows organisations to identify and resolve difficulties early, allocate resources efficiently and track progress effectively.

'''Efficient resource allocation'''

:: Program management helps organisations to allocate resources efficiently across different projects. By having a comprehensive view of all the projects involved in the change process, program managers can identify areas of overlap or duplication and allocate resources accordingly. This ensures that resources are used effectively and efficiently, which ultimately reduces costs and improves project outcomes.

'''Increase risk management'''

:: Program management enables organisations to identify and reduce risks across projects. This helps to minimise the impact of potential problems on the overall change process.

= Annotated bibliography =

For further reading on the topic or related topics, the reader is encouraged to check out the following material:

'''Facilitating Change, Lauge Baungaard Rasmussen, 2011'''
:: This book presents a guide for people who want to facilitate change processes within their organisations. Moreover, it provides a framework on how to assess whether an organisation is ready for a change, which has not been covered in this article.

'''Kotter's 8-Step Change Model as a Tool in Program Management, Emma Balstrup Klinke Hansen, 2018'''
:: This Wiki article describes Kotter's change model, which is another model than the once provided in this article. It explains how this model can be used to implement changes in organisations' programs.

'''Leading Change, John Kotter, 1996'''
:: This book discusses why change initiatives often fail due to the fact that they are not following a structured process. In this context, the book provides successful and unsuccessful examples of various change initiatives.

'''The Theory and Practice of Change Management, John Hayes, 2010'''
:: This book has been involved in some parts of this article. However, it includes other relevant and important information related to change management. For instance, the book provides different practical tools for managing change processes including Lewin's change model, Kotter's eight-step model and action research.

= References =
<References/>

[[Category:Change Management]]
[[Category:Program Management]]