Joanna Dolan

Guest

linkedin

Joanna Dolan,
Revenue Enablement Director at Ping Identity

"Revenue Architect Podcast"
Episode 23

From Sales Enablement to Revenue Acceleration - with Joanna Dolan

Revenue Architect is the podcast for revenue leaders navigating the evolving landscape of sales, RevOps, and revenue management. Each episode dives into practical strategies, proven frameworks, and real stories from operators who are building and scaling modern revenue engines.

In this episode of Revenue Architects, Steve and Jay sit down with Joanna Dolan, Revenue Enablement Director at Ping Identity, to explore how revenue teams can move beyond traditional sales enablement and build a more disciplined approach to revenue acceleration.

Joanna shares practical insights on improving revenue execution, strengthening forecasting, aligning teams, and using AI to help sellers perform better.

In this episode, you'll learn:

  • Why revenue enablement needs to evolve into revenue acceleration and focus on measurable business outcomes.
  • How to build a disciplined forecasting process based on qualification, evidence, and consistent deal inspection.
  • How managers can coach different types of sellers while still maintaining consistency and accountability.
  • Why CRM discipline matters and how better data can help sellers identify gaps and de-risk opportunities.
  • How RevOps, enablement, product marketing, and sales can bridge the gap between strategy and what actually happens in the field.
  • Why revenue execution is a shared responsibility, with the CRO, managers, and supporting teams each playing a role.
  • How AI can reduce administrative work, improve seller preparation, and provide coaching at scale without replacing human judgment.
  • Why organizations should get their fundamentals right before scaling them with AI.

Whether you're a CRO, VP of Sales, Revenue Operations leader, or frontline sales manager, this conversation offers actionable insights for building a more effective, predictable, and scalable revenue engine.

The Revenue Architect Podcast Episode 23: Show Notes

Building a Better Revenue Engine

Revenue leaders have spent years investing in enablement programs, sales methodologies, CRM systems, training, and increasingly, AI.

Yet many organizations still struggle with the same fundamental problems: unreliable forecasts, inconsistent sales execution, weak opportunity qualification, and sellers who have plenty of information but don't always know how to apply it in the moment.

The problem isn't necessarily a lack of tools or training.

It is a lack of connection between the systems, processes, people, and decisions that drive revenue.

That is why the role of revenue enablement is changing.

In a recent Revenue Architects conversation, Joanna Dolan, Revenue Enablement Director at Ping Identity, explored what happens when enablement moves beyond training and becomes part of the organization's revenue execution engine.

Her perspective points to a broader shift:

Modern revenue teams need to focus less on delivering enablement and more on accelerating the quality and consistency of revenue execution.

Forecast Accuracy Starts With Business Rhythm

When a forecast is unreliable, CRM hygiene is often blamed.

Sellers aren't updating opportunities. Forecast categories don't match reality. Commit deals don't have enough evidence behind them.

So organizations add more fields, introduce new dashboards, or remind sellers to update Salesforce.

But better CRM hygiene alone doesn't create a reliable forecast.

The quality of the forecast is a reflection of the quality of the conversations happening before the forecast.

If managers don't consistently inspect opportunities, challenge assumptions, review deal progression, and establish what good evidence looks like, the CRM simply records everyone's opinions.

A seller may feel confident about a deal. But confidence isn't the same as customer movement.

A disciplined revenue organization therefore needs a business rhythm around opportunity management:

  • Regular deal inspection
  • Consistent qualification
  • Manager-led coaching
  • Clear evidence requirements
  • A common methodology for identifying risk
  • Ongoing review of customer movement

Frameworks such as MEDDPICC can provide structure, but the framework itself isn't the answer.

The real value comes from using it to create better questions and better conversations.

What has actually changed with the customer? What evidence supports the opportunity? What risks remain? What needs to happen next?

When those questions become part of the operating rhythm, forecasting becomes less about seller confidence and more about evidence.

And that makes the forecast more trustworthy.

The Goal Isn't CRM Compliance. It's Better Execution.

One of the biggest challenges revenue leaders face is getting experienced sellers to adopt standardized processes.

High-performing sellers often have their own way of working. If they're consistently hitting quota, they may question why they need to document their process or follow a prescribed qualification methodology.

Trying to force every seller into exactly the same behavior isn't necessarily the answer.

Instead, revenue leaders need to make the connection between process and performance clear.

A seller is much more likely to document an opportunity if doing so helps them identify a missing stakeholder, uncover a qualification gap, prepare for the next conversation, or get leadership support at the right moment.

This changes the conversation from:

"You need to update Salesforce."

to:

"This information helps us understand where your deal is vulnerable and how we can help you win it."

That distinction matters.

The purpose of a sales methodology isn't to create administrative work.

It is to give sellers and managers a shared system for making better decisions.

Revenue Enablement Has a Translation Problem

There is another challenge that often gets overlooked.

Revenue organizations don't operate in isolation.

Product marketing develops messaging. Product teams build capabilities. Leadership sets strategy. RevOps designs processes. Enablement creates resources. Sales takes everything into the market.

Somewhere between those teams, however, the meaning can get lost.

A product team may understand exactly why a new feature matters.

A seller may still be wondering:

"When should I bring this up with a customer?"

That's the translation gap.

The field doesn't necessarily need more content. It needs clearer signals and less friction.

Instead of another 20-page enablement document, sellers may need to know:

  • Which customer situations make this relevant?
  • What business problem does it address?
  • What value should I communicate?
  • What objections should I expect?
  • What questions should I ask?
  • What evidence tells me there is a real opportunity?

