DTU ProjectLab - User contributions [en-gb]

Symbiosis of change and project management

2022-03-27T21:16:22Z

S213053: /* Success criteria */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T21:14:57Z

S213053: /* Success criteria */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

<pre>Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria. </pre>

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T21:14:02Z

S213053: /* Success criteria */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria. 

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T21:13:41Z

S213053: /* The basis of change management */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria. 

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T21:13:22Z

S213053: /* The importance of change management in relation to project success */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria. 

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T21:12:49Z

S213053: /* The basis of change management */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria. 

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T21:12:30Z

S213053: /* The importance of change management in relation to project success */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria. 

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

 ===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T21:11:40Z

S213053: /* Success criteria */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria. 

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution. <ref>Sarayreh, Bashar Hussein, Hassan Khudair, and E. A. Barakat. "Comparative study: The Kurt Lewin of change management." International Journal of Computer and Information Technology 2.4 (2013): 626-629. </ref>

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company. <ref>Levasseur, Robert E. "People skills: Change management tools—Lewin's change model." Interfaces 31.4 (2001): 71-73.</ref>

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team. <ref>Shirey, Maria R. "Lewin’s theory of planned change as a strategic resource." JONA: The Journal of Nursing Administration 43.2 (2013): 69-72.</ref>

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Articles Spring Term 2021

2022-03-27T21:05:15Z

S213053: /* Overview of 2021 Wiki Collections */

=Overview of 2021 Wiki Collections=

