Skip to main content

It's about data applicability, not quality

·1 min

I wrote yesterday how data quality shouldn’t be the focus.

But even with that, at some point you’ll be looking at a dataset and thinking “is this data good enough for what I want to use it for?”.

Most people will say you’re assessing the quality of the data.

But really, it’s the applicability.

That applicability is dependant on your use case, at that point in time.

And data that is applicable to your use case, may not be applicable to someone else’s.

So, how do you know if you can apply the data to your use case?

You need the data owner to set the expectations. For example:

  • How timely will it be?
  • How complete will it be?
  • What are the support levels?

And so on.

Knowing that, you can now make an objective decision about the data’s applicability.


Want great, practical advice on implementing data mesh, data products and data contracts?

In my weekly newsletter I share with you an original post and links to what's new and cool in the world of data mesh, data products, and data contracts.

I also include a little pun, because why not? 😅

Enter your best email here:

    (Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)

    Andrew Jones
    Author
    Andrew Jones
    I build data platforms that reduce risk and drive revenue.