How do you as a RevOps leader collaborate with other teams to develop and implement reports that are relevant and actionable for everyone?

[Copied answer from another similar question]

We talk - a lot. I think RevOps/Sales Ops teams get into trouble when they build things in a bubble and don't spend time working with the consumers of the information.

As a leader in RevOps or Sales Ops, you are probably already having 1:1 meetings with the leaders in these other functions. Sometimes reporting or analytics needs will come up organically but other times you'll have to dig to find out what is and is not working for them. Either way, by engaging you get a better understanding of the business needs and then can form a perspective on what you can and should build in terms of reporting.

The second key is to come with a strong hypothesis of what to create, where to create it (e.g., Salesforce dashboard vs. Tableau), and how the team will use it. If you just ask "what reports do you wish you had?" you'll either get nothing back or so many ideas (good and bad) that it's overwhelming. Having a POV and sharing that with these audiences can really help shape your work and let you prioritize and say no to things (an essential RevOps skill).

Once you start building reporting, you can iterate and work to enable users to self-serve. We have probably all experienced the reporting request > build report > still get asked basic analytical questions that the dashboard answers flow. By iterating and creating the right enablement, you empower these audiences to answer questions themselves, free up your own time to work on insights and actions rather than reactive question answering.