Let’s take Rivery’s internal Slack environment as an example. We have a Slack channel, where we send a proactive message about what happens in each trial account so staff can reach out and respond with personalized engagement within one business day, often within minutes. This is then followed by a higher free trial conversion rate and generated revenue, where the data team is able to tie what they’re  doing directly to the number-one metric of ROI: revenue. What we’ve seen is a 40% increase in terms of conversion with this proactive field team workflow, as well as helping the teamwork of our go-to-market effort. 

Whether fully adopting a data mesh methodology with data products across the org or not, most organizations should strive to make it so that the operational analytics use cases are actually owned by the domain teams with the domain expertise, such as sales teams, marketing teams and product designers. Those teams have the required background to act rapidly on insights delivered from data. Having that domain expertise is also crucial to obtaining and measuring results right from the outset, as well as modeling use cases. That doesn’t mean the technical setup isn’t supported by the data team but ultimately, the usage and adjustments of the workflow over time are the responsibility of the domain teams.

More info: What is Automated Network Provisioning