Prioritization in Enablement Webinar

If you've spent even a week in sales enablement, you know the feeling: a never-ending stream of requests, every one of them labeled "urgent." New battle cards. Discovery training. A Forrester report your CMO wants the whole team "enabled on." And somehow, it all lands on your plate.

In a recent webinar, enablement veterans Stephanie Middaugh and Nina LaRouche shared practical frameworks for cutting through the noise and building an enablement function that actually moves the needle.

Here are the key takeaways.

Why Prioritization Is the Hardest and most important Part of the Job

Enablement is uniquely positioned to see the full weight of everything hitting the sales team at once: legal changes, onboarding redesigns, new product launches, methodology shifts, comp updates, and more. And every single ask, regardless of where it comes from, feels both important and urgent.

The cost of getting this wrong is real: quality goes down, deadlines get missed, teams burn out, and stakeholder trust erodes. Nina put it plainly, "The worst thing we can do is ask them to spend time in learning and it not be impactful." As someone who spent 15 years as a seller herself, she's fiercely protective of rep time.

Stop Saying Yes to Everything, But Do It Strategically

Stephanie acknowledged what many enablement professionals feel early in their careers: the instinct to say yes to everything because we're helpers by nature. The problem? When review time comes and someone asks what impact you've had, "I did everything everybody asked me" isn't a business outcome.

The reframe: saying no or not yet is one of the most helpful things you can do for the organization as long as you explain your reasoning. Stephanie's advice: lead with a disclaimer. Tell your stakeholders upfront that you ask a lot of detailed questions, and why. It keeps the door open instead of putting them on the defensive.

Key Frameworks for Prioritization

1. The Impact vs. Effort Matrix

Score each request from 1–10 on both potential business impact (does it tie to an OKR? affect revenue? require significant behavior change?) and required effort (from both your team and your learners). Plot them on a matrix and focus your energy accordingly:

• High impact, high effort → Schedule it proactively

• High impact, low effort → Quick wins, do these now

• Low impact, low effort → Fill-ins if capacity allows

• Low impact, high effort → Deprioritize or decline

2. The Learning Budget

Nina recommends setting a clear limit and getting stakeholder alignment on it upfront. Her best practice was 5 hours per rep per month. When requests start stacking up to six, seven, or eight hours of learning time, you have a concrete, agreed-upon benchmark to push back with. It turns "no" into a data-backed conversation.

3. The Tiering Framework

Borrowed from product marketing's launch tiering model, this approach buckets enablement requests into three levels:

• Tier 1: Full behavior change required: new messaging, methodology, pricing, platform shift. These need a full-blown enablement initiative. Aim for no more than one or two per quarter.

• Tier 2: Supplemental to how teams work: not a full behavior change, not just an FYI.

• Tier 3: Information sharing: newsletters, team conversations, brief updates. The Forrester report? Tier 3.

4. The BANT Qualification for Enablement Requests

Nina drew a direct parallel between qualifying a sales opportunity and qualifying an enablement ask:

• Budget: Does the enablement team have capacity? Do learners? Do managers have bandwidth to reinforce?

• Authority: Who's the real champion? Be wary of "the CRO said this is the #1 priority" from multiple people in the same month.

• Need: What does the data actually show? Is this a real, widespread problem or a reaction to one bad call?

• Timing: Is there a broken process that needs fixing first? Training on top of a broken workflow won't stick.

Knowing vs. Doing: Ban the Word "Know" from Learning Objectives

One of the most memorable moments of the webinar: Nina bans the word "know" from any learning objective on her team. Knowing something is not the same as doing something. Content existing in the world doesn't mean learning is taking place. Just because you pushed out a battle card doesn't mean behavior changed.

The question to ask: What do we want reps to do or say differently than they do today and why aren't they doing it already? The answer is often not a knowledge gap. It might be a broken process, a misaligned comp plan, or a tool that isn't working. Enablement's job is to diagnose not just to train.

Build a Flexible Roadmap

Stephanie shared a roadmap template that visualizes tiers, timelines, and capacity across the quarter. Her recommendation: plan roughly 60% of your roadmap in advance and leave 40% flexible. Two acquisitions in four months will happen. Things change. Build in the room.

Final Thought

At the core of all these frameworks is one idea: enablement professionals exist to drive business results, not just to fulfill requests. As Nina put it, you may have a different path to get there than your stakeholders expect; your job is to help them understand why that path leads somewhere better.

And if you’d like to take a peak at the slides that were presented during the webinar, then you can click the button below!