Organizational Change Models

This content is syndicated from Agile Complexification Inverter by David Koontz. To view the original post in full, click here.

A short little comparison of Organizational Change models.

There is Kurt Lewin's 3 stage model:  Unfreezing, Change, Freeze.
See: Frontiers in Group Dynamics (1947).
A change towards a higher level of group performance is frequently short-lived, after a “shot in the arm”, group life soon returns to the previous level. This indicates that it does not suffice to define the objective of planned change in group performance as the reaching of a different level. Permanency of the new level, or permanency for a desired period, should be included in the objective. -- Kurt Lewin
Then there is the most well known:  John Kotter's 8 Steps model.
  1. Establish a sense of urgency.
  2. Create the guiding coalition.
  3. Develop a vision and strategy.
  4. Communicate the change vision.
  5. Empower employees for broad-based action.
  6. Generate short-term wins.
  7. Consolidate gains and produce more change.
  8. Anchor new approaches in the culture.
These were developed from Kotter's study of failed organizational changes.  He found these typical failure modes:

  • Allowing to much complexity
  • Failing to build a substantial coalition
  • Understanding the need for a clear vision
  • Failing to clearly communicate the vision
  • Permitting roadblocks against the vision
  • Not planning and getting short-term wins
  • Declaring victory too soon
  • Not anchoring changes in corporate culture
From:  “Force for Change: How Leadership Differs from Management“  by John Kotter.

Another model is the ADKAR model for individual change management by Prosci. This is a 5 step model.
  1. Awareness – of why the change is needed
  2. Desire – to support and participate in the change
  3. Knowledge – of how to change
  4. Ability – to implement new skills and behaviors
  5. Reinforcement – to sustain the change
Described in Jeff Hiatt's (2006) book ADKAR: a model for change in business, government and our community.

Comparing these 3 well know models we see a pattern.  Change is hard, people are the resistance force and the driving force for change.  The number of steps in the model are less important than the full understanding that change is a process.

One of the best models for understanding that change is a process is William Bridges's book Managing Transitions: Making the most of Change.  In his model we have: The Ending, Neutral Zone, New Beginning.  The key is viewing change as a transition process.

Leave a Reply

What is 6 + 6 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”