Data contracts anti-pattern #1: Contracts as documentation
A data contract without impact is just documentation.
Hello š Hope youāve had a good weekend!
Iāve seen a lot of people succeed with data contracts, but Iāve also seen a lot of people struggle. So, over the next four weeks Iām going to write up 4 common anti-patterns Iāve seen.
Interestingly, each of them looks like progress, but they fail to solve the underlying problems.
Iāll kick this series off with the most common anti-pattern: Contracts as documentation.
Thereās also links to posts on building governance into the platform, making an impact as a platform PM, and analytical identifiers.
Data contracts anti-pattern #1: Contracts as documentation
This is where the data contract is written once, often in a document or spreadsheet, usually by the data team rather than the data producer, and thatās it.
It is correct at the time of writing, but quickly drifts from reality as the schema evolves in production. The owner points to an individual who leaves the company, or a team that no longer exists following a reorg. The SLO definitions are based on observations over the last few weeks, not a commitment made by the data owners.
This happens because the data contract isnāt doing anything. Thereās no platform tooling or automation using the contract to monitor or manage the data. The āownerā of the contract has no incentive to maintain it because nothing depends on it being accurate.
While it starts as a useful reference document, it gradually becomes a liability. Itās actually worse than no contract at all, because it provides false assurance to consumers who believe it.
To prevent yourself from implementing this anti-pattern, ensure every field in the contract does something through platform tooling and automation. That could be CI checks preventing breaking schema changes, or SLOs and/or quality rules that fire alerts when they fail, or a data catalog/context layer that is populated from the contract.
Itās the impact a data contract has when it is missing or incorrect that keeps it accurate and up to date. Otherwise itās just documentation.
Interesting links
Why the Best Governance Is Built Into the Platform, Not Bolted On by BjĆørn Broum
Great post on embedding governance into the data platform.
How to make an Impact as a Platform Product Manager by Alex Craciun
While specifically about developer platforms most of the advice is also good for anyone building data platforms.
Integration by Design: Analytical Identifiers by Patrik Lager
Good argument that we should be more deliberate about the identifiers we use.
Being punny š
A man tried to sell me a coffin today. I told him thatās the last thing I need.
Upcoming events
Data Community Conference, September, London
Thanks! If youād like to support my workā¦
Thanks for reading this weeks newsletter ā always appreciated!
If youād like to support my work consider buying my book, Driving Data Quality with Data Contracts, or if you have it already please leave a review on Amazon.
Enjoy your weekend.
Andrew
Originally posted at https://andrew-jones.com/newsletter/2026-06-26-data-contracts-anti-pattern-1-contracts-as-documentation/.