The three "buckets" of contact data
Broadly speaking, when collecting data on contacts (individuals or organizations), there are three "buckets" of data being collected:
- Contact information (name, address, phone, email)
- Transactional information (stuff they've purchased)
- Demographic data (information about the individual or organization, e.g., lines of business, areas of interest, professional status, etc.).
Of these three, the most difficult to manage is demographic data. For demographic data you have to answer three questions:
- What data will you collect?
- How will you use it?
- How will you maintain it?
Working with my clients, I often see that question #1 is easily answered, but they struggle with questions 2 and 3.
And here's the thing: If you collect demographic data, you really need to be able to answer both questions 2 and 3 before you start collecting that data. Because if you don't, I can almost assure you that the data you collect now will become stale in very short order. Most demographic data changes over time. And since it changes over time, you have to have a process in place to continually update it (question 3 above).
And equally important, you need to have a reason to collect the data (question 2) that is more than "That would be interesting to know."
So ask yourself: for all the demographic data we collect, do we have an answer to questions 2 and 3? And if not, should we be collecting that data at all?
![]()
Wes's Wednesday Wisdom Archives
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 […]
More on Meetings
More on Meetings I’ve written before about the importance of making sure your meetings are […]
