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
Two tips for data conversion
Two Tips for Data Conversion I’ve written a lot about data conversion over the years […]
Who should “own” the database?
Who should “own” the database? One of the most common questions I get from my […]
What makes you weird?
What makes you weird? When I work with clients on selecting a new association management system, one […]
Why “AMS Consortiums” Don’t Work
Why “AMS Consortiums” Don’t Work About once a year I will get a call from […]
Your vendor will disappoint you
Your vendor will disappoint you I follow politics as a hobby. A past publisher from […]
Learn how to lose
Learn how to lose “Winning is great, sure, but if you are really going to […]
Ownership is Required
Ownership is required When asked for the most common reason AMS implementations fail, I typically respond […]
It’s all relative…
It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with […]
Eliminate to optimize
Eliminate to optimize So much of data management is habit (both good and bad) which is […]
For data governance, ask “Why?”
For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data […]
