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
It’s all about managing expectations
It’s all about managing expectations I placed an order online on a Friday and the […]
Experience is the best teacher
Experience is the best teacher Experience is the best teacher. Every one of us has […]
Don’t ask for what you don’t need!
Don’t ask for what you don’t need! Recently I received a bill from a doctor’s […]
It is never done – so celebrate!
It is never done – so celebrate! A client of mine recently had their official […]
MDR (Minimum Data Required)
MDR (Minimum Data Required) I’ve written about minimum viable product (MVP) in software development in the […]
Simpler and Faster is Better
Simple and Faster is Better Earlier this week I was fortunate enough to attend a […]
Patience and grace
Patience and grace A past client of mine recently told me: “You inspire confidence and […]
Sometimes you just have to try it and see what happens
Sometimes you just have to try it and see what happens The single greatest key […]
Training and testing
Training and testing I’ve written before that the best form of training follows this process: […]
How to save a “failing” project
How to save a “failing” project It is not unusual for me to receive a […]
