A Sales Enablement Project With No Impact Is Evidence

The review meeting tends to happen about two quarters after launch. The sessions ran, the playbook was published, attendance was respectable, and the number the programme was meant to move has not moved. Win rates sit where they were. Deal cycles are no shorter. Someone has to say what happens next, and the room has little appetite for an awkward answer.

The two easy exits

Two responses tend to arrive first. The first is a relaunch: the content was right but the delivery was thin, so the next version adds coaching, a certification and a manager toolkit. The second is quieter. The project is closed, the budget moves elsewhere, and enablement becomes a subject nobody raises for a year. Both treat the failed project as a verdict on enablement, when it is closer to an experiment whose results nobody has read.

A programme that ran for two quarters touched real deals with real reps. It changed some behaviour, failed to change other behaviour, and left a trace of both in the pipeline data, the call recordings and the reps' own account of what they did. That trace is the most specific evidence the company holds about its commercial system, and it is usually thrown away with the project. Why such programmes go wrong at the start is the subject of why sales enablement initiatives fail. This note is about the morning after.

The review that helps does not ask whether the project worked. It asks two narrower questions in order: did the behaviour the programme taught show up in deals, and where it did, did the stage it was aimed at convert differently. The combinations of those answers point in different directions.

Three patterns in the evidence

• Behaviour never changed. Reps attended, passed the assessment and kept running deals the old way, either because the content did not match the deals they work or because nothing in their week asked for the new behaviour.
• Behaviour changed and the number did not. Reps ran the new discovery or the new demo, and conversion at the target stage stayed flat. The skill was real, and it was not the constraint.
• Behaviour changed and then reverted. The new approach appears in the first month and fades by the third, usually around a quarter end. Something in the system pays for the old behaviour more than anything pays for the new one.

The second pattern is the most informative and the most often misread. A programme that changed behaviour without moving the result has shown, at some cost, that the loss sits somewhere else: in which accounts enter the pipeline, in pricing, in a product gap that better discovery now surfaces earlier, or in an unsettled decision about which segment the company is pursuing. The project did not fail to make an impact so much as it measured where the impact cannot come from.

The pattern that hides inside averages

Averages blur a fourth reading. The programme worked for one region, one segment or one tenure band and did nothing for the rest. Taken as a total, the result is flat. Taken by group, it often shows that the strong performers were already doing what the programme taught, or that the gain concentrated where deal size and buying process suited the method. That is a targeting finding, and it shrinks the next brief considerably.

The material needed for this reading exists for a short time. Call recordings roll off retention schedules. Reps who took part change territory or leave. The managers who were meant to reinforce the programme forget which deals they discussed it in. Stage definitions are revised in the next planning cycle, and the baseline becomes impossible to reconstruct.

What to collect before closing

A field review of a few weeks, run before the project is formally closed, is usually enough. In the reviews we have run, the useful material is plain:

• a sample of recorded calls from before and after launch, scored only for the behaviour the programme taught
• stage-by-stage conversion over the same period, split between the groups the programme reached and those it did not
• short interviews with reps about deals won and lost since launch, asking what they did differently and what stopped them
• the compensation plan and the pipeline review agenda as they actually ran, not as designed

None of this requires a new tool, and almost all of it is gone within a year. The interviews matter more than they appear to. Reps can usually say in a sentence why a technique was dropped: the prospect would not sit through a long discovery call, the manager wanted the forecast figure rather than the deal story, the method cost a week in a quarter that could not spare one. Those sentences are findings about the system, and the programme surfaced them at no extra cost.

Once the pattern is read, the choice stops being binary. Each reading suggests a different next step, and only one of them involves more enablement.

Matching the step to the reading

Where behaviour never changed, the first move is in the operating rhythm rather than the content: a pipeline review that asks for the behaviour, managers who inspect it in live deals, a short period in which it is visible whether reps use it. Where behaviour changed and the number did not, the work moves upstream into the commercial system, and further training would spend money to confirm a result already in hand. Where behaviour reverted, the compensation plan and the stage definitions come first. Where one group improved, the next programme is smaller and aimed at the conditions under which it worked.

A project that changed behaviour without moving the number has already answered the question a second programme would ask.

Some readings do end in stopping. If the evidence shows the skill was never the constraint, the honest result is to close the project and say why, in writing, so that the same request does not return next year under a new name. The discipline of stopping well is covered in kill criteria for projects, and it applies here with one addition: a stopped enablement project should leave behind a finding, not only a closed budget line.

A post-mortem run by the team that delivered the programme tends to grade the delivery. A review that reads the evidence for what it says about the commercial system needs someone with no stake in either the programme or its successor. That is the part of our consulting practice built on the diagnosis before solution method: the failed project is treated as data, and the next decision is made against it.

Where the reading does point back to capability, the next programme is written with the baseline and the target group the first one lacked, and our training work builds it to that brief. It is often the smaller of the two programmes, and the first one whose result can be judged.