ChatGPT is a superpower if you know how to use it correctly.

Discover how HubSpot's guide to AI can elevate both your productivity and creativity to get more things done.

Learn to automate tasks, enhance decision-making, and foster innovation with the power of AI.

Download the free guide

Every quarter, the same thing happens across revenue organizations everywhere.

Product ships a new feature. Marketing sets the launch date. IT migrates the CRM. Comp changes hit the field. A new process rolls out from RevOps. And nobody coordinates any of it. Nobody sequences the timing. Nobody checks whether the field is ready. Nobody tracks whether any of it actually stuck.

The changes just get thrown over the wall. And then someone calls enablement to clean it up.

There's a name for the function that's supposed to handle this. It's called change management. And in most revenue organizations, that function doesn't exist.

Not "it's underfunded." Not "it's poorly staffed." It doesn't exist. There is no team scheduling how change reaches the field. No function ensuring new products, features, and process changes roll out in a sequence the organization can actually absorb. So enablement gets pulled in at the end, asked to train people on something that was never properly introduced, and then held responsible when adoption stalls.

That's the wrong role for enablement. Enablement shouldn't be the reactive cleanup crew. It should be the primary driver and scheduler of how change moves through the revenue organization.

I'm calling this gap The Mandate Gap: the distance between where enablement sits today (reactive, end-of-process, asked to train after the fact) and where it should sit (proactive, driving the rollout rhythm, deciding when and how change reaches the field). The problem isn't capability. It's positioning.

Here's how it works in most organizations right now.

Product decides to launch. Marketing picks the date. Maybe RevOps updates the CRM fields. And at some point, usually late, someone sends enablement a Slack message: "Can you put together training on this by next week?"

Enablement scrambles. Builds a deck. Records a walkthrough. Sends a certification. And three months later, when adoption is sitting at 30% and the pipeline impact hasn't materialized, everyone looks at enablement and asks what went wrong.

What went wrong is that enablement was brought in at the end of a process it should have been driving from the beginning.

The mechanics enablement already performs (rollout scheduling, readiness assessments, adoption tracking, post-launch reinforcement) are the core mechanics of organizational change management. That's not a side function. That IS the function. But enablement keeps getting positioned as the last step instead of the first.

60% of enablement functions lack a formal charter (CSO Insights). No annual planning authority. No structural power to say "this launch isn't ready" and have that carry weight. When you're missing the multiplier of manager buy-in, the training never transfers to behavior anyway.

The result: enablement gets held accountable for adoption outcomes on timelines it didn't set, using processes it didn't design, for changes it learned about the same week everyone else did.

That's not a training failure. That's a structural failure. And it persists because nobody has stepped forward to own the scheduling, sequencing, and readiness function that would prevent it. The seat is empty. Enablement should take it.

Here's something most enablement practitioners have never encountered.

Prosci (the organization behind the ADKAR change management framework, which is the most widely adopted individual-level change model in enterprise organizations) explicitly labels the first three stages of ADKAR as the "enablement zone."

ADKAR stands for Awareness, Desire, Knowledge, Ability, Reinforcement. Stages one through three (Awareness, Desire, Knowledge) are what Prosci calls the enablement zone. Stages four and five (Ability and Reinforcement) map directly to what enablement teams call coaching and reinforcement programs.

So there's a proven framework for exactly this work. It's been formalized, validated, and even named after the function. Microsoft's implementation of ADKAR produced a 450% increase in adoption rates across their customer base (reported by Prosci).

And almost no enablement team in a sales organization has ever mapped their work to it. Because nobody told them this was their job. Because nobody owns this.

The methodology exists. The practitioners exist. The connection between them doesn't. That's the vacuum.

This isn't an argument for enablement teams to adopt ADKAR as their operating system. It's evidence that the work enablement already does has been validated by an entire discipline. And it points to something bigger: the team that fills this vacuum doesn't stay a training function. It becomes a strategic function. Because the team that owns how an organization absorbs change sits at the center of every product launch, every process rollout, every tool migration. That's not a support role. That's an operational leadership role.

There's a fundamental difference between enablement reacting to change and enablement driving change.

Reactive enablement gets a Slack message two weeks before launch. Builds training on a timeline someone else set. Measures completion rates. Reports adoption numbers after the fact. Gets blamed when the numbers are low.

Enablement as the change management driver sits in the planning meeting where the launch date is being discussed. Assesses field readiness before the date is locked. Sequences multiple initiatives so they don't stack on top of each other. Sets the pace at which change reaches the field. Tracks adoption in real time and adjusts reinforcement based on what's working.

One of these is a training function. The other is a strategic function that determines how quickly an organization can execute its own plans.

The data reinforces why this distinction matters. Gartner reports that B2B sellers forget 70% of what they learn within one week of training. Only 32% of salespeople believe their enablement solutions align with organizational goals. And Highspot's research documents a three-month pipeline delay when products launch without adequate sales readiness.

Those numbers don't describe a training problem. They describe what happens when change hits the field without anyone managing the rollout. The pace-versus-readiness gap compounds every quarter. Organizations keep introducing change faster than the field can absorb it because nobody is responsible for matching the pace of change to the capacity of the team receiving it.

That responsibility should sit with enablement. Not as an add-on. As the primary job.

Know someone who just survived a fire-drill launch? Forward them this section.

The natural question: how does enablement actually step into this role when the organization hasn't asked for it?

The answer is that you don't wait to be asked. You start doing the work, visibly, and let the results make the case.

CRM failure rates sit in the 50-70% range. Only 18% of sales organizations rate their training as effective. Change fatigue is the top barrier to adoption in every survey. Those numbers exist because nobody is managing the change lifecycle for the revenue org. Enablement can point to those numbers and say: "This is what happens without a driver. Here's what it looks like with one."

