Skip to main content

Prioritise data projects just like anything else

·1 min

Every organisation beyond a startup has multiple teams or groups working together to deliver something of value for the organisation.

There might be a dependency on an API, the UI, marketing, legal, and so on.

So there will be a process to have discussions to prioritise this work across all the teams, ensuring they are all incentivised to deliver what they need to when it is needed.

Here’s the thing:

If you’re a data team building something that is valuable for the business, and you depend on data that isn’t good enough, then you should be involved in those same discussions.

It’s not necessarily easy! But it will force you to get better at articulating the value you are trying to provide and why that is important for the organisation.

And if you do that well enough, you will get the alignment you need to incentivise other teams to deliver the data you need, so you can quickly and effectively deliver value.


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.