Enablement's Forgotten Role in Change Management
The new sales process is live. The CRM is updated. You explained why the change matters and had the project lead run the team through some training.
Three weeks later, deal reviews sound exactly the same.
Reps are using the new fields to document the old approach. Managers ask the same questions they always asked. The forecast still depends on who tells the most convincing story.
Everything on the rollout checklist got checked, yet the way people work barely moved.
Why? Because you tried to change their behavior without changing your own.
Effective change management requires focused enablement. It's the part almost everyone skips. Someone has to translate the business decision into specific behaviors, help people practice those behaviors, and make sure they stick. That work has to start before the training invite goes out, not after.
You don’t plant a garden and skip the watering. Planting is the exciting part. The watering and weeding isn’t. Planting seems like the hardest step. It’s not. The watering and weeding are. And they’re what determines whether anything is going to grow. You see where this metaphor is going.
Change means asking people to give up habits that worked. Those habits got someone to quota, or got them promoted, or kept a customer happy. A slide explaining the new approach doesn't erase the reasons they trusted the old one.
Say you’re moving upmarket because you’ve determined it’s the best path to bigger deals and more predictable revenue. Moving upmarket isn’t as simple as targeting bigger companies. It requires a more complex sales motion. Reps now need to navigate buying committees, build a real business case, and pull in technical resources earlier than they used to. "Start selling to enterprise accounts" sounds like direction. It's actually a blank page, and every rep fills it in differently.
Enablement makes that direction concrete. What discovery needs to uncover. How to spot a missing stakeholder. When to loop in a solutions engineer. What counts as evidence a deal is real. Building that out early also surfaces the contradictions nobody planned for. If the new motion needs deeper discovery but managers still push reps to send a proposal after the first call, the team is getting two instructions at once. Someone has to catch that before it becomes an adoption problem instead of a planning conversation.
Workflow matters here too. Seventy percent of B2B sellers say they're overwhelmed by the number of tools required to do their job. A new process that just gets stacked on top of everything else isn't a rollout, it's a pain in the ass. Part of enablement's job is deciding what gets retired when something new comes in. The old spreadsheet. The duplicate report. The meeting that stopped serving a purpose a month ago.
Managers are the lynchpin. A rep can leave training ready to try the new approach and drop it after one deal review. If the manager only asks about close date and contract value, that's what gets prepared for. If the manager asks how the buyer described the problem, who owns the decision, and what proves the deal is moving, the new approach gets reinforced in the one place that actually counts, real deal reviews. Companies with consistent coaching see 32% higher win rates and 28% higher quota attainment.
Enablement can build the system, but leaders determine if expectations stay consistent and whether managers get time to coach instead of just chase numbers. You can't hand accountability for the change to a function that doesn't control anyone's priorities.
The work doesn't stop at launch. Once people start using the new approach, the real questions show up. As Mike Tyson said, “Everyone has a plan until they get punched in the face.” A rep hits a buying process that doesn't fit the playbook. A handoff meets every documented requirement and still misses the context the next team needs. Two managers grade the same deal stage differently. Don’t mistake them for failures, they're feedback. Enablement’s job is to listen, sort the skill gaps from the process gaps, and get the right people in a room to fix it.
That matters more than it sounds. More training doesn't fix a slow approval process. Another reminder email doesn't fix conflicting incentives. Sometimes the change itself is wrong, and the people closest to running it are the first ones who'd know.
Measuring completion tells you who did what you asked them to. It doesn't tell you what changed. If you want to know whether the new discovery approach is working, listen to whether reps are actually uncovering business impact and using it to shape the next call. Watch whether that shows up in conversion over time. Revenue takes a while to catch up. Behavior doesn't.
For a growing company, this doesn't need a department. It needs an owner, whether that's a dedicated enablement hire, a fractional partner, or someone already wearing four hats who takes this on as a fifth. What matters is that the ownership starts before the change gets announced and doesn't disappear the week after.
Before your next rollout, ask who's responsible for helping someone use the new approach on an ordinary Tuesday, with a full calendar and a real deal at risk. If nobody has an answer, those tomatoes you just planted are going to die on the vine.