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
Maintenance isn’t sexy
Maintenance isn’t sexy I remember reading once long ago that one of the reasons our […]
“Will I still have a job when this is done?”
“Will I still have a job when this is done? While working with a client […]
Evolution, not revolution
Evolution, not revolution I don’t recall where I first heard it many decades ago, but […]
The power of the users’ group
The power of the users’ group Recently in an online users group forum for an […]
Who is your data evangelist?
Who is your data evangelist? I was recently talking with a client of mine about […]
Who is your data evangelist?
Who is your data evangelist? I was recently talking with a client of mine about […]
Ratio of Data to Errors
Ratio of Data to Errors One of the elements of a good data governance plan […]
Back to basics
Back to basics Over the past couple of years I’ve noticed that some AMS vendors […]
Your people matter
Your people matter I’ve written many times about how people, process, and technology have to […]
We remember moments…
We remember moments… “We do not remember days, we remember moments.” – Cesare Pavese Another […]