You need a PLAN to deal with duplicates

You need a PLAN to deal with duplicates

Here's the thing about duplicate records: No matter what you do, you'll never get rid of them completely, because humans are human. Whether it's a staff member creating a duplicate record because they forgot to check if the record exists, or it's a customer who doesn't want to take the time to reset his password and just creates another record with a different email address, duplicates are going to happen.

And because duplicates are inevitable, you have to have a plan for dealing with them. Here are some suggestions:

  1. Create data integrity reports that will help you identify potential duplicate records, and run those reports consistently. ("Consistently" means at least once a month, if not more often.) And make sure someone (or several someones) on staff has responsibility for cleaning up this data.
  2. Make it everyone's job on staff to identify potential duplicates whenever they are using the database and make sure you have a clear process for how those duplicate records are reported. And make sure someone (or several someones) on staff has responsibility for cleaning up this data.
  3. And did I mention to make sure someone (or several someones) on staff has responsibility for cleaning up this data?

Managing duplicate records is a journey, not a destination. No matter how good your technology is, like weeds in a garden, duplicate records are going to appear. So you have to have a plan for dealing with them, not just now, but always.

Wes's Wednesday Wisdom Archives

Simpler and Faster is Better

August 24, 2022

Simple and Faster is Better Earlier this week I was fortunate enough to attend a […]

Patience and grace

August 17, 2022

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

August 10, 2022

Sometimes you just have to try it and see what happens The single greatest key […]

Training and testing

August 3, 2022

Training and testing I’ve written before that the best form of training follows this process: […]

How to save a “failing” project

July 27, 2022

How to save a “failing” project It is not unusual for me to receive a […]

How to avoid the “IT black hole”

July 20, 2022

How to avoid the “IT black hole” Going all the way back to my days […]

The “People” are important!

July 13, 2022

The “People” are important! I’ve written a lot about people, process, and technology over the […]

Always look for the MVP

July 6, 2022

Always look for the MVP I first wrote about minimum viable product (MVP) just three […]

The longer you take, the longer it will take

June 29, 2022

The longer you take, the longer it will take It may sound like a tautology, […]

Data is for action

June 22, 2022

Data is for action When deciding whether or not to collect a piece of data, […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top