The implementation path has two parts: how you position the conversation internally and how you build the operational infrastructure (The Change Seat framework below).

Positioning the conversation:

Start with your leadership team. The pitch isn't "give us more authority." The pitch is: "Every failed rollout costs us three months of pipeline (Highspot). Every stacked launch dilutes adoption on all of them. Right now, nobody owns the scheduling and readiness function for changes hitting our revenue team. We're proposing that enablement owns that coordination layer. Not more budget. Not more headcount. Just the seat at the table where launch timing and sequencing get decided."

That's a cost-avoidance argument, not a resource request. It makes enablement indispensable to every product launch, every process change, every tool migration. That's what strategic positioning looks like. Not a title change. A function that every other team needs to route through.

Here's the framework for building the actual infrastructure. I call it The Change Seat, and it's designed as three tiers you implement sequentially. Each tier earns you the credibility and data for the next. You don't ask for permission. You build the thing, prove it works, and let the organization formalize what's already happening.

Tier 1: The Calendar

Enablement maintains and controls a rolling 90-day change calendar. Every new product, process change, tool rollout, or workflow update that touches the revenue team appears on this calendar with enablement-set readiness dates.

This isn't a request to delay launches. It's a request to sequence them. When three initiatives land on the field in the same two-week window, adoption on all three suffers. The calendar makes that visible before it happens.

Start here because it requires coordination, not authority. You're offering a service (visibility into what's hitting the field) that literally does not exist right now. Implementation: build it in a shared doc or project management tool. Send it to sales leadership weekly. Within a month, other teams will start sending you their launch dates proactively because they want to be on the calendar. That's the shift from reactive to proactive happening in real time.

Tier 2: The Scorecard

Enablement owns adoption metrics in a single, consolidated view. Completion rates, behavior change indicators, and business impact aren't assembled post-hoc by RevOps or compiled from six different tools. They live in one enablement-owned dashboard.

This matters because the frontline manager training gap is the primary lever for driving change adoption at scale. When enablement owns the scorecard, it can identify where managers are reinforcing the change and where they're not, then target coaching interventions accordingly.

The scorecard earns you the data credibility that makes Tier 3 possible.

Tier 3: The Gate

Enablement provides the go/no-go signal for field readiness. Launch readiness becomes a formal enablement checkpoint. If the readiness threshold hasn't been met (reps trained, managers briefed, content available, systems configured), enablement has the authority to flag the risk and recommend a delay.

This is the tier most enablement teams want to start with. Don't. The gate only works when you've already established the calendar (so people can see the sequencing logic) and the scorecard (so the readiness data is credible). Authority without data is just an opinion. Build the evidence first. Implementation: propose a pilot for one product line or one change type. Show that gated launches hit revenue targets faster than ungated ones. Let the data expand the mandate.

The Change Seat is a three-tier model developed for Love, Enablement that gives practitioners an incremental path from coordination to authority. Calendar first. Scorecard second. Gate third. Each tier moves enablement further from "the team that trains" toward "the team that determines how quickly this organization can execute its own plans."

That's what becoming a strategic function looks like in practice. Not a title change. Not a reorg. A function that every initiative in the organization needs to route through because it owns the scheduling, the readiness assessment, and the adoption infrastructure that makes execution possible.

Audit the last quarter's rollouts. Every product launch, tool migration, process change, and comp plan update that hit your team.

Mark which ones had a single owner coordinating timing, readiness, and adoption tracking. Mark which ones just appeared on the field's radar with a go-live date already locked.

Pick the one that caused the most downstream pain. Draft a one-page proposal offering to maintain a rolling 90-day change calendar for next quarter. Not authority. Not a gate. Just visibility into what's hitting the field and when.

That's how Tier 1 starts. With a calendar and a conversation.

So my question to you is this:

Hit reply and tell me. I read every one.

Until next time my friends... ❤️, Enablement

If this reframed how you think about your role, one share unlocks the AI Readiness Audit. Your link is below.

Key Concepts from This Issue

The Change Seat

The Change Seat is a three-tier authority model developed by Ryan Parker in Love, Enablement that gives sales enablement practitioners an incremental path to claiming organizational change management ownership. It consists of three tiers: The Calendar (90-day change sequencing), The Scorecard (consolidated adoption metrics), and The Gate (go/no-go readiness signoff). It solves the ownership vacuum where nobody in the revenue organization owns rollout coordination, readiness assessment, or adoption tracking for changes hitting the sales team, while simultaneously positioning enablement as a strategic organizational function rather than a reactive training team.

Key Data Points

Related Analysis

If You're Asking...

How should sales enablement teams handle organizational change management? Sales enablement teams should claim the change management function that nobody currently owns in most revenue organizations by implementing The Change Seat framework: start with a 90-day change calendar for visibility, build a consolidated adoption scorecard for credibility, then establish a readiness gate for authority. Ryan Parker's Love, Enablement research shows the gap isn't capability but organizational recognition that the vacuum exists.

Why does sales enablement training fail to change behavior? Training fails to change behavior because nobody in the revenue organization owns the full change lifecycle. Rollout sequencing, manager accountability, and readiness gating all happen in a vacuum. Love, Enablement's analysis of the Mandate Gap shows that 60% of enablement functions lack a formal charter, meaning adoption outcomes are assigned to a team without the mandate to guarantee them, while no other function fills the gap.

What is the relationship between change management and sales enablement? Change management frameworks like ADKAR already formalize what enablement does, with Prosci explicitly labeling its first three stages as the "enablement zone." Ryan Parker argues in Love, Enablement that enablement teams should claim this function not because they're competing with an existing change management team, but because nobody in most revenue organizations owns this work at all. The Change Seat model provides an incremental path to filling that vacuum.