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
Perfection is expensive (in fact, it’s not possible!)
Perfection is expensive (in fact, it’s not possible!) “Perfection is expensive. The last 5 percent […]
AI is a journey, not a destination
AI is a journey, not a destination Lately I’ve noticed a lot of associations talking […]
Action produces information
Action produces information “Action produces information. If you’re unsure of what to do, just do […]
Why a single source of truth is so beneficial…
Why a single source of truth is so beneficial… The holy grail of data management is […]
Just because you can, doesn’t mean you should
Just because you can, doesn’t mean you should I’ve worked in and with associations for well […]
Data doesn’t need to be perfect to be useful
Data doesn’t need to be perfect to be useful “Your data doesn’t have to be […]
Don’t just clean data, clean reports and queries
Don’t just clean data, clean reports and queries One of the reasons I exhort my […]
Don’t forget, your staff have day jobs…
Don’t forget, your staff have day jobs… The vast majority of my work is finite […]
Beware the automated “How did we do?” trap!
Beware the automated “How did we do?” trap! One of the downsides of technology is […]
Hindsight is 20/20
Hindsight is 20/20 I’m currently working with a client that is moving from their legacy […]