A system change requires a culture change
By its very nature, when you introduce a new enterprise-wide system like a new AMS, you are going to have to change the culture of your
organization in order to best leverage the new system.
A simple example: When I work with my clients on selecting a new AMS, they often tell me that only one or a few staff use the current system. "It's too difficult for any of us to use" or "Cindy knows the system best, so we rely on her to manage all the data."
In these examples, the current culture is one where very few staff use the system. But presumably you're changing systems, in part, so that more staff can/will use the system. Whether you realize it or not, that's a change in culture.
A new system is very likely to change many things about your
organization's culture, so you need to be prepared for that. There are entire books written on how to change your culture, so I won't go into that here. But if you really want to get the most from a new AMS, you need to acknowledge that the culture will change, and you need to be prepared to drive that culture change in the most positive way possible.
Wes's Wednesday Wisdom Archives
It’s easy to collect; it’s harder to manage The beauty of today’s highly configurable AMS …