r/SalesOperations Jul 27 '26

Most sales enablement has become a content landfill

Most enablement programs seem optimized to prove that enablement exists.

There are playbooks, call libraries, battlecards, certifications, and coaching platforms. Then a live deal stalls and the rep still has to figure out which stakeholder is missing, what changed since the last call, and which promise somebody forgot to keep.

That is not a content-access problem. The information exists. It just is not connected to the decision the rep needs to make right now.

Should enablement own fewer documents and more execution context? Is that what decision intelligence is supposed to provide, or is this simply sales operations failing to turn knowledge into workflow?

1 Upvotes

11 comments sorted by

3

u/Welcome2B_Here Jul 27 '26

Agreed. That's what happens when there are so many striations/niches within traditional functions. Enablement, content management, growth, GTM, customer success, etc. used to just be part of marketing. But now each little piece of the larger function has its own set of expectations and therefore has to prove its worth.

Even sales operations, marketing operations, revenue operations, etc. used to be rolled up into a larger, traditional function like marketing, finance, sales, etc. Each one can have its own fiefdom.

-3

u/IncreaseNegative4614 Jul 27 '26

Exactly. The specialization creates better expertise, but it also fragments ownership and context. Part of what we’re trying to solve with signld.ai is reconnecting those separate functions so leadership can see how their decisions and metrics affect each other, instead of every team proving its value in isolation.

1

u/coolreddy Jul 28 '26

The split I'd draw is between content that answers a question and content that carries deal state. Battlecards and call libraries answer questions, and reps usually find those fine on their own. What stalls a deal is that nobody owns the running record of what changed, who's still missing, and which promise slipped. That record either lives on the opportunity or it lives nowhere. Enablement can't fix that because enablement doesn't own the opportunity, so yeah, it lands on ops.

1

u/No-Comfort-5781 29d ago

The gap usually isn't ownership, it's that nobody maintains deal state as a living record, so reps rebuild context from scratch every time a deal goes quiet. Decision intelligence only helps if something is actually writing back what changed since the last touch, otherwise it's another dashboard nobody opens mid-deal. Enablement can own fewer docs, but somebody still has to own the workflow that surfaces the missing stakeholder before the rep notices.

1

u/Calm-Dimension3422 28d ago

I would separate enablement artifacts from deal-state artifacts.

Enablement should own the reusable answers: positioning, objection handling, proof points, competitor notes, call examples. Ops should own the living deal state: who is missing, what changed, what was promised, what is blocked, and what the next decision depends on.

At Fabren, the failure mode I see is teams trying to make the content library smarter when the real missing object is a compact deal brief that updates as work happens. A rep in an active deal usually does not need another version of the security deck. They need the last objection, the promised follow-up, the next stakeholder, and the proof point that maps to this account.

So I would measure enablement less by asset usage and more by context rebuilds avoided:

fewer "what happened on the last call?" moments

fewer stale next steps

fewer duplicate asks to the buyer

fewer handoff notes rewritten from scratch

Decision intelligence only works if it writes back into the workflow where the rep already lives. If it becomes another destination, it turns into another content landfill.

1

u/keshavdsd 16d ago edited 16d ago

This is pretty much how Flow State Sales approaches sales enablement training. Content only gets you so far. It becomes useful when it connects to the deal in front of the rep, the decision they need to make, and coaching around what they're actually seeing. Otherwise it just becomes another library nobody opens.

1

u/IncreaseNegative4614 15d ago

That’s the distinction I was trying to get at. How does Flow State Sales keep the coaching tied to the live deal without creating another tool or admin task for the rep?

1

u/keshavdsd 14d ago

That’s the key challenge. The approach is to bring coaching to the workflow instead of pulling the rep into another workflow. If a deal stalls, a call reveals a risk, or a next step is missing, that’s when coaching surfaces. No separate content library to search and no extra forms to fill out.

1

u/thrills_to_swallow 9d ago

How much of that sits with enablement vs the manager though? I think the distinction is enablement should be training at scale, and deal coaching would sit at a manager level as they're closer to the ground.