can your teams retrieve info in the moment with a lead or customer? no doubt. but there's a distinction in cognitive psychology that many of us (myself included) forgot about when we got claude-pilled and rev ops started ops-ing. i think it's running many companies' ramp metrics into the ground based on the conversations i've had this year.

this learning was tough. and i messed it up myself by not prompting workflows into gtm onboarding.

we are figuring out retrieval with ai. building out knowledge interfaces for reps and managers. content libraries, knowledge bases, ai assistants. all retrieval infrastructure. and retrieval infrastructure is genuinely useful. i'm not arguing you should scrap it.

but retrieval has a ceiling. very few people learn through retrieval.

we are destroying recall with ai. reps are not encoding meaning, building frameworks or heuristics they can apply and get creative, curious, and strategic with on a live call or conversation. you know, the thing we are paying them for.

most enablement programs are built almost entirely around retrieval. content libraries, knowledge bases, ai assistants. all retrieval infrastructure. and retrieval infrastructure is genuinely useful and critical.

but a rep in a live discovery call can't pause the conversation to search for "what to do when the buyer mentions a competitor while discussing timeline." that moment lasts about four seconds. either the rep recognizes the pattern and responds (recall) or the moment passes and the deal shifts underneath them.

if you're a psych nerd, read this. otherwise skip.

cognitive load theory (originated by john sweller at the university of new south wales) tells us that working memory has hard limits. a rep on a live call is already juggling the buyer's words, their own talk track, the deal context, and whatever dynamics are happening on the other side of the table. when you add "search for the right content" to that stack, something drops. usually it's the thing that matters most: reading the room.

this is why experiential learning is so disproportionately effective compared to content consumption. when a rep does a role-play and gets feedback, or shadows a senior ae on a tough call, or runs a simulated discovery with a tool like exec or hyperbound, they're encoding patterns into long-term memory. they're building what psychologists call "automaticity": the ability to respond without conscious effort. same mechanism that lets a basketball player read a pick-and-roll without thinking about it. the pattern recognition becomes instinct.

diagnostic learning works the other end of the problem. instead of waiting for a rep to realize they have a gap (they usually don't), the system catches the behavioral drift early. gong flags that a rep's discovery calls are getting shorter. pipeline data in clari shows their conversion rate dipping at a specific stage. the manager gets a prompt before the 1:1. a specific pattern connected to a specific behavior, not a generic "coach this person" alert.

this is spaced reinforcement, one of the most well-documented principles in learning science. hermann ebbinghaus mapped the "forgetting curve" back in the 1880s, and the research since then has consistently shown the same thing: people retain dramatically more when learning is distributed over time and tied to real performance contexts. a two-day bootcamp gives you a spike. diagnostic coaching gives you a slope.

why rev ops and enablement lines are blurring here (i actually don't care what everyone is calling themselves but we need a systems expert and a human behavior expert on fixing this recall problem).

enablement can design the coaching playbook and build the intervention curriculum. but without rev ops, they're flying blind on which reps need what and when.

rev ops owns the data that makes diagnostic learning possible and they know which leading indicators actually predict performance at your company. they can tell you whether discovery call volume or demo-to-close ratio is the better early warning signal for a specific segment. they maintain the salesforce architecture that tracks this stuff.

the problem i see constantly: enablement builds a coaching program based on gut feel about what reps need, and rev ops builds dashboards that nobody in enablement ever looks at. two teams, staring at the same problem from different angles, never connecting their work.

the fix is straightforward but requires both teams to shift. rev ops needs to stop thinking of "reporting" and start thinking of it as "triggering." when a metric moves, what should happen next? that's a question they should be answering with enablement, not in isolation.

enablement needs to stop designing programs in a vacuum and start asking rev ops, "which 3 metrics should we be watching, and what thresholds should trigger a coaching intervention?" then build backward from those signals.

when i work with teams on this, the first session is usually just getting both functions in the same room with a whiteboard and mapping which metrics connect to which rep behaviors. it takes about 90 minutes. and almost every time, someone says something like, "i've been tracking this for months but nobody asked me what it meant."

you may need an audit to assess "cognitive coverage."

think of it as a spectrum. on one end, you have reps who can retrieve anything but recall nothing. they're dependent on tools and slow in live conversations. on the other end, you have reps who recall everything from 2019 and haven't updated their mental models since. both are a problem.

cognitive coverage means your reps can recall the patterns that matter most in live moments, and retrieve the details (pricing, product specs, competitive intel) when they have a few seconds to look them up. you're building for both.

the enablement question is: which patterns need to live in a rep's head, and which ones are fine to live in a tool? that's a judgment call that changes by role, segment, and sales motion. no surprise to hear an enterprise ae running a 9-month cycle needs different recall patterns than an smb rep closing in 14 days.

map the moments in your sales process where reps can't pause to look something up. those are your recall priorities. then build experiential programs around those specific moments and let diagnostic learning catch the reps who are drifting. and let the retrieval layer handle everything else.

that's cognitive coverage. and right now, most teams are only building half of it.

Opus 4.6

Extended

Claude is AI and can make mistakes. Please double-check responses.

‍