Daily data contracts tips

Data evolves over time, and as such a data contract needs to support that. We do that by ensuring each data contract has a version.

How many alerts do you get every day?

And how many of them are actionable?

While data products are for people, they still require an interface that allows people to access them - usually through a system such as a database, an analytics tool, a notebook, and so on.

You’re delivering data - and data products - to people.

You need a relationship with those people to ensure you’re delivering what they need.

Data is at the heart of every meaningful service, and it’s the effective use of that data which builds a product, and a business.

𝗧𝗵𝗲 𝟭-𝟭𝟬-𝟭𝟬𝟬 𝗿𝘂𝗹𝗲 𝗼𝗳 𝗱𝗮𝘁𝗮 𝗾𝘂𝗮𝗹𝗶𝘁𝘆

One of my favourite talks at Big Data LDN was by Hannah Davies on The Building Blocks of Data Culture During Transformation.

The quality of your data isn’t simply “good” or “bad”.

Nor does a particular quality dimension necessarily need to be improved.

My post the other day on understanding the concepts, and applying them at your organisation reminded me of how I first encountered data mesh, and how I started applying some of the concepts to my organisation.

I talk a lot about data quality and how it could be improved, because I strongly believe that with a little bit more discipline we can do a lot better.

There’s a lot of great writing out there about interesting ideas like data contracts, data mesh, and much more.