Geyto Research · Juan Ferreiro · Market note · · 2 min read

Change management and technology adoption. Where they overlap and where they differ

Change management models help prepare people. Technology adoption also calls for adjusting the initiative and looking at the actual work.

In brief: change management and technology adoption overlap, but they are not the same thing. Change management models help prepare people: communicating, building commitment, training, reinforcing. Technology adoption adds two questions: whether the work actually changed, and whether the initiative itself needs adjusting for the change to hold.

What change management models contribute

In 1995, John Kotter published an influential article on why transformation efforts fail. He proposed a sequence of steps: establish a sense of urgency, form a coalition, communicate a vision, remove obstacles, secure early wins and anchor the change in the culture.

The ADKAR model, developed by Jeffrey Hiatt at Prosci, looks at change from the individual's point of view. It describes five stages: awareness of the need, desire to take part, knowledge of how to change, ability to do it and reinforcement to sustain it.

Both models bring order to something important: change requires attention to people, not only to the project. When that work is not done, the project is left to each person finding their own way.

What remains to be solved

They assume the change is well defined. The models work to get the organization to the future state. By design, they do not ask whether that future state, as designed, is viable in each place where the work happens.

They look at the person more than at the task. ADKAR describes the individual transition very well. Adopting a technology also depends on shared routines, handoffs between areas and conditions of the job that no single person controls.

In practice, the plan often closes at launch. The models do address sustaining change: ADKAR includes reinforcement, and Kotter calls for anchoring it in the culture. But in many projects the change plan ends once people have been informed and trained, and the period after launch, when real cases appear, gets less attention than it needs.

The technochange proposal

M. Lynne Markus used the term technochange for projects in which technology is the means to change how an organization works. Her argument: these projects fail when they are managed only as technical projects, and also when they are managed only as organizational change. They need both at once, and in particular they need the solution to be revisited as it is implemented.

Two sides that can change

The underlying difference is one of symmetry. Change management tends to see the organization as the side that has to adapt. Technology adoption looks at the relationship between what the initiative demands and the capacity available to sustain it. When the two do not match, you can work on the organization, on the initiative or on both: its sequence, its timing, what it asks for first.

What to do with this

  • Use change management models for what they do well: preparing and supporting people.
  • Add the question they leave out: is what we are asking for viable where the work happens?
  • Extend support into the period after go-live.

More in Both sides can change and in our approach.

Geyto Research publishes essays, evidence reviews and market notes on what happens after go-live.

Frequently asked questions

What is the difference between change management and technology adoption?

Change management deals with preparing and supporting people through a change. Technology adoption looks at whether the work actually changed and whether the change holds, and recognizes that the initiative may also need adjusting.

What is ADKAR?

It is a Prosci model, proposed by Jeffrey Hiatt, that describes individual change in five stages: awareness, desire, knowledge, ability and reinforcement.

What is technochange?

It is the term M. Lynne Markus used for projects in which technology is the means to change how an organization works. Her argument is that these projects need to combine technical management with the management of organizational change.

Sources

  1. Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59–67.
  2. Hiatt, J. M. (2006). ADKAR: A Model for Change in Business, Government and Our Community. Prosci.
  3. Markus, M. L. (2004). Technochange management: using IT to drive organizational change. Journal of Information Technology, 19(1), 4–20.

Share