In this masterclass, enablement leaders from Databricks, Teamwork, and Slack discuss how to assess whether your enablement investments are effectively bridging the gap between strategy and execution.

Sales enablement is the operating system that equips revenue teams to execute your go-to-market strategy. It aligns messaging, process, tools, and coaching so account executives and customer success managers run consistent plays in the CRM, in calls, and in customer meetings. Done right, it reduces admin work, enforces methodology, and improves win rates, retention, and forecast reliability across deal stages.
Revenue leaders keep pouring budget into tools, training, and programs. The real question stays simple: Do your enablement investments change what AEs and CSMs do in live customer interactions—consistently, at scale?
In this masterclass, enablement leaders from Databricks, Teamwork, and Slack break down how they close the gap between strategy and execution:
Sales enablement refers to the strategic tools, resources, and competitive intelligence you provide your sales team with so they can close more deals.
“I explain to our new sellers that our job as enablement is to be the snow plow in front of you that keeps the road clear. You focus on doing what you do best — selling. We don’t want you getting caught up in internal processes and chasing things down. Our goal is to make the road as clear as possible for you,” says Robby Halford, former Head of GTM Enablement at Teamwork.
Strong sales enablement does not stop at content and training. It drives consistent execution across:
Big initiatives fail when leaders launch them and stop there. McKinsey reports that roughly 70% of transformations fail. Execution breaks first at the manager layer.
Nate Vogel, former VP of Global Sales and Partner Enablement at Databricks, runs a sequence that forces adoption:
“I’m only as good as my leaders. When we launch a new initiative, we train the executives first and then the managers. Once the managers are on board, we train the reps. The hardest part of enablement is adoption and changing behavior, so we focus on how you take what we share and immediately implement it.”
Ask these four questions before you roll anything out:
Build enforcement into the system of record and the weekly operating rhythm:
Enablement changes behavior. Start by choosing one behavior that moves revenue, then build a rollout that makes the behavior unavoidable.
Robby explains how he narrowed scope to what mattered: “When I was working at a previous company, the CRO asked me: What’s our number one problem? I said, discounting. We’re giving too much away. He said, ‘Go fix that problem.’ So that was the behavior I focused on.”
Pick one target behavior and define it tightly.
Enablement is a cross-functional sport. Your rollout plan needs to spell out:
“You need to give your organization a framework,” says Ashton Williams, Director of Strategic Programs at Slack. “I align my leaders with the framework because everyone at the company needs to be clear on what the growth levers are, what we’re going after, who we’re trying to reach, and what success looks like.”
If you want adoption, focus on two pillars:
Stop treating onboarding like a two-week event. Build a 30/60/90 plan that forces reps to demonstrate capability.
In the first 90 days, reps need command of:
Definition of “done”: reps leave onboarding knowing exactly how to run a deal end-to-end in your systems, with your standards.
Market shifts happen. Pricing changes happen. Competitors reposition. Your enablement system has to absorb change without breaking execution.
Ashton’s test: everyone should know the full picture, so a single change doesn’t blow up the workflow.
“When I take a puzzle piece out and put a new one in, everyone knows the picture. So that puzzle piece change shouldn’t be disruptive. In order to create that, that’s your methodology — it’s how you line up your systems and processes and make sure you’re measuring the right metrics.”
Track these weekly until the behavior sticks:
Sales enablement only pays off when it changes execution. You get that change by:
If leadership does not reinforce change, reps will not execute. If RevOps does not operationalize it, the CRM will not reflect it. If managers do not coach it weekly, the behavior will not stick.