Ownership is required
When asked for the most common reason AMS implementations fail, I typically respond "lack of testing." But implementation is only the first step in the process. Long-term success for the AMS requires ownership.
What do I mean by ownership? I mean that someone (or a team) internally has actual responsibility for the long-term success of the AMS. Too often what happens after implementation is each department takes ownership of only its own area, which ultimately leads to silos and, longer-term, to a system that is no longer working at optimal levels.
Once you're past implementation, someone (or a team) has to have responsibility for the ongoing maintenance and support of the system. If your organization doesn't or can't have a single individual do this, create a team of representatives from key areas (typically membership, events, and finance, along with others) that are responsible for working together to keep things on track. (Click here to read more about these teams.)
But whether it's one person or a team, the "owner" has to be clearly identified and has to focus on the long-term success of the system. The system will not take care of itself!
![]()
Wes's Wednesday Wisdom Archives
Perfection is expensive (in fact, it’s not possible!)
Perfection is expensive (in fact, it’s not possible!) “Perfection is expensive. The last 5 percent […]
AI is a journey, not a destination
AI is a journey, not a destination Lately I’ve noticed a lot of associations talking […]
Action produces information
Action produces information “Action produces information. If you’re unsure of what to do, just do […]
Why a single source of truth is so beneficial…
Why a single source of truth is so beneficial… The holy grail of data management is […]
Just because you can, doesn’t mean you should
Just because you can, doesn’t mean you should I’ve worked in and with associations for well […]
Data doesn’t need to be perfect to be useful
Data doesn’t need to be perfect to be useful “Your data doesn’t have to be […]
Don’t just clean data, clean reports and queries
Don’t just clean data, clean reports and queries One of the reasons I exhort my […]
Don’t forget, your staff have day jobs…
Don’t forget, your staff have day jobs… The vast majority of my work is finite […]
Beware the automated “How did we do?” trap!
Beware the automated “How did we do?” trap! One of the downsides of technology is […]
Hindsight is 20/20
Hindsight is 20/20 I’m currently working with a client that is moving from their legacy […]
