Podcast

How Revenue Operations Leaders Make Change Stick

Revenue operations creates value when information changes a decision and the decision changes behavior. Dan Leva's career shows the capabilities required to complete that chain: analytical depth, clear presentation, commercial context, and leadership that helps other people perfo

Revenue operations creates value when information changes a decision and the decision changes behavior. Dan Leva's career shows the capabilities required to complete that chain: analytical depth, clear presentation, commercial context, and leadership that helps other people perform the work.

His path moved from statistics and actuarial analysis into client management, sales operations, and eventually senior revenue operations leadership. RevOps emerged where those experiences met.

Analytical skill matters when it creates meaning

An actuarial internship taught Dan to work with large data sets, use Excel deeply, and summarize complex information for an executive audience.

The last capability is the important one. Analysis becomes operational when someone can explain what happened, why it matters, and what the team should do next.

RevOps teams should design reporting around decisions rather than data availability. A complete dashboard can still fail if its audience cannot see the consequence.

Presentation is part of the work

Early in a client-facing role, Dan was asked to take notes. He returned a near-verbatim record without a useful summary, decisions, or next steps. His manager sent him back to do it again with context.

That feedback became a durable lesson: information must be shaped for the reader.

The same standard applies to an operating recommendation. State the question, summarize the evidence, name the conclusion, and make ownership of the next action clear. Raw detail may be correct while still being unusable.

RevOps often appears where skills intersect

Sales leaders began asking questions about what the company was winning, losing, and seeing in Salesforce. Dan's background let him extract the data, interpret it, and connect it to the commercial work.

That pulled him from client management into sales operations.

Career paths into RevOps often work this way. The role emerges at the intersection of technical ability and business context. People who can both analyze the system and understand the decision are hard to replace with a narrowly defined specialty.

A seat at the table requires decision-ready work

Dan found the operating role energizing because leadership used the information to take action. He had access to important questions and could see how his work affected the business.

RevOps earns that position through usefulness, not proximity alone. Leaders return to the function when it consistently frames tradeoffs, validates assumptions, and helps the organization choose.

The fastest way to lose that trust is to report numbers without understanding how they were produced or what they imply.

Leadership changes the time horizon

Dan's transition into people management was difficult because he knew he could complete many tasks faster himself.

The leadership calculation is different. Doing the report in two hours may solve this month's need. Spending more time teaching someone else can return capacity every month that follows.

That investment also expands the team's judgment. The goal is not merely delegation. It is developing people who can understand the question, perform the analysis, and communicate the result.

Every person needs a different form of support

After years of management, Dan emphasizes that people cannot be managed only through their job titles. Individuals have different strengths, motivations, and ways of learning.

A standard process can define the outcome while managers adapt coaching and context. This is especially important during change, when people begin from different levels of understanding and confidence.

Uniform communication may feel efficient but produce uneven adoption.

The practical lesson for RevOps leaders

To make change stick:

  • Connect analysis to a specific decision.
  • Present conclusions, context, and next steps rather than raw detail.
  • Combine systems knowledge with commercial understanding.
  • Build trust through consistently decision-ready work.
  • Invest time in developing the team's judgment.
  • Adapt support to the people carrying the change.
  • Measure whether behavior and outcomes changed after launch.

RevOps is not complete when the recommendation is approved. It is complete when the organization can execute the decision reliably.

About the guest

Dan Leva is Senior Vice President of Revenue Operations at Cielo Talent. His background spans statistics, actuarial analysis, client management, sales operations, analytics, and more than a decade of people leadership.