Revision as of 17:14, 5 May 2023

Abstract

The purpose of this wiki article is to give an overview of the Lippitt-Knoster tool for complex change management, and how this relates to project management. When considering project management, one must also consider that projects are led by people, and that most projects are influenced or effected by some sort of change, whether it being a change in deadline, budget, resources, etc. Thus when working with project management, the project manager must consider the effect of changes and thereby change management. In short, when project management and change management are integrated there is a larger chance of success ^[1].

This paper will include a walk-through of the Lippitt-Knoster model and the different aspects included and considered in the model. The paper will consider the usability of the model and how the model can be used in practice, both prior, during and after a project has been completed. Thus, considering if the model can be used to improve further change initiatives and enhance learnings to use in future projects.

Lastly the article will also include aspects of limitations, in regard to the conflict areas, when looking at the model from a theoretical perspective vs. a practice perspective. As Project management and change management are different management diciplines, one must consider possible challenges of an integration of the two. Furthermore, the limitations in regard to organisational setup and industry will also be considered when talking about the model and how project management is included, since these aspects have large influence working with both change management and project management.

Big idea

During a project period, It is common that changes occur. These changes can be in regard to people, resources, timing, budget, etc. For this reason, it is important to account for the effects the changes have on the project and the project team. Hence why change management is an important factor to consider when performing projects and in project management in generel.

Whereas project management focuses on processes and activities needed to complete and be success full in a project, change management focuses on the people affected by the projects underway. Hence one would argue that a change manager uses strategies that focus on individual achievement and change adaptation, and a project manager uses processes that focus on meeting benchmarks and achieving clearly defined objectives. Thus, an inherent focus on both management disciplines would ensure projects long-term success in the organization ^[2].

One recognized change model is Lewins tree step model, which involves the steps of unfreeze, move, and refreeze. This process of change put emphasis on the need for change, hence the unfreezing, moving toward the desired change, and lastly refreezing the new norms and making sure that the change is rooted ^[3].

On the other hand, as with change management, there are multiple approaches to project management, on of them being system-oriented problem solving, or systems enegineering. Here the breakdown structure are very similar to that of Lewins three step change model, as the framework for solving project with a system-oriented minset is mapping current state and a target state, and then plan for how to achieved this ^[4]..

Hence, one could argue that the nature of project management and change management follows the same life cycle as is illustrated in below picture.

Since project managers primary focus is on fulfilling the objectives of the project, there is a secondary focus on the impact the project has on the project team and involved stakeholders. As a result of the impact among employees being of secondary focus, changes can expedite uncertainty among the project team and stakeholders, and this uncertainty can foster e.g. anxiety, confusion, or resistance, which are some of the problems that are highlighted by the Lippitt-knoster model.

The Model

The Lippitt-Knoster model, as can be seen in the visual to the right, consist of five different aspects to consider, when working with and planning for change. The areas are Vision, Skills, Incentives, Resources and Action Plan, and they are outlining the required elements for successful change, and the possible conflict outcomes, if they are not considered ^[5]..

Vision

Initially, a Vision for the change must be considered, thus answering the questions 'Why is the change needed?'. Hence, the 'why' is an immensely important aspect, as the people working with the change will experience confusion, if they cannot relate or understand the reason for change and if they ask themself questions such as 'Why should I do this?'.

Skills

Considering the skills needed for change is also important, since the lack of skills among the people working with change will feel anxious about the forth coming change. Here the model seeks to map what skills are needed and if the people working with change have the necessary expertise or training.

Incentives

Another important aspect is the incentive for change. All people working with the change must be able to see the value in the change, or else possible resistance can occur. Here both tangible and intangible incentives should be considered; is the incentive monetary or does it drive personal achievements?

Resources

Resources are also important to consider, and whether the project team has the resources it requires to bring forth the change. If there are not enough resources, it will bring frustration to the people working with the change. Here it would be relevant to consider both internal and/or external resources, and how the dynamics are also influences by the combination of these.

Action Plan

Lastly, it is important to consider the fact that the change should entail an action plan, which should be clear and developed in collaboration with all stakeholders. Without an action plan, the people working with the change could start to feel they are going in no direction and it creates a false start for the project team.

