The Sales Execution Gap

Tribal Knowledge: Your Best Rep's Motion, Trapped in Their Head

Tribal knowledge is the winning motion locked in your best reps' heads. Documenting it is half the job; getting every rep to run it is the half that counts.

Tribal knowledge is the unwritten, hard-won expertise your best reps carry in their heads, the order of the questions and the feel for when to push, and it is a risk because it is never captured, rarely shared, and walks out the door when they do.

Ask a great cook for the recipe and you get something useless: a list that says “season to taste” and “bake until it looks right.” The knowledge that makes the dish is in their hands, not the card. They could no more write it all down than you could write down how to ride a bicycle. The card is honest. It is also missing the part that matters.

Your best sales rep keeps a recipe exactly like that. The order they ask questions in. The pause they leave after the price. The instinct that a deal has gone silent for a reason. None of it is written anywhere. It is tribal knowledge, the unwritten motion that makes them your best rep, and it has a habit of leaving when they do.

Most teams treat this as a documentation chore: get it out of their heads, into a doc, done. That is half the job, and the easier half. Our position, and the throughline here: capturing the motion is the start, but tribal knowledge only pays off when every rep runs it in the moment, not when it is filed.

Where tribal knowledge lives: a row of sales reps with the best rep highlighted in magenta, and a callout noting that the order of the questions, the pause, and the when-to-walk instincts that make them effective are unwritten and live in no document
The motion that wins is already running in your best reps. It is unwritten, which is why it does not scale and walks out when they do.

What is tribal knowledge?

Tribal knowledge is the expertise a team carries informally, passed by demonstration and osmosis rather than written down. The philosopher Michael Polanyi gave it its sharpest definition in 1966: “we can know more than we can tell” (Polanyi, The Tacit Dimension). The skilled rep knows more about closing than they could ever dictate into a document, which is exactly why the document, when someone finally writes it, feels thin next to the person.

That gap carries a real cost, and it shows up in two places. The first is ramp. A new hire is handed the explicit half, the pricing and the slide deck, and left to reconstruct the tacit half by trial and error, which is slow and expensive. The second is loss. When a strong rep resigns, the explicit half stays and the tacit half leaves with them. Panopto’s workplace knowledge study put a number on the everyday version of this drain: employees lose around 5.3 hours every week waiting on knowledge held by a colleague or rebuilding expertise that already existed somewhere (Panopto, Valuing Workplace Knowledge). A day and a half a month, spent fetching what someone already knew.

There is a deeper reason this matters to us. The best process on your team is not a thing a consultant will sell you. It already exists, running inside your top performer, proven on real deals. The job is not to invent a motion. It is to find the one that already works and make it the standard everyone runs.

Why does documenting tribal knowledge fail?

Because writing it down moves it one step, and teams mistake that step for the finish. The motion goes from one person’s head into a document, which feels like progress, and in one sense it is: the knowledge now survives the person. But a document is not a behavior. The captured motion sits in a file, and the other reps go on selling the way they always did, because nothing reached them at the moment they were working.

This is the same wall every sales knowledge base hits. The answer exists, it is findable, and the rep on a live call still does not use it, because using it means stopping the work to go look. A documented motion has no advantage here. It is one more thing in the library that the busy rep drives past.

The doc was never the obstacle.

Capturing tribal knowledge is not transferring it: a three-stage diagram showing knowledge in the head (tacit, leaves when they leave), then in a doc (captured but unread), then in the work (acted on in the moment), with the gap between the doc and the work marked as the step nobody ships
Documenting moves tribal knowledge from the head to a doc. The step that changes results, from the doc into the work, is the one teams skip.

Forgetting finishes the job. Even the rep who reads the new motion in a training session sheds most of it within days, not from carelessness but from being human. So the captured knowledge sits in a doc, the rep half-remembers a worse version, and real tribal knowledge transfer never happens, because transfer is not telling someone once. It is the right move arriving when they need it.

When the motion does not spread, the cause is the system, not the people. Reps are not ignoring the playbook out of arrogance; the playbook never reached them where the work happens. As we argue in the sales execution gap, the fix is to deliver the motion into the flow, not to lecture harder about discipline.

How do you turn tribal knowledge into a standard?

