Data
2025
Data incidents are opportunities
Hey 👋 How is it May already?! Here in the UK we have another bank holiday weekend. If you do too, enjoy the time off!
2024
Assumptions built on assumptions
Your customers assume the data application they are paying for is always correct and always up to date.
What does it mean to take responsibility?
What does it mean when we say data producers must take responsibility for their data?
The 98/2 rule
The 98/2 rule as described in the Farnam Street newsletter back in July has really stuck with me:
Conway's law and data
Conway’s law asserts that the designs of systems are influenced by an organisation’s communication structure, suggesting that how teams are organised and communicate will reflect in the final product.
Data teams start with accessibility
A new data team, perhaps being created in a business that is evolving from a startup to a scaleup, often focus on accessibility.
Friction is a data teams biggest challenge
Jesse Anderson ran a survey which had some interesting results. One of the key takeaways that stood out to me is this:
Writing code is the easy part
Writing code. Modelling data. Building transformations.
That’s the easy part.
The hard part is using all of that to deliver meaningful value to your organisation.
The limits of centralisation
There’s a limit to what you can do with a fully centralised data team.
A centralised team will never have the capacity to make all data accessible. So, only the most important datasets will be of decent quality to be truly accessible to most of the organisation. The rest will be inaccessible.
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? 😅
(Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)