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
The vaguer the question, the vaguer the answer
The vaguer the question, the vaguer the answer As the old saying goes, the devil […]
The best choice given the information you have
The best choice given the information you have “Hindsight is 20/20” is a cliché because, […]
Action isn’t the same as progress
Action isn’t the same as progress I’ve written before that not taking action is an […]
Start with the end in mind
Start with the end in mind Like so many, I probably first heard the phrase […]
It’s quiet in here…maybe TOO quiet…
It’s quiet in here…maybe TOO quiet… One of the truisms of data management is that […]
It’s ALWAYS about expectations
It’s ALWAYS about expectations The headline reads: “Tesla sets record for vehicle deliveries, an increase […]
It’s hard to get UNangry
It’s hard to get UNangry I often emphasize to my clients the importance of testing […]
Some history IS important!
Some history IS important! When I’m advising clients on data conversion (moving data from one […]
“Many mickles make a muckle.”
“Many mickles make a muckle.” “Many mickles make a muckle.” – George Washington Apparently, this […]
It’s easy to collect; it’s harder to manage
It’s easy to collect; it’s harder to manage The beauty of today’s highly configurable AMS […]
