Sales Enablement Content Nobody on the Sales Team Actually Uses

A client's marketing team produced 40 enablement assets over a year — one-pagers, battlecards, email templates, objection-handling guides. When we interviewed a sample of ten sales reps and asked which assets they'd actually used in the last quarter, the answers clustered around three items, and one of those three was a spreadsheet a rep had built himself, not anything marketing had produced.

Why volume doesn't translate to usage

Marketing was building content based on what they assumed reps needed — competitive battlecards, product one-pagers, persona guides — without actually asking reps what they were struggling to answer in live deals. The three assets that did get used all had one thing in common: a rep had explicitly requested them after running into a specific, recurring objection in real calls. Everything built speculatively, without that direct request, mostly sat unused in a shared drive.

Enablement content built from what marketing assumes reps need gets filed away. Enablement content built from what a rep just asked for gets used that afternoon.

• Build a lightweight request pipeline where reps can flag a specific objection or gap they're hitting, and prioritize content against that queue.
• Track actual usage, not just production volume, as the enablement team's core metric.
• Sunset content nobody's opened in 90 days rather than letting the library grow indefinitely.
• Interview reps directly rather than relying on sales leadership's secondhand sense of what the team needs.

The fix wasn't producing less content, it was inverting who initiates it. Once the enablement team switched to a request-driven model, the volume of content dropped by half and the usage rate, measured by actual document opens tied to active deals, roughly tripled.