Write it down!
If you're in the market for a new AMS (or any new technology that has a breadth of functionality, e.g., LMS, marketing platform), before you start shopping and looking at products, you need to write down what you want out of the system.
I'm surprised at the number of organizations I've spoken with over the years who tell me they've been shopping for an AMS, and when I ask them if they've got some written document that outlines the functionality they're seeking, they respond with: "No, we have it in our heads."
There are many reasons to document your needs, but here are the two biggest:
- Documenting your needs allows you to communicate to the vendors exactly what you're expecting from their product. Documentation allows you to avoid the inevitable comments from vendors like "We didn't know that's what you wanted."
- Documentation gives you a "checklist" during implementation. If you've documented what you need, throughout implementation you can refer back to it to answer the question: "Are we implementing what we wanted?"
Documentation helps us avoid the need to "read minds." So whether it's an AMS, an LMS, a new email system, or any other technology, whatever your needs are... WRITE IT DOWN.
![]()
Wes's Wednesday Wisdom Archives
Two tips for data conversion
Two Tips for Data Conversion I’ve written a lot about data conversion over the years […]
Who should “own” the database?
Who should “own” the database? One of the most common questions I get from my […]
What makes you weird?
What makes you weird? When I work with clients on selecting a new association management system, one […]
Why “AMS Consortiums” Don’t Work
Why “AMS Consortiums” Don’t Work About once a year I will get a call from […]
Your vendor will disappoint you
Your vendor will disappoint you I follow politics as a hobby. A past publisher from […]
Learn how to lose
Learn how to lose “Winning is great, sure, but if you are really going to […]
Ownership is Required
Ownership is required When asked for the most common reason AMS implementations fail, I typically respond […]
It’s all relative…
It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with […]
Eliminate to optimize
Eliminate to optimize So much of data management is habit (both good and bad) which is […]
For data governance, ask “Why?”
For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data […]
