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
You don’t have to automate EVERYTHING to be successful
You don’t have to automate EVERYTHING to be successful I was discussing a data management […]
Technology won’t solve your process problems
Technology won’t solve your process problems Over the past few years I’ve watched as many […]
“Screen noise” is a real thing. You might be able to fix it.
“Screen noise” is a real thing. You might be able to fix it. One of […]
Success Starts at the Top
Success Starts at the Top I recently had a conversation with an association staffer who was […]
Who are you bringing along?
Who are you bringing along? Last week I had the opportunity to attend the AWTC […]
Write it down!
Write it down! If you’re in the market for a new AMS (or any new […]
Why “weeding the garden” is so important
Why “weeding the garden” is so important One of the most important activities for maintaining […]
It’s time to stop excusing association professionals
It’s time to stop excusing association professionals I worked in associations for nearly 10 years, […]
More demos is not better
More demos is not better When I work with clients on selecting a new system, […]
The database owner should be “passionate”
The database owner should be “passionate” I’m frequently asked by my clients: “Who should we […]
