Evolution, not revolution
I don't recall where I first heard it many decades ago, but the phrase "evolution, not revolution" always struck me as one key to understanding how data management really works. (I heard the phrase in relation to something else but naturally I found a fit for data management!)
It's really quite simple: When it comes to improving the quality of your data, there are no magic bullets that will bring dramatic improvements (revolution). Improving your data quality takes time (evolution). Here are just a few examples of what that might look like:
- Finding potentially bad data through data integrity reports.
- Seeking out and eliminating duplicate data.
- Making business rules as simple as possible.
None of these activities executed once (revolution) will make a huge change. All of these activities done consistently over time (evolution) will dramatically improve the quality of your data.
Consistency and patience wins the day. Remember, it's evolution, not revolution.
![]()
Wes's Wednesday Wisdom Archives
Don’t be so lazy…
Don’t be so lazy… One of the things that attracted me to the software world […]
Don’t try to do everything at go-live
Don’t Try to do Everything at Go-live When implementing a new AMS, there is a […]
Make sure your system has broad support
Make sure your system has broad support An AMS vendor pointed out to me recently […]
You have to have the right people in place
You have to have the right people in place This may seem obvious, but I’ll […]
Ask “What” not “Why”
Ask “What” not “Why” As a consultant, one of my favorite questions to ask my […]
Engagement is measured by the customer
Engagement is Measured by the Customer I’ve written a bunch about measuring engagement in the past. (Click […]
Yes, you do have a process for that
Yes, you do have a process for that When I work with clients on pretty […]
“Correct your mistakes before they become your habits”
“Correct your mistakes before they become your habits” Yet another great quote from James Clear: “Correct […]
Sometimes it’s a process issue
Sometimes it’s a process issue When I work with clients on developing a needs list […]
First ask: “How will I use this data?”
First ask: “How will I use this data?” Whether it’s during data conversion, adding a […]