This is where modern enablement has an increasingly important role.

It sits between organizational strategy and the reality of the customer conversation.

And the relationship needs to work in both directions.

The field shouldn't just receive information from product marketing and leadership. It should also send information back.

If sellers repeatedly hear that customers don't see value in a particular capability, that isn't simply a sales problem.

It may be a signal about the product, positioning, market, or customer segment.

Revenue execution improves when information flows in both directions.

Enablement Is Becoming Revenue Acceleration

This is perhaps the most important shift.

Traditional enablement has often been measured by activity:

  • How many people were trained?
  • How many sessions were delivered?
  • How many resources were created?

Those metrics tell you what enablement did.

They don't necessarily tell you what changed.

A revenue acceleration mindset looks further downstream.

It asks:

  • Is pipeline quality improving?
  • Are sellers reaching productivity faster?
  • Are opportunities better qualified?
  • Are managers coaching more effectively?
  • Are sellers communicating business value more clearly?
  • Are deals progressing with fewer risks?
  • Is revenue performance improving?

That changes the role of the function.

Enablement isn't simply responsible for teaching sellers.

It becomes part of the system responsible for improving how revenue gets executed.

That means field execution, deal support, business value, onboarding, communications, coaching, and RevOps can't be treated as disconnected activities.

They are interconnected parts of the revenue engine.

Who Owns Revenue Execution?

Revenue execution doesn't belong to one department.

The CRO may ultimately own the revenue outcome, but the CRO cannot personally manage every deal, coach every seller, inspect every opportunity, or maintain every process.

Managers own much of the day-to-day execution.

RevOps provides the operational infrastructure.

Enablement builds capability and reinforcement.

Product marketing connects the market, product, and field.

Sales and customer-facing teams provide direct insight into what customers actually need.

The model is less like a single owner and more like an engine.

Every component has a role.

And if one component isn't working, the entire system can slow down.

That is why alignment matters more than simply defining ownership.

A revenue organization can have excellent processes and still struggle if managers apply them inconsistently.

It can have great training and still underperform if sellers don't use it.

It can have excellent data and still make poor decisions if nobody knows how to interpret it.

Revenue acceleration happens when the entire system works together.

AI Should Strengthen the Revenue Engine—Not Replace It

AI adds another layer to this evolution.

The temptation is to start with the technology:

"Where can we use AI?"

A better question is:

"Where can AI remove friction from a process that already works?"

That's where AI can have immediate value.

Consider sales preparation.

A seller preparing for a discovery call may need to research an account, review opportunity information, understand the customer's industry, identify likely business challenges, prepare questions, and determine what value to explore.

AI can help compress that preparation.

Instead of starting the conversation with a blank page, the seller can start with a structured point of view and spend more time doing what humans are better at:

listening, questioning, interpreting, and responding.

The same principle applies to coaching.

AI can give sellers an environment to practice customer conversations repeatedly, receive feedback, and improve their ability to communicate value.

That creates something traditional enablement often struggles to provide: practice at scale.

But the goal isn't to turn sellers into scripts.

It is to help them understand the thinking behind the conversation so they can respond naturally when the conversation doesn't go according to plan.

AI Can Create More Human Sales Conversations

There is an interesting paradox here.

Used well, AI can actually make sales conversations more human.

When sellers spend less time gathering basic information, they have more mental space for curiosity.

Instead of entering a discovery call thinking:

"What do I know about this company?"

they can enter thinking:

"What do I still need to understand?"

That creates room for deeper discovery.

AI can surface potential issues, identify gaps, summarize account information, generate preparation materials, and provide prompts.

But the seller still has to determine whether those insights are relevant.

The customer still has to validate the assumptions.

And the seller still needs to understand the business impact.

AI can accelerate preparation.

It shouldn't replace judgment.

Don't Use AI to Scale a Broken Process

This is where many AI initiatives can go wrong.

If your qualification process is inconsistent, AI won't automatically make it consistent.

If your data is unreliable, AI won't magically produce reliable insights.

If your sales methodology is unclear, AI can simply distribute that confusion faster.

The principle is straightforward:

Don't automate ambiguity.

Before implementing AI, revenue leaders should establish the fundamentals:

  • Define what good execution looks like.
  • Establish a consistent sales methodology and operating rhythm.
  • Make sure the underlying data is useful and trustworthy.
  • Identify repetitive work that creates unnecessary friction.
  • Apply AI where it can reinforce those established standards.
  • Measure the impact on execution and revenue outcomes.

This approach shifts AI from being another technology initiative to becoming an operational advantage.

Building the Revenue Engine Around Better Decisions

The evolution from sales enablement to revenue acceleration isn't really about changing a job title.

It's about changing the organization's definition of the job.

The question is no longer:

"How do we train our sellers?"

It becomes:

"How do we help our revenue teams make better decisions and execute more effectively?"

That requires a connected system.

Better business rhythm creates better opportunity visibility.

Better qualification creates better forecasting.

Better translation creates better field execution.

Better coaching creates stronger seller capability.

Better data creates better decisions.

And AI can provide leverage across all of it, when the fundamentals are already in place.

For revenue leaders, the opportunity isn't to build an organization with more processes, more content, or more technology.

It's to build one where people, processes, data, and AI work together to improve revenue execution.

That's what turns enablement into acceleration, and a collection of revenue functions into a revenue engine.

For more inspiring stories and actionable strategies from top executives, subscribe to the Revenue Architect Podcast on your favorite streaming platform:

  • youtube music