Application

By integrating change management into project management, it can increase the support for the project and reduce resistance, as it combines the people aspects and the project aspects, thus contributing to achieving the project objectives and realising organisational benefits ^[6].

• How can the model be used?

There are multiple areas, wherein the model can be utilised. Thus, it can both be in the pre project or pre change period, where the model serves as a support tool for mapping areas to focus on and/or areas to assess further before the commencement of the project and/or change ^[7]. The model can also be used through a change process or project, to identify areas and/or processes which are not working as intended within the project og process. Lastly, the model can also be used as a post-project or post-process review framework, to further understand what elements that succeeded and those that did not, and thus why.

Pre-project

Regarding project management and the inherently present complexity in projects, the model can be utilized as a planning tool. In the mapping of the current state, referring to the system-oriented approach to project management, the project manager can use the different components in the model as corner flags in the planning, to make sure each of these is present and/or considered in the mapping of the current state. So forth the project manager, already before the project commencement, knows that there are missing components, she will either have the possibility to plan around them, so forth budget constraints are present, or she will be able to increase or plan for the missing components, so that the project team already from the beginning are prepped with the mindset of a successful change or project completion.

why is complexity important to consider? ^[8].

During project

Problems and/or challenges arise in projects, often due to complexity and uncertainty ^[8]. Though, even though the project manager and the project team are aware of complexity and uncertainty, it cannot always be planned for. Thus, the Lippitt-Knoster model can also be utilized during a project period, as a framework for identifying possible problems, that are the root cause of different symptoms such as delays or unmet deadlines throughout a project period. Here the model provides a framework for the project manager again, with the different components serving as corner flags in the analysis. The project manager will be able to either map out and/or exclude possible causes for unmet deadlines, with the perceived experience from the project team in focus. By utilizing the model, a derived benefit could be that the project team will feel heard and involved in figuring out what the reasons behind the delay and/or other complications are, because the components in the model take the perception of the project work into consideration, thus creating a space for collective improvement in the project team, which will benefit the project overall.

Post-project review

- How did the project end? - Why / why not was it a succes? - single vs. double loop learning? ^[3].

Limitation

As change mangement and project management is different diciplines in theory, one does not function in practice without the other.

- performing the analysis is time consuming, and requires a lot of input. This input also needs to be given from all aspects of a project, thus requiring a lot of resources. - you have to account for interdependencies between these areas, as they might not be easily divided in practice. - it does not provide a how to, but just, what is wrong - as manager, you need to either know how to move forward with the results, or be prepared to put in the work and/or plan for this in upcoming projects. -

References

Many of the following references are online articles and conference papers, as the Lippitt-Knoster model was birthed at the XX conference in xxxx, by xx Knoster, when he used the original model by xx Lippitt as sources.

1. ↑ Prosci, 2012/2020, https://www.prosci.com/resources/articles/change-management-best-practices. Best Practices In Change Management
2. ↑ LucidChart, 2023, https://www.lucidchart.com/blog/project-change-management#:~:text=What%20is%20change%20management%3F,other%20changes%20within%20the%20organization).. Understanding the difference between project management and change management
3. ↑ ^{3.0 3.1} John Hayes, 2002/2006/2010/2014, fourth edition, Palgrave Macmillan. The Theory and practice of change management
4. ↑ Josef Oehmen, 2023. Systems-Oriented Problem Solving to Project Management
5. ↑ Sergio Caredda, 2020, https://sergiocaredda.eu/organisation/tools/models-the-lippitt-knoster-model-for-managing-complex-change/. Models: The Lippitt-Knoster Model for Managing Complex Change
6. ↑ Prosci, https://www.prosci.com/resources/articles/integrating-change-management-and-project-management. Integrating Change Management and Project Management
7. ↑ Michael Nanfito, 2015, https://www.linkedin.com/pulse/get-grip-managing-change-deploying-knoster-model-michael-nanfito/. Get a Grip on Managing Change: Deploying the Knoster Model for Successful Implementation
8. ↑ ^{8.0 8.1} Edoardo Favari, 2023, Springer. Project Management: Leading Change in the Age of Complexity