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
Inertia Contributes to Bad Data
Inertia Contributes to Bad Data Without knowing anything about your organization or its data, I’d […]
What are you doing with new contacts?
What Are You Doing with New Contacts/ I was very interested to read in a […]
Be Aware of Selection Bias
Be Aware of Selection Bias I wrote recently about the mistaken perception of older members […]
Some Things Just Take Time
Some Things Just Take Time I learned recently that an elephant’s gestation period is 18 […]
Sometimes It’s the Least Bad Choice
Sometimes It’s the Least Bad Choice Just like in life, sometimes when we’re making technology […]
Our Members Aren’t Tech Savvy
Our Members Aren’t Tech Savvy Having worked now in the association space for more than […]
Motion vs. Action
Motion vs. Action One key to successful data management is understanding the difference between motion […]
There is ALWAYS a Trade-off
There is ALWAYS a Trade-off I’ve written many times about trade-offs (you can read a […]
Little by little, a little becomes a lot
Little by little, a little becomes a lot “Little by little, a little becomes a […]
Why do we treat data management differently?
Why do we treat data management differently? A recent post on ASAE’s community read: “Looking […]
