The costs propagate forwards, but the value doesn't propagate backwards
The costs of producing data increases as it passes through all the different pipelines and teams needed to refine the data into something useable.
I’m no longer publishing daily data contract tips, but I am still writing! Check out my new weekly newsletter.
The costs of producing data increases as it passes through all the different pipelines and teams needed to refine the data into something useable.
Why would you create and maintain good quality data.
If you don’t know how it is being used.
How, exactly, should you version data contracts?
The default answer is often to use SemVer.
SemVer is a standard from software engineering and used widely to version libraries and releases of software applications.
Data contracts are often considered as a solution to improve the change management and quality of an organisations data.
Your data contract tooling should be designed for data producers.
In many organisations, much of the most important data is produced by in-house software.
I often get asked: How do I get data producers to publish their own data contracts?
While a lot of people associate data contracts with data quality (and I did call my book Driving Data Quality with Data Contracts!), one of the problems data contracts is great at helping to solve for is change management.
When building a (data) platform you end up thinking a lot about the abstractions you are providing, and the trade-offs they cause.
What key business processes depend on your data?
Do the owners and users of those processes understand how dependable the data is?
Nash Squared’s Digital Leadership Report from last year recorded that 64% of organisations they interviewed think that big data and analytics are the way to deliver competitive advantage, yet only 1 in 5 are using it to deliver increased revenue.