Knowledge Transfer: Telling Someone Is Not Transferring

A relay race is not won at the moment a runner reaches the next runner. It is won in the handoff, in the half-second when the baton has to pass from one fist into another at full speed. Watch a relay team lose, and nine times out of ten the runner was fast enough. The baton hit the ground in the exchange zone. The speed was there. The pass was not.

Knowledge transfer is that handoff, and most teams grade themselves on the wrong half of it. They count how fast the first runner ran: the doc written, the training delivered, the answer posted. That is real work, and it matters. But the race turns on whether the baton landed in the next hand at the moment it had to, while the second runner was already moving. Our position, and the spine of this piece: knowledge transfer is the result, not the act, and it has happened only when the receiver can use the knowledge when it counts.

What is knowledge transfer, and where does it break?

Knowledge transfer is the result of moving what one person knows to another, and it has happened only when the receiver can use that knowledge at the moment it counts. Telling is the attempt. Transfer is the landing.

This sounds like splitting hairs until you watch it fail in the open. A senior rep explains the renewal save play to the new hire over coffee. Clear, complete, generous. Both walk away certain the knowledge moved. Three weeks later the new rep is on a renewal call, the customer hints at leaving, and the play is gone. Not misremembered. Gone, the way a phone number you heard once is gone. The telling happened. The transfer did not.

Knowledge sharing is the act of making the answer available. Knowledge transfer is whether the next person could pick it up and run. The two get used as if they were one word, and that single confusion is why so many teams feel busy and starved at the same time. A wiki can be full and a team can still be guessing.

Why does knowledge fail to transfer even when everyone documents it?

Because memory works against you, and most teams have never once accounted for it. Hermann Ebbinghaus, working alone in the 1880s, memorized lists of nonsense syllables and then measured how fast he lost them. He found that forgetting is steep and early: we shed a large share of what we learn within the first days unless something pulls it back (Ebbinghaus and the forgetting curve). A thing told once is already half gone by the end of the week.

So picture the new rep again. The save play was handed over in a room, with full attention, on the day they started. By the time a real renewal call lands weeks later, the copy in their head has faded to a smudge, and there is no second delivery at the corner where they have to turn. The knowledge was real. The timing was fatal.

There is a cost to all of this, and it is measurable. Panopto’s workplace-knowledge study found employees lose roughly 5.3 hours every week waiting on knowledge a colleague holds or rebuilding something that already existed somewhere (Panopto, Valuing Workplace Knowledge). Those hours are the sound of knowledge that was shared, in the posting sense, and never transferred. Every one of them is a baton on the track.

And notice where the failure does not live. It is not that people refuse to teach, or refuse to learn. The teaching is happening. The receiving fails for two flat reasons:

• Wrong place. The answer sits somewhere the receiver has to leave their work to reach. A doc lives in a wiki; the call is in the dialer. Reaching it costs a detour, and a detour under pressure does not get taken.
• Wrong time. Even when the receiver did read it, they read it days or weeks before they needed it, and the forgetting curve did the rest. Availability and recall are different things, and only one of them is on the dashboard.

When the receiver does not use what was transferred, that is a system failure, not a discipline failure. The fix is structural, the same conclusion we reach in the sales execution gap: make the right answer arrive at the work, when the work happens, and the so-called motivation problem mostly evaporates.

What does real knowledge transfer look like in practice?

It looks like the second runner getting the baton at full speed, in the exchange zone, without breaking stride. Concretely, transfer is a delivery problem with four moves, and the order matters:

• Capture from the live motion. Pull the answer from the people running the real play, not from a tidy theory of it. The knowledge worth transferring is the tribal knowledge your best people carry in their hands, captured the way a coach films a swing rather than describing it.
• Deliver at the moment of need. Bring the answer to the receiver inside the tool where they work, the instant the situation calls for it, instead of waiting for them to remember it exists and go searching.
• Curate to one next step. Hand over the single move the moment requires, not a reading list. A precise answer in the moment beats a complete archive the receiver has to triage mid-call.
• Inspect whether it landed. Measure whether the receiver acted on the answer, not whether it was posted. Changed behavior is the only proof that transfer happened, and it is the one number almost nobody tracks.

That last move decides everything. A team measured on how much it documents will reward the first runner and never check the handoff. A team measured on whether the answer changed the next action is finally grading the pass.

Grade the pass, and the rest follows.

The picture has an edge worth naming. Not every piece of knowledge wants delivery in the moment, deep skill is built over time, not handed across in a baton pass. But for the operational answer the receiver needs while the work is moving, the moment of need is the only delivery time that transfers anything.

The proof that timing is the lever, not volume, sits in our own data. The 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 waits in a separate place (The State of Sales Enablement). Same content, same people. The difference was whether the baton reached the second runner while they were already moving.

What we recommend

Two ways to run this. You can keep grading the first runner, more docs, more trainings, a tidier wiki, and keep losing hours to a team that has been told everything and can recall almost none of it at the moment it matters. Or you can build for the handoff: capture the answer from the live motion, deliver it at the moment of need, curate it to one step, and inspect whether the receiver acted.

We recommend the second, and the evidence points one way. Memory sheds most of a one-time telling within days. Teams burn hours every week on knowledge that was published and never reached anyone. And answers delivered in the flow more than triple quota attainment over knowledge parked somewhere separate. Telling was never the hard part. Getting the answer to land in the next hand, at speed, is the work that turns telling into transfer.

So stop counting how much you tell and start watching whether it lands. The knowledge your best people hold is worth capturing first, and there is more on where that expertise lives and walks out the door in tribal knowledge, on the system that holds it in the internal knowledge base, and on the sales-specific build in the sales knowledge base.