{| class="wikitable sortable"
|+Spring Term 2021 Wiki Collections
|Group name
|First name
|Surname
|Student number
|[[Article name]]
|-
|-
|TAs Example
|Thomas
|Giannoulopoulos
|s192419
|[[APPM Example 2021]]
|-
|-
|Group 12
|Christian
|Frøsig
|s175044
|[[Belbin's 9 team roles]]
|-
|-
|Group 1
|Oliver
|K. Vittrup
|s163754
|[[Top-down vs bottom-up estimations]]
|-
|-
|44
|Jeyad
|M. Baig
|s153585
|[[Planning Methods - 3 Levels of Project Planning]]
|-
|-
|Group 17
|Quoc-Khanh Rose-Marie Therese
|Madsen
|s123462
|[[Applying Tuckman’s model for team development]]
|-
|-
|31
|Haoxiang
|Sang
|s192258
|[[Cost control with statistic tools]]
|-
|-
|Group 31
|He
|Fan
|s192195
|[[Work Break-down Structure]]
|-
|-
|Group 19
|Ángel
|Castro del Olmo
|s193246
|[[Stakeholder Engagement and Sustainability in Maritime Spatial Planning]]
|-
|-
|44
|Abdullah Shams
|Turkmani
|s153337
|[[ICT Agreement]]
|-
|-
|Group 17
|Jacopo
|Renzi
|s210445
|[[Double Diamond in Project Management]]
|-
|-
|Group 35
|Helga Sigríður
|Magnúsdóttir
|s202027
|[[Network Planning]]
|-
|-
|12
|Cæcilie
|Kortbæk
|163873
|[[Double diamond]]
|-
|-
|Group 18
|Frithjof Johannes
|Thiem
|s202972
|[[DevOps]]
|-
|-
|12
|Emilie
|Winther Schmidt
|163884
|[[Iron Triangle]]
|-
|-
|12
|Anna
|Fredgaard
|s163887
|[[Active Listening Technique]]
|-
|-
|35
|Ruben
|Raes
|s202029
|[[Iron Triangle of Project Management]]
|-
|-
|21
|Claudia
|Balcells
|s202939
|[[APPPM Issue Tree]]
|-
|-
|35
|Brynja
|Gudmundsdottir
|s202030
|[[FAST goals]]
|-
|-
|16
|Andrea
|Pin Morales
|s205567
|[[The Business Case]]
|-
|-
|16
|Lena Maria
|Thyen
|s202969
|[[The 7 Habits of Highly Effective People for Successful Leadership]]
|-
|-
|35
|Úlfar
|Viktorsson
|s202022
|[[The 4 Disciplines of Execution]]
|-
|-
|16
|Moritz
|Rindermann
|s202976
|[[Tuckmans model for Team Development]]
|-
|-
|Group 29
|Heiðdís Ósk
|Pétursdóttir
|s202025
|[[Efficiency and Effectiveness]]
|-
|-
|31
|Xabier
|Martínez de Zabarte
|s210323
|[[Scrumban]]
|-
|-
|17
|Aldís Braga
|Eiríksdóttir
|s202045
|[[Blake-Mouton Managerial Grid]]
|-
|-
|32
|Jan Otis
| Ernst
|s210433
|[[RACI Matrix]]
|-
|-
|3
|Julie
| Finne-Ipsen
|s153987
|[[Kahneman - Two Thinking Systems]]
|-
|-
|24
|Maria Eileen
| Hubbuck
|s210444
|[[Risk Management-Identification]]
|-
|-
|11
|Alina
| Barun
|s202514
|[[Maslow's Hierarchy of Needs]]
|-
|-
|24
|Felix Vinzenz
|Wütherich
|s202968
|[[Emotional Intelligence and Leadership]]
|-
|-
|28
|Ariadna
|Ramos
|s191852
|[[The Work Breakdown Structure (WBS)]]
|-
|-
|Group 27
|Jakob
|Grønvald
|s164346
|[[Maslow‘s Hierarchy of Needs, Motivation in the workplace]]
|-
|-
|Group 16
|Martina
|Rampazzo
|s202895
|[[Earned value management (EVM)]]
|-
|-
|Group 2
|John
|Fritz
|s202967
|[[Learning plan]]
|-
|-
|Group 24
|Henning
|Duwe
|s210450
|[[SWOT Analysis]]
|-
|-
|Group 14
|Søren Emil
|Kjær
|s201528
|[[GANTT]]
|-
|-
|Group 23
|Mathilde Kremmer
|Broberg
|s175074
|[[Corrective and Preventive Actions (CAPA)]]
|-
|-
|Group 14
|Rune Lykke
|Høg
|s165012
|[[The use of the A3 management process]]
|-
|-
|Group 35
|Tinna Hrönn
|Unudóttir
|s202032
|[[Constructive communication]]
|-
|-
|Group 17
|Eva Rún
|Arnarsdóttir
|s203214
|[[Biases in Project Management]]
|-
|-
|Group 24
|Astrid
|Skovhus
|s164499
|[[Getting Things Done (GTD)]]
|-
|-
|Group 7
|Phillip
|Dyrberg
|s164503
|[[Double diamond: A design process model]]
|-
|-
|Group 14
|Amanda Emilie
|Søborg Berthelsen
|s154707
|[[The Johari Window]]
|-
|-
|Group 23
|Nicolai Mossing
|Madsen
|s164515
|[[SMART Goals (Specific, Measurable, Attainable, Relevant, Time-bound)]]
|-
|-
|Group 27
|Marie-Louise Wolfsberg
|Schmidt
|s164417
|[[The Affect Heuristic]]
|-
|-
|Group 4
|Erika Marie
|Strøm
|s203224
|[[Parkinson's Law in Project Schedule Management]]
|-
|-
|Group 16
|Beatrice
|Ranzato
|s202887
|[[X-Matrix Hoshin Kanri]]
|-
|-
|Group 9
|Helene Waldmann
|Jørgensen
|s173891
|[[Lag & Lead]]
|-
|-
|Group 4
|Zahra
|Al-Mosawi
|s193938
|[[Belbin Team Roles in Project Management]]
|-
|-
|Group 14
|William Axel Linderoth
|Michaelen
|s153275
|[[Design-Build]]
|-
|-
|Group 31
|Jesús
|Gracia Yoldi
|s210111
|[[Kanban in APPPM]]
|-
|-
|Group 35
|Katrín Erla
|Bergsveinsdóttir
|s202026
|[[Contingency plans]]
|-
|-
|Group 1
|Cecilie Marie Raagaard
|Christensen
|s160832
|[[Work breakdown structure (WBS)]]
|-
|-
|Group 19
|Ali Jamal
|Jomeh
|s173741
|[[SMART goals: A goal-setting technique]]
|-
|-
|Group 15
|Tobias
|Hyldmo
|s206658
|[[High performing teams]]
|-
|-
|Group 5
|Samah
|Said
|s203228
|[[Reference class forecasting]]
|-
|-
|Group 3
|Emilie
|Torp
|s153320
|[[Goal Hierarchy]]
|-
|-
|Group 3
|Victor Nørregaard
|Schwærter
|s164745
|[[Milestone Planning]]
|-
|-
|Group 9
|Jacob
|Ammitsøe
|s173849
|[[Authenticity]]
|-
|-
|Group 18
|Anna
|Bjørn Reland
|s154556
|[[Choosing the appropriate medium (oral – written – hybrids)]]
|-
|-
|Group 10
|Wail
|Atrari
|s170706
|[[The Double Diamond Tool: An efficient Project Management Tool]]
|-
|-
|Group 10
|Mohammad
|Abou Hassan
|s160101
|[[Implementing SWOT]]
|-
|-
|Group 10
|Ahmet
|Akgül
|s152597
|[[Smart goals (Specific, Measurable, Achievable, Realistic, and Timely)]]
|-
|-
|Group 2
|Amalie
|N. Müller
|s173675
|[[Big five personality traits (OCEAN model)]]
|-
|-
|Group 29
|Pétursdóttir
|Stefanía Ósk
|s202044
|[[Situational leadership - Hersey and Blanchard]]
|-
|-
|Group 10
|Abdulahi
|Hayle Hassan
|s164691
|[[Stakeholder management]]
|-
|-
|Group 27
|Louise
|Landschoff
|s165111
|[[SCRUM - A Project Management Framework]]
|-
|-
|Group 10
|Sara
|Alabiidi
|s164650
|[[The Blake-Mouton Managerial Grid]]
|-
|-
|Group 4
|Felix
|Dressel
|s202965
|[[The SPALTEN Problem-Solving Methodology as a Decision Making Tool in Project Management]]
|-
|-
|Group 11
|Sandra
|Nielsen
|s153370
|[[Conflict ladder]]
|-
|-
|Group 11
|Lise Munch
|Nordheim
|s200400
|[[McGregor's X & Y theory]]
|-
|-
|Group 2
|Simon
|Knutsson
|s202041
|[[Earned Value Management (EVM)]]
|-
|-
|Group 12
|Christoffer
|Askgaard
|s165098
|[[Design the team you need to succeed using Belbin's team roles]]
|-
|-
|Group 24
|Gaute Bø
|Aaløkken
|s202065
|[[Diversity in teams]]
|-
|-
|Group 2
|Lukas
|Tanzer
|s200120
|[[Kanban]]
|-
|-
|Group 7
|Sofie
|Lundsteen
|s170285
|[[Creating effective teams with the use of Belbin's Team Roles]]
|-
|-
|Group 14
|FIRST NAME
|LAST NAME
|STUDY ID
|[[Applying the Hawthorne studies to project management]]
|-
|-
|Group 3
|Amalie Nordstrøm
|Nielsen
|s153272
|[[The seven characteristic principles]]
|-
|-
|Group 14
|Louise Damborg
|Frederiksen
|s185238
|[[Using Facilitation to Mitigate Bias in a Team Setting]]
|-
|-
|Group 1
|Georg Holger
|Waage
|s163819
|[[Fishbone Diagram]]
|-
|-
|Group 28
|Özgenur
|Baştuğ
|s203033
|[[Change Orders in Construction Projects]]
|-
|-
|Group 9
|Mads
|Møhlenberg
|s173879
|[[A hybrid consisting of Agile and Stage Gate]]
|-
|-
|Group 29
|Svanhvít Birta
|Guðmundsdóttir
|s203174
|[[Project Milestones]]
|-
|-
|Group 23
|Bente
|Meidahl Münsberg
|s175068
|[[Gantt Charts]]
|-
|-
|Group 27
|Frederik
|Carlsson
|s164345
|[[FAST Goals]]
|-
|-
|Group 11
|Tobias
|Rydahl
|s200471
|[[Using DISC assessment for project team management]]
|-
|-
|Group 7
|Mads
|Støjfer-Hønberg
|s174303
|[[SCRUM - An Agile Project Management Framework]]
|-
|-
|Group 21
|Matthieu
|Buy
|s202925
|[[The Five-Factor Model (OCEAN)]]
|-
|-
|Group 18
|Astrid Helene
|Erecius
|s171013
|[[Choosing communication media for negotiation]]
|-
|-
|Group 44
|Zainab
|Jalal
|s165491
|[[Work Breakdown Structure in project management]]
|-
|-
|Group 2
|Anna Felicia Mai
|Lindström
|s202046
|[[Project Status Reporting]]
|-
|-
|Group 28
|Alberto
|Melloni
|s202894
|[[Pre-mortem analysis]]
|-
|-
|Group 29
|Thore Uwe
|Aye
|s202746
|[[Quality Gates in Project Management]]
|-
|-
|Group 9
|Lydia
|Tsintzou
|s193745
|[[SWOT Analysis Guide]]
|-
|-
|Group 28
|Kendra Ana
|Rodríguez López
|s200182
|[[Choosing by Advantages Decision-Making System]]
|-
|-
|Group 23
|Rasmus
|Engberg
|s164513
|[[RDM]]
|-
|-
|Group 4
|Christine
|Fryland
|s153875
|[[Theory X-Y in project management]]
|-
|-
|Group 28
|Manas P.
|Dalvi
|s210143
|[[Effective Tools for Multiple Project Management]]
-
|-
|Group 12
|Joakim
|Vollertzen
|s163947
|[[Extreme Project Management (XPM)]]
|-
|-
|Group 19
|Shubham
|Ingole
|s200092
|[[Stakeholder Management using Social Network Theory]]
|-
|-
|Group 31
|Alvaro
|Bello
|s210447
|[[Forecasting and estimation techniques]]
|-
|-
|Group 09
|Dorothea
|Georgiadou
|s200230
|[[Risk Register analysis]]
|-
|-
|Group 09
|Maria Konstantina
|Papaioannou
|s195550
|[[Fishbone diagram analysis]]
|-
|-
|Group 21
|Kelvin
|Scott-Fordsmand
|s174312
|[[RiskRegister]]
|-
|-
|Group 18
|Christoffer Friis
|Hansen
|s164569
|[[Identifying risk]]
|-
|-
|Group 1
|Giulia
|Zanelli
|s205701
|[[Earned Value Management - EVM]]
|-
|-
|Group 29
|Tinna
|Dofradottir
|s203177
|[[Adaptive Project Framework]]
|-
|-
|Group 23
|Jonatan Larsen
|Edry
|s165499
|[[The iron triangle as an analytical tool]]
|-
|-
|Group 4
|Mikkel Walther
|Hellesen
|s203227
|[[System Readiness Level Index]]
|-
|-
|Group 5
|Yamila Denise
|Aviles
|s203409
|[[Agile Release Train]]
|-
|-
|Group 5
|Kallina
|Karamitsiou
|s202249
|[[Kahneman's dual-system thinking]]
|-
|-
|Group 19
|Prasad
|Jagtap
|s200109
|[[Communication Management using Service Blueprint]]
|-
|-
|Group 3
|Johan Holger
|Rasmussen
|s210512
|[[Daniel Kahneman's two systems of thinking]]
|-
|-
|Group 18
|Sigrún Björk
|Sævarsdóttir
|s200165
|[[The Scrum framework]]
|-
|-
|Group 1
|Francesca
|Pieraccini
|s206673
|[[Double Diamond model]]
|-
|-
|Group 15
|Dionysios
|Dasopoulos
|s202916
|[[Tuckman's Model for Sustainable Team Development]]
|-
|-
|Group 15
|Joern
|Appelt
|s202854
|[[Intrinsic Motivation]]
|-
|-
|Group 23
|Oliver
|Karlsson
|s165080
|[[Double Diamond Model]]
|-
|-
|Group 5
|Victor
|Soler Fuertes
|s206040
|[[OKR - Objectives and Key Results]]
|-
|-
|Group 31
|João
|Ferreira
|s202867
|[[Psychological safety as a key factor to quality and productivity of Organizations]]
|-
|-
|Group 31
|Timo
|Scheitinger
|s202966
|[[The big five (OCEAN)]]
|-
|-
|Group 15
|Maria-Lito
|Glykioti
|s151256
|[[The role of Emotional Intelligence in Project Management]]
|-
|-
|Group 15
|Hafeez
|Ahmadi
|s164137
|[[ISM Principles of Change]]
|-
|-
|Group 18
|Marie Elly Ulricke
|Kristensen
|s144408
|[[Motivation through Theory X&Y from a Project Management perspective]]
|-
|-
|Group 18
|Christopher
|Burgdorf
|s154689
|[[Simple Multi-Attribute Rating Technique (SMART)]]
|-
|-
|Group 5
|Ishak
|Zaaimia
|s164631
|[[Parkinson's Law]]
|-
|-
|Group 11
|Sara Ballegaard
|Laursen
|s193723
|[[Organizational Socialization]]
|-
|-
|Group 19
|Ali Waleed
|Abbas
|s172841
|[[Fishbone diagram for root cause analysis]]
|-
|-
|Group 17
|Cecilia
|Thuy Duyen Nguyen-Cong
|s184300
|[[The 7 Habits of Highly Effective People by Stephen R. Covey]]
|-
|-
|Group 44
|Farah
|Sabri
|s164740
|[[Lack of communication in project management]]
|-
|-
|Group 1
|Shakila
|Khan Malik
|s173780
|[[Risk]]
|-
|-
|Group 27
|Asbjørn Martin
|Kruuse
|s153470
|[[Chairing a meeting]]
|-
|-
|Group 23
|Tummas Dímun
|Mohr
|s160129
|[[Project Dashboards]]
|-
|-
|Group 27
|Vanessa
|Clausen
|s183302
|[[Overcoming small-big projects (Gantt)]]
|-
|-
|Group 09
|Emil
|Ballermann
|s174393
|[[Parkinson's law and how to manage it]]
|-
|-
|Group 4
|Gian Marco
|Grieco
|s202893
|[[Parkinson's Law: achieving more in less time]]
|-
|-
|Group 44
|Shahad
|Abdelaziz
|s122945
|[[Outsourcing]]
|-
|-
|Group 3
|Tais
|Christiansen
|s165131
|[[Relationship of projects, programs and portfolios]]
|-
|-
|Group 4
|Sana
|Ilyas
|s192815
|[[SCRUM framework]]
|-
|-
|Group 5
|Mia Chrstine
|Wheitman
|s206053
|[[The use of Gantt Charts]]
|-
|-
|Group 35
|Sigurjón Bjarni
|Bjarnason
|s202049
|[[The Work breakdown structure(WBS)]]
|-
|-
|Group 19
|Morten Dam
|Laursen
|s200364
|[[Multiple Project Management: Summary, Theory and Improvement]]
|-
|-
|Group 29
|Céline Engelbrecht
|Galea-Larsen
|s147312
|[[Group Development - The Tuckman Model]]
|-
|-
|Group 28
|Hazal
|Alawi
|s180408
|[[The Double Diamond Framework]]
|-
|-
|Group 17
|Xenia
|Jørgensen
|s123633
|[[Teams - Creation and optimisation]]
|-
|-
|Group 11
|Jonas
|Bøje Simonsen
|s154089
|[[Logic tree and the Answer First Methodology]]
|-
|-
|Group 28
|Kavikrishnan
|Balakrishnan
|s164338
|[[Learning plans for high uncertainty projects]]
|-
|-
|Group 2
|Riccardo
|Pollacchini
|s192412
|[[Complex Project Management (CPM)]]
|-
|-
|Group 44
|Rokiya
|Ahmed Ramzy
|s170501
|[[Lean in construction industry]]
|-
|-
|Group 50
|Avishkar Anil
|Vadnere
|s206513
|[[Strategic Planning using SWOT analysis]]
|-
|-
|Group 5
|Niels
|Tietgen
|s193191
|[[Microsoft Teams]]
|-
|-
|Group 29
|Bastien
|Haas
|s202932
|[[The 7 habits of highly effective people applied to Management]]
|-
|-
|Group 17
|Jacob
|Lützhøft Christensen
|s184113
|[[Lag and Lead]]
|-
|-
|Group 44
|Gergely
|Bordi
|s213053
|[[Symbiosis of change and project management]]

Symbiosis of change and project management

2022-03-27T20:55:24Z

S213053: /* Change management in practice using the Lewin-model */

Symbiosis of change and project management

2022-03-27T20:53:27Z

S213053: /* Communication strategies that help change */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change. <ref>Lies, Jan. "Internal communication as power management in change processes: Study on the possibilities and the reality of change communications." Public Relations Review 38.2 (2012): 255-261. </ref>

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.
<ref>Paton, Robert A., and James McCalman. Change management: A guide to effective implementation. Sage, 2008. </ref> <ref>Anderson, Dean, and Linda Ackerman Anderson. Beyond change management: Advanced strategies for today's transformational leaders. John Wiley & Sons, 2002.</ref>

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:51:53Z

S213053: /* The background and pitfalls of change */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref> <ref>Millar, Carla CJM, Olaf Groth, and John F. Mahon. "Management innovation in a VUCA world: Challenges and recommendations." California management review 61.1 (2018): 5-14. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:51:23Z

S213053: /* The background and pitfalls of change */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others. <ref>Pearse, Noel J. "Change management in a VUCA world." Visionary leadership in a turbulent world. Emerald Publishing Limited, 2017. </ref>

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces. <ref>Mack, Oliver, et al., eds. Managing in a VUCA World. Springer, 2015. </ref>

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:50:13Z

S213053: /* Stakeholders */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project <ref>Aladwani, A.M. (2001): Change Management Strategies
for Successful ERP Implementation. Business Process
Management, 7 (3) </ref>.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". <ref>Al-Mashari, M. – Al-Mudimigh, A. – Zairi, M. (2003):
Enterprise Resource Planning: A Taxonomy of Critical
Factors. European Journal of Operational Research,
146 </ref>.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. <ref> Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:47:58Z

S213053: /* Top leadership */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. <ref>Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1) </ref> In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. <ref>Kohnke, O. (2005): Change Management als strategischer
Erfolgsfaktor bei ERP-Implementierungsprojekten. In:
O. Kohnke/Walter Bungard (Hrsg.): SAP-Einführung
mit Change Management. Gabler Verlag </ref>

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:46:17Z

S213053: /* Success criteria */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146 </ref>

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:45:03Z

S213053: /* Reasons why a project could fail */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

<ref>Umble, E.J. – Haft, R.R. – Umble, M.M. (2003): Enterprise
Resource Planning: Implementation Procedures and
Critical Succes Factors. European Journal of Operational
Research, 146</ref>

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:43:38Z

S213053: /* Abstract */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes <ref>Bingi, P. – Sharma, M.K. – Godla, J.K. (1999): Critical
Issues Affecting an ERP Implementation Information
Systems Management, 16</ref>. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:42:39Z

S213053: /* Conclusion */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

==Refrences==
<references/>

Symbiosis of change and project management

2022-03-27T20:42:17Z

S213053: /* The basis of change management */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing. <ref>Krüger, K. (2002): Excellence in Change Gabler Verlag
Nah, F. F-H. – Zuckweiler, K.M. – Lau, J. L-S. (2003): ERP
Implementation: Chief Information Officers’ Perceptions
of Critical Success Factors. International Journal Of
Human-Computer Interaction, 16(1)</ref>

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

<ref> Kohnke, O. – Bungard, W. – Madukanya, V. (2005):
Verbreitung und Stellenwert von Change Management
im Rahmen von SAP Projekten. In: O. Kohnke/
Walter Bungard (Hrsg.): SAP-Einführung mit Change
Management. Gabler Verlag </ref>

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

<references/>

Symbiosis of change and project management

2022-03-27T20:39:47Z

S213053: /* Conclusion */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==
In summary, Kurt Lewin's three-phase model is applicable to all elements of the corporate change management processes. The key point for the labor market and organizations is the training of competent management that is able to find the right answers for the company in the VUCA world, deal with problems and make the necessary changes based on good strategy. In such a way we don't need to use the language of force and orders, but maintain and even increase employee engagement after the change has taken place.

<references/>

Symbiosis of change and project management

2022-03-27T20:34:45Z

S213053: /* Change management in practice using the Lewin-model */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

==Conclusion==

Symbiosis of change and project management

2022-03-27T20:34:11Z

S213053: /* Change management in practice using the Lewin-model */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case, this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine-tuned and appropriate settings. It is important that in corporate culture, for change to be properly implemented the leader is not ashamed to admit a wrong decision. A good leader is someone who realizes in a short amount of time that change is needed and he also admits this to his team.

Symbiosis of change and project management

2022-03-27T20:30:32Z

S213053: /* Change management in practice using the Lewin-model */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

In the second phase, the phase of the change, the actual process of the change happens. What the management had planned, will be introduced. Changes in an organization can happen on three levels: individual, structures and systems, corporate and organizational atmosphere. With this in mind, you can consciously prepare for change and this process can also be structured and executed. In our case, after a few weeks, a conflict developed between the two newly formed organizations and sectors in the company. To solve this problem a facilitated workshop was held, that had as a final output a refined task matrix, which clarified the problematic area and removed the obstacles towards further success. For this to happen, it is required that the managers and the staff always be able to find a constructive solution, before the problem escalates.

The third phase is the solidification or re-freezing phase, which is the process where the change is finalized. Failure to do so, or improper execution involves the rearrangement of the processes from the original condition. In our case this meant that the organizational structure has been introduced in all corporate processes and governance systems, with fine tuned and appropriate settings.

Symbiosis of change and project management

2022-03-27T20:07:59Z

S213053: /* Change management in practice using the Lewin-model */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has the potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]] In the first phase, the thawing phase, the current organization and system is changed. In this section, several methods can be used by change managers and professionals. In my practical example, the management has chosen the following path: first, the experts analyzed why the company is not reaching the desired revenue numbers that are included in the plans for that business year. The possible reason for this according to the Pareto principle was that the company had too general answers and reactions for some of the more significant questions, dictated by the market. The root cause of this was that some functions of the management acted as a part of a larger organizational department, and thus lacked the decision-making powers and competencies, that would have been necessary for successful and efficient operation. In this case, the company, to overcome the already mentioned organizational resistance, chose a well thought out, structured, and conscious communication method, that supported change by presenting necessary analytical information to the employees. An important element of this phase was to make the employees aware that the change itself has to happen, and there's no alternative for the company.

Symbiosis of change and project management

2022-03-27T19:54:44Z

S213053: /* Change management in practice using the Lewin-model */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has a potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin1.jpg|500px|thumb|left|]]

File:Lewin1.jpg

2022-03-27T19:54:23Z

S213053:

Symbiosis of change and project management

2022-03-27T19:52:08Z

S213053: /* Change management in practice using the Lewin-model */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has a potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

[[File:lewin.jpg|500px|thumb|left|]]

File:Lewin.jpg

2022-03-27T19:51:01Z

S213053:

Symbiosis of change and project management

2022-03-27T19:50:38Z

S213053: /* Change management in practice using the Lewin-model */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. We have got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

People constantly encounter a change in their daily work, more precisely there's only one sure thing and that is change. In international practice, this phenomenon is expressed in a mosaic word: VUCA.

VUCA expanded includes:
* '''Volatility'''
* '''Uncertainty'''
* '''Complexity'''
* '''Ambiguity'''

Managers and employees in companies need to cope with these four circumstances on a day-to-day basis and provide appropriate answers and solutions to questions related to these categories. Under such circumstances, it is essential to have a top leadership that is ready, able, and motivated towards change. The hardest task for a manager is to overcome resistance against change. The shorter the time, while resistance is present in a company's management the more effective, is the management of the change process.

[[File:Vuca.png|400px|thumb|right|]]

===The background and pitfalls of change===

Resistance and the elimination of resistance to organizational change are in the focus of Lewin's force-field theory. The psychologist and researcher during the development of his theoretical model used a so-called Open-System Theory, in relation to organizational behavior. This theory compares organisms to organizations/companies and enterprises, it says that they behave the same, meaning they all try to survive and establish, then maintain a relative balance. In biology this condition is called homeostatic condition, when the living organism is constantly and sufficiently adapting to external and internal changes and conditions, thus maintaining biological stability, which is one of the most important characteristics of living organisms. Lewin thought that the same is true to the business sector, and in the name of successful projects, we need to set a balance, all the factors that support change must be strengthened and the factors that oppose it, weakened. There can be innumerable indicators of change (eg. technological advancements, market urges). In my practical example, the transformation of the organization was needed due to certain features weren't highlighted in the company, and certain management functions were in the subordinate role compared to others.

Every time a change happens, it is very important that the proper preparatory analyzes and process plans are ready and suited to the specific situation before the transformation begins. We need this to prevent and eliminate the resistances mentioned in the Lewin model, the first steps should try to get rid of the forces that try to curb the change until a critical mass appears. For this, however, is crucial to know the root cause of the possible breaking forces.

===Communication strategies that help change===

In practical situations, Lewin's three-step model was created with the help of leaders and change management professionals. We can say that the most common inhibitory effect of the change is the pursuit of permanence and security by the people. In addition to security, those working in the organization are also sometimes afraid of their own success, as they believe that if a new structure emerges as a result of the change, where new managerial functions are highlighted or introduced, individual failure also increases, which everybody wants to avoid. This is why one of the most important tools for eliminating barriers is the communication strategy of the change process itself. It is no coincidence that this is a vital element of the preparatory phase of a change.

In the case of my practical example presented below, the key to the communication strategy was creating a communication "scenario" that is broken down by day, including:

* When managers consult with which employee or sector
* When and with what content the coordination will take place
* What channel through the communication takes place
* To whom and when will the information process progress

The positive nature of an organizational atmosphere is a key factor to avoid and managing change, it allows employees to look at change without fear, and with openness. Quality information could be an organizational response to the following questions:

* When and what will happen?
* What is the background of change
* What are the benefits of the change for the employees and for the company?

The communication that is able to support change management is successful and effective if it is not necessary for the employee to guess what will exactly happen to them or with the organization. The worst-case scenario is when the employees don't get information on time, or a more dangerous case is the appearance of disinformation. In these cases, the lack of information, due to human nature, will be supplemented by imagination, which can create unacceptable situations in reality.

===Change management in practice using the Lewin-model===

In our case, the communication method used by the management of the company in our practical example was, in addition to informing, the solution recommended by Lewin, ie. the partial involvement of the employees in the decision making. The management held a key employee forum, where the whole plan of the change has been presented, this step is of course preceded by several smaller group workshops. The management of the company at the meeting has presented three possible versions of the structure and procedure, of how the organization planned to operate the following business year. For all three versions, in addition to the factual description, -pro and - con arguments were added with detailed economic calculations. Seemingly the most effective model was the one that involved giving the task to the staff of helping with compiling their individual and organizational objectives for the coming period. For example what they want to achieve in the company, beyond what the senior management strategically designated. Of course, the organizational goals set by staff were incorporated into the forthcoming communication materials and the organization openly thanked valuable employee contribution.

Kurt Lewin created a three-phase model for managing change, that has a potential to stand ground in today's competitive sphere and help the change process effectively. The three phases are:

# First phase: Defrosting
# Second phase: Change or move
# Third phase: Solidification or re-freezing

Symbiosis of change and project management

2022-03-25T20:53:32Z

S213053: /* The backgrounds and pitfalls of change */

Symbiosis of change and project management

2022-03-25T20:53:05Z

S213053: /* Communication strategies that help change */

Symbiosis of change and project management

2022-03-25T20:49:23Z

S213053: /* Communication strategies that help change */

Symbiosis of change and project management

2022-03-25T20:27:15Z

S213053: /* The backgrounds and pitfalls of change */

Symbiosis of change and project management

2022-03-25T19:38:45Z

S213053: /* The backgrounds and pitfalls of change */

Symbiosis of change and project management

2022-03-25T19:21:36Z

S213053: /* Introduction to the VUCA model */

Symbiosis of change and project management

2022-03-25T19:16:37Z

S213053: /* Introduction to the VUCA model */

Symbiosis of change and project management

2022-03-25T19:03:56Z

S213053: /* Introduction to the VUCA model */

Symbiosis of change and project management

2022-03-25T19:02:54Z

S213053: /* Introduction to the VUCA model */

File:Vuca.png

2022-03-25T19:02:20Z

S213053:

Symbiosis of change and project management

2022-03-25T12:57:21Z

S213053: /* Abstract */

Symbiosis of change and project management

2022-03-24T21:38:17Z

S213053: /* Performance */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. Weáve got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,2001, 2005)'''.

In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''.

Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====
Performance as an aspect of success is hard to measure, this way in the referenced studies they gave rather low importance to it regarding success factors. It is mentioned that the introduction of appropriate performance targets and properties is difficult, and the tendency shows that they rather focus on quantifiable measurements than take into account people-oriented "soft" success factors. Like individual or group behavior and motivation. Change management is not applied in these cases at all or only insufficiently. In practice, projects usually start without change management, and sooner or later they reach a point where the lack of identifying a needed change or the resistance from the stakeholders significantly hampers the continuation of the project. In this case, a cry for help is made towards change management, a framework is needed to save the situation.

==Change management in practice==
===Introduction to the VUCA model===

Symbiosis of change and project management

2022-03-24T21:20:48Z

S213053: /* Stakeholders */

Symbiosis of change and project management

2022-03-24T21:19:55Z

S213053: /* The importance of change management in relation to project success */

==Abstract==
In the last few decades, the value of project management was a bit misunderstood. Weáve got to a point where we label as project management different processes or activities that are actually not in this field. Projects can be really different in terms of their scale, their funding, and it really depends on what happens within their corporate framework. We can safely assume that the success of a project rests on how well it is prepared, how receptive are the ones who try to achieve it, and how positive or negative is the attitude towards the specific project. A lot of times these properties are more important, than the actual professional competence of the worker, employee, or manager. In this article, I would like to investigate the necessities and needs of change management in relation to project management, since in practice these too cannot exist without each other's logical background.

If we look back 10-15 years in the past, in the operation of big companies changing to new IT systems and computers was great challenge management wise. And change happened under the umbrella of project management. How did this actually happen?

The CEOs of the companies had big expectations regarding the use of computers instead of human-centered work. They wanted shorter intervals between the ordering and payment processes, a decrease of the administrational staff, or better customer service. However to implement these technologies they needed to link the introduction of IT systems to a wide range of organizational changes '''(Bingi – Sharma – Godla, 1999)'''. Although the employees of the companies looked at this conversion in a bad way, they felt that this is an obstacle to their daily work habits or as a restriction to it. At this point, we can see how the management of change is as equally important as the project itself.

__TOC__

==The success criteria of projects==
===Reasons why a project could fail===

Since in practice, the realization of a lot of projects fails, we should clarify what's the success criteria of a typical project. A project is successful if:

* It's considered finished within a specified time frame
* Uses a budget from within a specified spending limit
* Fulfills the intended purpose

At the same time, a project is considered unsuccessful if:

* Before or during the implementation phase, it is interrupted or stopped
* It reaches the implementation phase but doesn't fulfill its purpose

'''(Fitz-Gerald – Carol, 2003)'''

Because of the high number of unsuccessful projects, we should look at the reasons behind it more deeply:

* The strategic goals of the project weren't clearly defined, Not just the goals, but the expectations of the project weren't clear enough.
* The top of the management is not working with the defined system of the project, the responsible leaders do not see the essential and key changes which are introduced and are not actively monitoring the implementation process.
* The project management underestimates the scope, size, and complexity of the project:
** Unrealistic timelines are made, and communication is not sufficient for the amount of the expectations
** There is no consistency between business expectations and the chosen system
* The organization is not behind the change:
** Employees naturally seek the status quo and do not feel the need for change
** Workers are afraid of the new system, maybe it can make their work more difficult, or maybe reduces the place and value in the company, or even makes their work obsolete or unnecessary.
* The project team is not skilled enough
* Users are unable to operate the new system properly, due to a poor design or insufficient training
* Data quality is not ensured, inaccurate data leads to loss of confidence towards the project. Employees set aside the new system and get back to the old, reliable one.
* After organizational changes, performance indicators are not fitted properly
* The involvement of different supply sites for the project has not been adequately addressed
* Technical problems with implementation difficulties

'''(Umble - 2003)'''

===Success criteria===

Because most of the studies and articles overlap or sometimes complement each other in identifying the critical success factors, six higher categories have been developed, that contain different success criteria.

These six higher categories consist of:

# '''Top leadership:''' - which has to have total commitment and vision as critical success criteria
# '''Project management''': - clear project goals, consistent team members, enough and correct data, planning and control
# '''Organization''': - optimization of business processes
# '''Stakeholders:''' - communication, cooperations, and involvement, information, and education
# '''Technology:''' - choosing a program or project package, implementing that into the used system, data handling
# '''Performance:''' - performance limit and criteria, descriptive and incentive system

'''(Umble - 2003)'''

We can see that the success of different projects depends on lots of different factors. However, to what extent they are related to change management we need to look a little deeper into the importance of change management at different project phases.

==Change management in a project==
===The basis of change management===

The concept of change management is difficult to determine because it is used for different situations and the scale ranges from general change to change in the preparation phase or maybe change in the sales. Also, the literature on the topic is dominated by practical experiences and an integrative, theoretical frame is missing.

This problem also exists in the context of change management related to project management. In order to have a uniform interpretation of the concept, the following definition is considered relevant:
Under change management, we mean the management of in-depth planned changes in a company. It is primarily about people, while the aspects of the subject are covered by project management. Change management targets the change process, from start to the final evaluation, and does not make statements about possible contents.

'''(Kohnke - Bungard - Madukanya, 2005).'''

[[File:Changemanagement.jpg|550px|thumb|left|]] Moving forward with the ideas from the '''Success criteria''' chapter, the critical success factors for '''"Organization"''' and '''"Technology"''' are clearly in the content/subject level in the purpose of implementing a project. Meanwhile the '''"Top leadership"''', '''"Stakeholders"''' and '''"Performance"''' categories represent the people oriented side of the process.

===The importance of change management in relation to project success===

Studies have shown that change management has significant importance in the implementation of projects. In the following sections, I would like to summarize the key findings related to three people-oriented categories of success factors.

====Top leadership====

Different studies have rated top management as the most important of the critical success factors. In project implementations, usually not just a large area of the company's assets are affected, but also the ones who want the integrate the change. To make the necessary changes the support of the senior management is essential. Support is not just about providing the needed resources for the project, but also for the change process itself. It is not enough to be a member of the top management, you have to have the responsibility and possibility of decision approval, covering all areas concerned. According to Nah's (2003) study, the vision of the project, compared to the other success factors only is in the middle importance-wise. But vision plays a very important role, as it gives direction to change. '''(Nah's, 2003)''' In addition, vision provides a long-term perspective. Implementing projects are usually long-term plans, that can take up several years, especially if there are cultural changes that come with it. A high problem area is also the short-term perspective of the management and their focus on quick solutions which can hinder the success of the project. Deep changes take time, and this time must be given to the company by the top management. '''(Kohnke, 2005)'''

====Stakeholders====
A really common problem area is that the need to manage a change was not recognized at all or in time. The implementation of new systems leads to deep changes within a company's affected sectors. The affected employees perceive this differently, leading to insecurity, fear, and resistance, which all could negatively affect the success of the project '''(Aladwani,
2001, 2005)'''. In practice, this resistance leads to diversion from the necessary changes, and in the end, only the old processes are mapped into the "new system". '''(Aladwani, 2005)'''. Dismantling this resistance and applying a new way of working and system acceptance is the most important task of change management. In a company where employees share common values and goals and are open to change, the project is more likely to succeed. '''(Nah- Zuckweiler - Lau, 2003)'''.

====Performance====

Symbiosis of change and project management

2022-03-24T20:57:02Z

S213053: /* The importance of change management in relation to project success */

Symbiosis of change and project management

2022-03-24T20:28:51Z

S213053: /* The basis of change management */

Symbiosis of change and project management

2022-03-24T20:25:48Z

S213053: /* The basis of change management */

Symbiosis of change and project management

2022-03-24T20:24:40Z

S213053: /* The basis of change management */

Symbiosis of change and project management

2022-03-24T20:22:58Z

S213053: /* The basis of change management */

Symbiosis of change and project management

2022-03-24T20:16:41Z

S213053: /* The basis of change management */