Enablement Content Is Built for the Rep Who Doesn't Need It
The rep who reads every battlecard and opens every playbook is already good. The rep you're worried about isn't reading any of it.
Your content library usage data looks healthy. Reps are opening things, downloading things, maybe even bookmarking things. And yet the bottom quartile of your team is still struggling in exactly the ways they were struggling six months ago. This is not a coincidence. It is a design flaw baked into how almost every enablement function builds and curates content, and it starts with a false assumption about who actually reads the stuff.
The Implicit User You Built It For
Think about the last piece of enablement content you produced or approved. A discovery guide, a battlecard, a competitor one-pager. Now think about who you pictured using it. Someone who noticed a gap in their own performance, went looking for a resource, found it, read it carefully, and then translated the principles into their next call. That is a self-directed, metacognitive rep who already knows what they don't know.
That is, broadly, your better performer.
The rep who is actually in trouble does not know what they don't know. They are not aware that their discovery calls are shallow because they conflate feature interest with genuine pain. They are not going looking for a guide on multi-threading because they do not yet understand that single-threaded deals are why they keep losing at procurement. They would not recognise the relevant content if they opened it, because recognising its relevance requires the very skill they are missing.
Content libraries are almost universally optimised for initiative and synthesis, two competencies that correlate strongly with high performance. The reps who have them least are the ones who need the content most.
Teardown: Three Artefacts, Three Failure Modes
1. The Discovery Guide
A typical discovery guide runs to twelve slides or a four-page PDF. It lists question categories (situation, problem, implication, business impact), provides example questions under each, and probably includes a reminder to listen actively and summarise back.
The competency it assumes: the rep already understands the difference between a question that surfaces pain and one that just gathers information. Without that distinction, the guide is a question bank. The struggling rep reads "What are the consequences of not solving this?" and treats it as a script line, firing it regardless of what came before. They get a vague answer, move on, and log the call as "good discovery." They are not being lazy. They genuinely cannot tell the difference between a meaningful response and a polite deflection, because recognising that difference requires pattern recognition they have not yet built.
The guide does not address this gap because the person who wrote it does not have this gap.
A Discovery Call Checklist is marginally better if it is sequenced and conditional, but most are not. Most are post-call verification tools for people who already ran a decent call.
2. The Battlecard
Battlecards are almost always built as information transfer documents. Competitor strengths, competitor weaknesses, your differentiators, suggested talk tracks. The format implicitly assumes that the rep's problem is insufficient information about the competitive landscape.
For a competent rep, a battlecard is a useful crib sheet. They know when they are in a competitive situation, they know how to weave a differentiation point into a conversation without it sounding like a pitch, and they know when to use the content and when to leave it alone.
The struggling rep's actual problem in competitive deals is rarely information. It is framing. They know the differentiators. They cannot land them. They either deliver them as a feature list or they raise competitor weaknesses in a way that sounds defensive. The battlecard does not teach positioning. It assumes the rep can already position and just needs the ammunition. Giving someone more ammunition when they cannot aim is not helpful.
| Artefact | Assumed competency | What the struggling rep actually lacks |
|---|---|---|
| Discovery guide | Ability to evaluate response quality in real time | Pattern recognition for genuine vs. polite engagement |
| Battlecard | Ability to frame and position, not just recite | Conversational control during competitive pressure |
| Competitor one-pager | Ability to translate features into buyer-relevant outcomes | The habit of asking "so what does that mean for you?" |
3. The Competitor One-Pager
This one is perhaps the most egregious, because it is often the most confidently produced. It compares features side-by-side, maybe includes a pricing comparison, and ends with a summary of why you win.
It is a document that makes sense to someone who already thinks in outcomes. A strong rep looks at a feature comparison and instinctively translates it: "We have audit logging, they don't. That matters to the IT security lead who is worried about compliance reporting. That is my angle." A struggling rep looks at the same table and reads it as trivia. They might mention audit logging on a call. They will mention it to the wrong person at the wrong moment and get a blank stare.
The one-pager has not failed because the information is wrong. It has failed because it outsources all the inferential work to the reader, and the reader who most needs the document is least equipped to do that work.
The Reframe: Design for Deficit, Not for Initiative
Enablement content should be built around the cognitive load and skill deficit of the bottom quartile, not the reading habits of the top. This is not a call to dumb things down. It is a call to make the reasoning visible, not just the conclusions.
Concretely, that means:
- Show the reasoning, not just the output. Instead of "ask about business impact," show a real exchange, what the rep said, what the buyer said, and why the follow-up question was the right one. Annotate it. Make the thinking visible.
- Design for the moment of use, not the moment of learning. A rep will not consult a twelve-slide guide between calls. A one-paragraph prompt with a single decision rule they can read in thirty seconds before dialling, that they might actually use.
- Diagnose before you prescribe. Content that is irrelevant to a rep's specific deficit is noise. If you do not know what each rep's actual skill gap is, you are distributing content by hope. Running a Team Skill-Gap Heatmap Generator before your next content refresh will tell you more than any usage metric.
- Build in explicit translation steps. The competitor one-pager should include a worked example of how to take a feature and turn it into a buyer-relevant implication, done for them once, so they can replicate the pattern.
- Separate reference from instruction. Battlecards as reference material are fine. But if positioning is broken, that is a coaching and skill problem, not an information problem. Stop trying to fix it with a better battlecard.
The usage data looks fine because the reps who are opening your content are the reps who open content. The reps who are struggling are not underperforming because they missed a resource. They are struggling because the resources you have built require skills they do not yet possess to be useful. Until you close that loop, your content library is a very tidy monument to the reps who did not need it.