Capture the motion from the people who already run it, then deliver it back to everyone at the moment of the work. The sequence is concrete, and none of it depends on willpower:

  • Capture the motion, not the memo. Watch your best rep’s real deals and name the steps they take. Experts cannot fully narrate their own skill, so observe it rather than interview for it.
  • Curate it to the next action. Strip the captured motion to the single next move a rep needs, not a forty-page binder. One clear step beats a complete manual nobody opens.
  • Deliver it in the flow of work. Surface that next step inside HubSpot, Salesforce, the inbox, wherever the rep already sells, so running the motion costs no detour.
  • Inspect whether it gets run. Measure adherence to the captured motion, then coach the gap. You cannot spread a standard you do not inspect, and inspection is what turns a good example into a team habit.
From your best rep to every rep: a magenta source node representing the best rep fanning out along gold standard lines to four navy nodes representing every other rep, showing the winning motion delivered as the standard everyone runs in the flow of work
The goal is not a tidy archive. It is the winning motion, captured once and run the same way by every rep, delivered in the flow.

That last step is where most knowledge sharing efforts die. A motion posted to a wiki and never inspected changes nothing; a motion delivered in the moment and measured for adherence becomes how the team sells. The difference is not the quality of the document. It is whether anyone built the path from the doc back into the work.

The payoff shows in the data. Our State of Sales Enablement found teams whose guidance lives in the flow of the work hit quota at 49 percent against 15 percent for teams whose knowledge sits in a separate destination (The State of Sales Enablement). The motion was the same; what changed was whether it reached the rep where they stood. When a century of tacit-knowledge research and our own field data agree that delivery in the moment is the deciding variable, that is the case worth betting on.

What we recommend

There are two ways to treat the expertise locked in your best people. You can leave it tacit and hope it rubs off, then absorb the slow ramps and the walkouts as a cost of doing business. Or you can capture the winning motion, deliver it back to every rep in the flow, and inspect whether it gets run, so the standard outlives any one person.

We recommend the second, and not as a hedge. The evidence is one-sided: expertise that stays tribal is fragile, leaks hours every week, and disappears with the people who hold it, while a captured motion delivered in the moment more than triples quota attainment over knowledge parked in a separate tool. Writing it down was never the finish line. Getting every rep to run it, while the work is in motion, is.

So find the motion that already works, capture it from the rep who runs it, and put it back in everyone’s hands at the moment they need it. Start with where that captured knowledge should live in the sales knowledge base, the daily discipline of it in sales process adoption, and the broader pattern in the sales execution gap.

Frequently asked questions

What is tribal knowledge?+
Tribal knowledge is the unwritten, hard-won expertise that lives in your most experienced people: the order they ask questions in, the moment they sense a deal is stalling, the phrase that unsticks a procurement review. It is real and valuable, and because it sits in their heads rather than in a system, it is fragile. It does not scale to new hires, and it leaves when the person leaves.
Why is tribal knowledge a problem?+
Because it makes your results depend on who happens to be in the room. A new rep ramps slowly because the motion that works was never written down, only demonstrated. A strong rep resigns and takes a piece of the playbook with them. And the team cannot improve a process nobody can see, because you cannot inspect or coach a motion that exists only as a habit in one person's hands.
How do you capture tribal knowledge?+
Start by observing the motion rather than interviewing for it, because experts cannot fully explain what they do. Watch your best rep's actual deals, name the steps they take, and write the sequence down. That captures it. But capture is only the first move: a document of the motion still has to reach every other rep at the moment they need it, or it sits unread like every other knowledge base.
What is the difference between tribal knowledge and a knowledge base?+
Tribal knowledge is the expertise before anyone writes it down; a knowledge base is one place teams try to store it once they do. Moving tribal knowledge into a knowledge base solves the storage problem, the knowledge now exists outside one person's head, but it does not solve the using problem. The captured motion only changes results when it is delivered back to reps in the flow of the work and the team inspects whether it gets run.
How is tribal knowledge transfer different from training?+
Training front-loads information in a classroom and hopes it sticks; most of it is forgotten within days. Tribal knowledge transfer works when the captured motion reaches the rep in the moment they need it, on the live deal, so the right next step is delivered rather than recalled. The test is not whether the rep was told, it is whether they ran the motion when it counted.

Your process, running itself.

Turn the playbook into rep behavior.

Book a demo Read The State of Sales Enablement