Don't ask for what you don't need!
Recently I received a bill from a doctor's practice. The bill provided a website for paying online. So I went to the website and the first thing it asked me for is my account number. This is good because the bill they sent me has my account number on it.
So I entered the account number, and the next thing it asked me for was my name. Hmmmmm, I already entered my account number, why do you need my name? But I dutifully entered my name.
Then it asked me which doctor I had seen (a required field). Wait a minute. You sent me the bill. Why do I have to tell you all of this just to pay?
There is a lesson here for anyone who manages data. The problem with asking questions of your customers that you should already know is not only is it annoying to the customer, but it also leads the customer to think, "Do they have any idea what's going on?" The customer quickly loses trust in your ability to manage their data.
So when you're collecting data online, be careful to only ask for the information you need. And never ask for data that you already should have.
![]()
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 […]
