Onboarding that stopped the knowledge drain
The metrics didn't show a problem — but every time someone quit, their know-how left with them, and a new rep needed five months to perform. Structured onboarding plus a knowledge base with an owner cut that to two.
The company
A mid-sized provider of outsourced sales and customer-support teams — client companies hand over their sales or support function, and the provider's people run it. Quality is measured in customer satisfaction, response times, and resolution rates. People are the product.
The problem
On the surface, nothing was wrong — no metric pointed at anything specific. That was the problem itself: the damage sat in the structure, where dashboards don't look.
- Support and sales reps kept leaving — and every leaver took their knowledge with them. There was no place where it could stay.
- New hires built their own training out of questions to colleagues, scattered documents, and their own mistakes. Five months to reach normal performance — and everyone treated that as normal.
- Without structured onboarding, how prepared a new rep was depended on luck — and customer satisfaction, response times, and resolution quality suffered with it.
- Every team did the same processes a little differently, because there was no single place that said how things are done.
The real diagnosis wasn't in any report: weak onboarding, and no knowledge system under it. The kind of problem nobody names out loud, because fixing it is nobody's KPI.
What we did
The engagement started with symptoms — people leaving, service quality going down. We traced them back to the missing structure: knowledge that lived only in people, and onboarding that was basically "figure it out yourself". Naming that, and getting everyone to agree it was real, was the first result of the work.
A defined program instead of improvisation: training modules built for each role, and a mentor — an experienced rep — attached to every new hire for the first months, to connect the theory with the real work.
Every key process written down step-by-step — what to do, who is responsible, who to ask, who to inform — in modern knowledge tools instead of email threads and outdated files. And the part that makes it a system, not a pile of documents: an owner, an update process, and regular feedback. A knowledge base nobody maintains becomes useless within a year.
Cross-training and rotation paths, so people tired of one role could move to another — support to sales, role to role — with the knowledge base making the move cheap. Several people who were ready to leave stayed.
What changed
This problem never showed up in a dashboard — and no tool alone would have fixed it. The missing layer wasn't software: it was structure. Onboarding with a clear path, knowledge with an owner and an update process, transitions that don't start from zero. Sometimes the work starts with pointing at the thing nobody wanted to say. That's the layer we built.
Losing the know-how every time someone quits?
Write us what hurts. Within 24 hours: an honest answer whether we can help, and the next step if we can.
Get in Touch