The Dog That Doesn't Bark

Change is about hearts and minds. Most advice focuses on the heart - but we need to address the mind if we are to address the rational causes of resistance and make it work.

An axiom of much change management advice is that people resist change. Regardless of how true this is in general, in business many of the problems of change are laid at the door of people resisting the change.

This in turn has created a mini-industry of change-management professionals offering advice almost all of which is concerned with overcoming resistance. Workshops, town hall meetings, posters, stakeholder management, mugs, force-field analysis and a whole panoply of consultant jargon, academic theorising and a panoply of tools, instruments and methods to 'engage people', 'secure buy-in' and 'obtain senior management commitment'.

And almost all of it barking up the wrong tree.

The issue is not overcoming resistance. It's about understanding the causes of resistance and removing them.

Most of the time, people resist change because the work environment in which they find themselves makes resistance a reasonable response to change. In other words, they resist change because the business environment encourages them to do so.

To give a simple example: if, say, we want middle managers to use a central recruiting process rather than go to their own local network of recruiters, then we will see rational resistance if the new process compared with current local practice is slower, more cumbersome, less flexible, has higher impact on local budgets, is less trustworthy or reduces the manager's choice over whom they hire. If I am locally measured on these things, reducing my ability to meet these metrics will, of course, increase my resistance.

No amount of persuasion, engagement or group working will change this logic. To change the logic, we need to change those aspects of the work environment that make resistance a correct and rational position.

So: if you want to make change happen (rather than talk to people about change), here are a few things to consider. Identify three or four places in the workflow of your new way of working where the quality of the process is visible.

Now change the environment round these three or four places by implementing answers to questions like these. What triggers the new way of working? What is in place to make it easy, practical, quick and aligned with relevant local metrics? What standards of performance are expected? What information do people get in real time about how well they are doing - and who notices?

Have the business put in place specific actions to reduce specific causes of resistance, real-time, in key places, as people work in the new ways. (And conversely, put in place things to make working the old ways harder).

Don't overanalyse, don't try to change everything (as I said, three or four places only) and don't work too hard to secure 'buy-in'. Try making operational changes quickly and seeing what works in terms of performance. When things work, the performance changes. 'Acceptance' is secondary.

You should find quite quickly a cluster of focused specific work environment changes that lead to people working differently. Document these and implement them pragmatically if you need to to roll the change out further.

While efforts to overcome resistance through persuasion, communication and engagement are good things, experience - and logic - show that you will get a better outcome if you adjust the work environment instead: this is the dog that doesn't bark.

- Mike