MDR (Minimum Data Required)

MDR (Minimum Data Required)

I've written about minimum viable product (MVP) in software development in the past. MVP means getting the product out into the market with the least amount of features, in order to get customer feedback and to just get something out there.

A related concept in data management is minimum data required (MDR)*. The purpose of MDR is to make it as easy as possible for your customer to buy, and to make it easier for you to manage their data (since there is less data to manage!).

Simply put, MDR asks the question: "What is the minimum number of data points required to complete this transaction?" For example, when a new member comes to join via your website, what is the minimum amount of data required to process that new membership? This is going to vary from organization to organization, but in my experience, almost all associations collect more information than they actually need to process the new membership.

When I ran a customer service department in an association back in the '90s (effectively pre-internet), I used to joke that the most efficient transaction would be one where a person calls and says "I want that" and you already have all their contact and payment information on file, and the transaction is completed. (And then Amazon invented the "Buy Now" button!)

So look at all of your transactional processes, especially those online, and ask yourself "What is the minimum number of data points required to complete this transaction?" Whether it's membership joins, renewals, donations, event registrations, product purchases, or something else, make the process as simple as possible for the buyer.

Less data to manage is easier data to manage.

Wes's Wednesday Wisdom Archives

Painting the Bridge

May 24, 2023

Painting the Bridge According to this article, the Golden Gate Bridge is painted continuously year-round. …

Painting the Bridge Read More »

Maintenance isn’t sexy

May 17, 2023

Maintenance isn’t sexy I remember reading once long ago that one of the reasons our …

Maintenance isn’t sexy Read More »

“Will I still have a job when this is done?”

May 10, 2023

“Will I still have a job when this is done? While working with a client …

“Will I still have a job when this is done?” Read More »

Evolution, not revolution

May 3, 2023

Evolution, not revolution I don’t recall where I first heard it many decades ago, but …

Evolution, not revolution Read More »

The power of the users’ group

April 26, 2023

The power of the users’ group Recently in an online users group forum for an …

The power of the users’ group Read More »

Who is your data evangelist?

April 19, 2023

Who is your data evangelist? I was recently talking with a client of mine about …

Who is your data evangelist? Read More »

Who is your data evangelist?

April 19, 2023

Who is your data evangelist? I was recently talking with a client of mine about …

Who is your data evangelist? Read More »

Ratio of Data to Errors

April 12, 2023

Ratio of Data to Errors One of the elements of a good data governance plan …

Ratio of Data to Errors Read More »

Back to basics

April 5, 2023

Back to basics Over the past couple of years I’ve noticed that some AMS vendors …

Back to basics Read More »

Your people matter

March 29, 2023

Your people matter I’ve written many times about how people, process, and technology have to …

Your people matter Read More »

Scroll to Top