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
“We run the report three times and get three different results.”
“We run the report three times and get three different results.” “We run the same […]
How do you know if you’re making progress?
How do you know if you’re making progress? We all want to improve our data management, […]
Don’t move too quickly OR too slowly
Don’t move too quickly OR too slowly This may sound like a big “duh!” but I’ll […]
“Your current habits are perfectly designed to deliver your current results.”
“Your current habits are perfectly designed to deliver your current results.” “Your current habits are […]
There is value in just going through the exercise
There is value in just going through the exercise I was working with a client […]
Daylight savings and business rules
Daylight savings and business rules This past Sunday, most of the US observed Daylight Savings […]
It’s always about priorities
It’s always about priorities No matter the size or type of technology project, you will […]
Only one can be best
Only one can be best One of my (many) pet peeves with software vendor marketing […]
Seek to simplify
Seek to simplify When I work with my clients on system selection or implementation, one […]
Some problems are not problems
Some problems are not problems “A problem with no solution is not a problem, it’s […]
