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

Some context, please

April 21, 2021

Some context, please A pet peeve of mine: A report about associations (e.g., marketing benchmarks report) where […]

Eventually automated emails get ignored

April 14, 2021

Eventually automated emails get ignored During the discovery and development phase of implementing a new […]

The challenge the AMS providers see

April 7, 2021

The challenge the AMS providers see Over the years I’ve asked AMS providers what they […]

Be careful about “solutioning” too quickly

March 31, 2021

Be careful about “solutioning” too quickly One of the great things about software developers is […]

What’s our next action?

March 24, 2021

What’s our next action? As you can imagine, I spend a lot of time in […]

Don’t automate for the sake of automation

March 17, 2021

Don’t automate for the sake of automation I’m the laziest person in the world. I […]

Don’t forget about what got better

March 10, 2021

Don’t forget about what got better Negativity bias is the tendency to focus on only […]

Give a little at a time rather than taking away

March 3, 2021

Give a little at a time rather than taking away I’m sure there’s research somewhere […]

First, you gotta have the data

February 17, 2021

First, you gotta have the data When I work with clients on a new AMS […]

Work on your relationship with your AMS vendor

February 10, 2021

Work on your relationship with your AMS vendor It is no coincidence that my most […]

Leave a Comment

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

Scroll to Top