Enablement Spring Cleaning: The Clutter Problem

One thing I've noticed over time is how quickly content adds up in Enablement.

It usually starts with good intent. Something like a new deck to support a launch, a battlecard for an upcoming deal, or a playbook designed to help the team improve. On their own, each of these makes sense. But over time, they start to pile up, and eventually you reach a point where reps aren't asking for more content, they're asking where anything actually lives.

The hard truth is that most Enablement teams don't have a creation problem. They have a clutter problem.

We build decks, battlecards, playbooks, call guides, and messaging docs, then wonder why reps still ask, "Where do I find that again?" It's not because they don't care; it's because there's too much, and at a certain point, more content stops being helpful and starts creating friction.

But there's a deeper issue I see consistently.

Content isn't structured around how customers actually buy.

Instead, it's organized around products, internal teams, launches, and org charts rather than the end-to-end customer journey. So even when the content itself is strong, it often doesn't show up at the moment a rep actually needs it.

And if it doesn't fit into the field's natural flow of work... from discovery to proposal to decision to close, the reality is that it gets missed. Not because reps don't value it, but because it doesn't align with how they execute in a live deal.

If I'm looking at this through a "spring cleaning" lens, I'm not asking what else we should build. I'm asking what we should remove, and more importantly, how the content we keep actually shows up inside the deal.

The best Enablement teams approach this differently. They consolidate instead of adding, retire outdated materials aggressively, and structure content around the buying journey rather than internal silos. They also prioritize embedding that content into the tools and workflows reps already use, instead of relying on a separate destination that requires extra effort to navigate.

Because the goal shouldn't be to document everything. It's to make execution easier. And execution doesn't happen in a content library—it happens inside a deal.