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
Be aware of unintended consequences
Be aware of unintended consequences I’ve written before that every decision involves a trade-off. When […]
Positive change is harder to see
Positive change is harder to see Humans are wired to see negative change because we […]
MVP: Minimum Viable Product
MVP: Minimum Viable Product In product development there is a concept known as MVP, or […]
You always need a reason for collecting data
You always need a reason for collecting data When you ask for data from someone […]
If you’re unhappy, speak up!
If you’re unhappy, speak up! My clients will often ask me something along the lines […]
Does it advance the mission?
Does it advance the mission? Because associations are mission-driven, everything you do should be seen […]
How should you start a new data project?
How should you start a new data project? When you’ve got a new data project […]
A Data Integrity Report…for Reports!
I’ve written elsewhere about the value of data integrity reports. But one of the most […]
Simple rules for complex systems
Simple rules for complex systems I first heard the phrase “simple rules for complex systems” […]
Accentuate the positive
Accentuate the positive I’ve written before about the importance of database public relationsand celebrating success. I’ll add […]
