↓Skip to main content

Make the impact visible

·1 min
Data Contracts Communication Data Incidents

Following on from yesterdays post, perhaps the key point is to make the impact of data issues visible.

Visible to engineers making changes to data. Visible to your data producers. Visible to your leaders.

If it’s not visible to them, how would they know?

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.
    ← → Talking to software engineers