How can an organization avoid the pitfalls of change that occur and sometimes cause CMS projects to fail?
EH: The resistance to change sometimes has its roots in the fact that workers have spent a great deal of time and personal energy working around problems in the old system, and don’t want to let go of that because they are afraid that what they are getting isn’t any better than what they already have. So the key to taking away fear is to give information. Not just about what is going to happen, but how it is going to impact people. I think one of the biggest mistakes companies make is to downplay the fact that change is going to impact people and it may even impact people to the extent that some individuals won’t be able to make the change. It’s always going to be a little disruptive, but the plus side is that humans are very good at adapting to change. If we weren’t we’d still be living in caves. But it’s a process and workers will probably need some help making the change. The one thing a company cannot do is ignore the issues and hope they’ll go away; they won’t. When the project is
