Ratio of Data to Errors
One of the elements of a good data governance plan is establishing data quality metrics. Put another way, what are your measurements for how good your data really is?
One of the simplest but perhaps most powerful metrics is the ratio of data to errors (or what percentage of your data is correct). Simply put, you take the total number of a set of data and compare that to the number of errors on the list. For example, a committee list of 24 names and emails that has two errors on it would have a ratio of 24:2 (or 92% accuracy, if you prefer percentages).
The reason I like this simple formula is that it allows you to have an objective measure of data accuracy. Too often I hear from my clients "Our data is garbage" but they can't really quantify what "garbage" means or what data that is "not garbage" looks like.
There is a tendency to believe the data should be perfect. This is impossible, of course, as I've written many times over the years. But using a ratio of data to errors can help you quantify how good or bad your data is, and also help you set a measurable target for how good your data should be.
Wes's Wednesday Wisdom Archives
Eyes wide open and affirmative decision-making
Eyes wide open and affirmative decision-making When I work with my clients on any type […]
Honoring an industry legend
Honoring an industry legend I’m taking a break from my usual data management tips to […]
Never burn a bridge
Never burn a bridge My children have reached the age where they have, or are, […]
You CAN compete with the big guys…
You CAN compete with the big guys… In my experience, associations often undersell their actual […]
Join (or start) your users group!
Join (or start) your users group! Today’s message is simple: If the AMS you’re using […]
They don’t care, until they care.
They don’t care, until they care. One of the more common questions I get from […]
Longfellow and data management
Longfellow and data management “We judge ourselves by what we feel capable of doing while […]
Do you really need all that historical data?
Do you really need all that historical data? A question I’ll often get from my […]
AI actually requires thinking
AI actually requires thinking “I don’t think AI introduces a new kind of thinking. It […]
It’s not the mistakes, but how you respond
It’s not the mistakes, but how you respond Recently a client was complaining about a bug that […]