This message was deleted.

Dealing with the ‘generators’ stakeholders hand in hand. If internal apps, then product owners and tech leads in charge

@quick-house-6813 thanks for that response! could you share some practices you have in place around how you stay close with product?

This is a hard nut to crack, but some things I've seen (similar to @quick-house-6813’s points above!): • Getting very involved with the implementation of new tooling other teams are bringing onboard (e.g. if Marketing is implementing a new customer engagement platform, support them through the integration process to ensure it's set up correctly and integrated into your tech stack properly) • With event collection, migrating to a CDP like Rudderstack or Segment can ensure you're centralizing data collection and implementation, and sending from a single source of truth (rather than arguing with Marketing about which event is correct "sign up" or "user registered" 🤦‍♀️ • Build relationships with different stakeholders who own tools in various departments (so get close to your Salesforce Operations Manager, or technical Marketing Ops person) so you can be brought in the loop when they're implementing new data collection, mapping, or moving data • Educating stakeholders on the importance of clean data collection so they understand the value and can share responsibility of owning their own data source • Becoming best friends with your Engineering team 🫶 --> co-develop processes to learn proactively about database schema changes, communicate about critical data bugs so they can be prioritized, and help them understand the downstream usage of the data they provide (or more advanced: work on building data contracts with your eng team!)

You took all the words from my mouth, @prehistoric-vase-57094 I would only add maybe ‘get full, evident, public and clear support from CEO to mess around outside your natural data space’, so everybody understands the purpose of all these actions you mention

Good point! Definitely need stakeholder buy in :)