I hear and read about resistance to change frequently. Most of the time it is referred to in a negative light or as an inherent human weakness. Wouldn't it be more productive if we focused on the “Change” itself rather than the “Resistance”?
We have all been on the receiving end of change that didn’t work out well for us, so it is natural to be apprehensive. If we think back to one of those “bad” changes, can we think of ways the change could have been approached that would have made it a better experience for the both the leaders and the participants?
Resistance to change can often be prevented – and I don’t mean through the use of force, quite the opposite. Just a few ways to improve the adoption of change is through the application of:
- betas
- simplified learning tools
- prototypes
- pilot trials
- demonstration
- user experience observation and testing
- involvement
The general expectation is that change should be “good”. A common experience is that it isn’t. If change wasn’t actually “good”, we wouldn’t constantly be trying to introduce it. We should probably put more effort into making sure everyone that is impacted by the change understands the benefits and agrees that it actually is “good”. If they did, we probably wouldn’t be experiencing so much resistance.
Other posts about keys to successful change implementation