Add one, remove one
In the world of home-organizing, there's the "one in, one out" rule. Simply put, for every new item that enters your home, one similar item must leave, helping to maintain a constant level of possessions and prevent clutter accumulation.
This would be a great rule for database managers when considering adding new fields of data to collect!
If staff wants to add a new field to collect a new data point, the first question is "Which data point/field are we going to remove?"
I'm only half-joking. Too often I see my clients adding new fields of data to collect while simultaneously not keeping up with the other data points they are supposed to be already collecting.
So when you think about adding a new field, ask yourself: "Are there other data fields we could remove while we're adding this new one?"
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 […]