ReveNEWS: The RevOps Newsletter - 28 Feb 2024

ReveNEWS: The RevOps Newsletter - 28 Feb 2024

RevOps Insights: RevOps Framework Deep Dive – Team Structure

The Hyperscayle RevOps Framework: Team Structure

Most companies underinvest in people and don’t think carefully about the structure of the teams that support RevOps. It’s not enough to just have the right people for the right role – it’s important to build synergy and trust with leadership to get everything in an optimal state, trust the decisions of self-organized teams, and understand that every single step in the process is important.

The maturity of a RevOps organization is not only measured in the number of people on a team but how well they work together.

Read more here: https://hyperscayle.com/insights/revops-framework-team-structure

Who to Follow in RevOps: Mike Rizzo, Founder of MarketingOps.com

Mike Rizzo has built a strong community at MarketingOps.com and MO Pros, and is a top voice for topics including AI, the MarTech stack, product-led go to market, and more. We’re especially looking forward to MOpza24.

Follow him here: https://www.dhirubhai.net/in/mikedrizzo/

RevOps Resources: What is RevOps from Justin Pena

We like this straightforward post from our Salesforce Consultant, Justin Pe?a offering a high level definition of RevOps. In this post, he explains in more detail what RevOps is, the common challenges when implementing RevOps tools, and the importance of RevOps data in the decision-making process.

Check it out here: https://justinpena.com/what-is-revops

RevOps Pro Tips: Document, Document, Document

From: Christian Martinez

Make it a habit to create documentation for every task, regardless of its complexity. Whether it involves sharing the setup, thought process, or plan, having this information readily available can streamline your day-to-day activities.

Not only does documentation aid your team and mitigate potential future issues, but it also provides reassurance that in your absence, others can understand the decisions and processes for current initiatives. For example, there was this time right at the beginning of a recent client project when we needed to update a set of filters in a Lead Source workflow (standardization process).

The client thought that they could blank the data for the field as this would make things smoother, when in reality it was the opposite. Without data, we couldn’t filter properly, and all the new workflow didn’t work until we dug in to figure out what was happening.

Luckily, there was solid documentation and data back-up, so we were able to get everything back in order in no time, These sorts of examples happen all the time, continuously convincing me that taking time to document up front will almost always save time and effort in the end.

Share the RevOps Love!

Like what you read? Please share with other like-minded leaders in marketing, sales and revenue operations.

要查看或添加评论,请登录

Hyperscayle LLC的更多文章

社区洞察

其他会员也浏览了