Why We Built Training Into the Knowledge Base

There’s a problem that shows up in almost every team I’ve worked with. You’ve got a knowledge base full of articles, processes, and policies. And then you’ve got a separate system for training. Maybe it’s an LMS. Maybe it’s a series of slide decks. Maybe it’s a shared folder full of PowerPoints that someone presented during orientation and nobody has touched since.

The training content says one thing. The knowledge base says another. Neither one is wrong, exactly. They just drifted apart because nobody had time to update both.

Two systems, one problem

The logic behind having a separate training system makes sense on paper. Training is structured. It has a sequence. You need to cover A before B, quiz people on C, and track who completed what. A knowledge base is more like a reference library. You search for what you need, read it, and move on.

But here’s what actually happens. Someone writes a great process document in the knowledge base. Then someone else copies parts of it into a training module. The training module gets a quiz. People complete it during their first week.

Six months later, the process changes. The article in the knowledge base gets updated. The training module doesn’t. New hires go through training, learn the old process, then discover it’s different when they actually start the job. Or worse, they don’t discover it. They just do it the wrong way until someone notices.

This is the fundamental problem with running two systems. The moment you have the same information in two places, one of them will fall behind. It’s not a question of discipline. It’s a question of time. Nobody has enough of it to maintain two copies of everything.

Where this actually came from

Before I started building KnowledgeScout, I was a Training and Quality Manager at a financial services contact centre. Forty people. Fast-moving organisation. Processes changed constantly because the industry required it.

Every time something changed, we’d build a slide deck. Walk the team through it in a huddle or a training session. Share it in a Teams chat. Job done, right?

Except three weeks later, nobody could find the deck. It was buried somewhere in a chat thread, or saved to a shared drive folder that made sense to the person who created it but nobody else. When a new starter joined, we’d scramble to pull together the “current” training materials, which usually meant digging through months of files and hoping we hadn’t missed an update.

We kept producing slide decks that went out of date almost as fast as we could make them. The information existed, but it was scattered across Teams, shared drives, and people’s memories. There was no single place where I could say “here’s everything you need to know, work through it in this order, and I’ll know when you’re done.”

That’s what I wanted. A system where the training material and the reference material were the same thing. Where I could build a structured path for new joiners and existing teams, point them at it, and trust that the content was current because it was the same content everyone used day to day. Not a copy. Not a slide deck that would be outdated by next month. The actual source of truth.

So we built Knowledge Paths

Knowledge Paths is our answer to this. It’s not a separate training module bolted onto the side of the knowledge base. It’s built into the same system, using the same content.

Here’s how it works in practice. You create a path, give it a title and description, and then add items to it. Those items are the articles and documents that already exist in your knowledge base. The same articles your team uses as day-to-day reference material. You arrange them in the order you want people to work through them.

You can enforce that order, so people have to complete step one before moving to step two. Or you can leave it flexible and let people jump around. It depends on the content. A compliance induction probably needs to be sequential. A collection of helpful resources for a new starter probably doesn’t.

Each path gets assigned to specific people with optional due dates. They see it in their dashboard. They work through it at their own pace. You can see who’s started, who’s in progress, who’s finished, and who’s overdue.

If you need to verify understanding, you add a quiz. You can attach one at the end of the path as an assessment, or include quiz articles at any point along the way. Quizzes are built right in, same editor, same system. You can choose whether people get to retake them or only get one shot.

And here’s the part that ties it together. Because the training content and the reference content are the same articles, there’s only one version to maintain. When you update a process article, every future path assignment uses the current version. You don’t have to remember to update a separate training module. There is no separate training module.

The chatbot detail that matters

We added something small that turned out to be surprisingly important. When someone is working through a Knowledge Path, you can restrict the AI chatbot for that path.

Why? Because if the path ends with a quiz and the chatbot can answer questions from the knowledge base, people will just ask the chatbot for the answers instead of reading the material. That defeats the point. With the restriction on, learners work through the content properly. Once they’ve completed the path, the chatbot works normally again.

It’s a small thing, but it’s the kind of detail that only becomes obvious when you’re actually using the feature for real training.

What this replaces

For a lot of teams, Knowledge Paths replaces the need for a separate LMS entirely. Not for everyone. If you need formal certifications, SCORM compliance, or complex branching course structures, you probably need a dedicated learning platform.

But if what you actually need is: “make sure new hires read these ten articles in order, quiz them on the key policies, track who’s completed what, and have the same content available as reference afterwards,” then you don’t need two systems for that. One will do.

That covers a lot of ground. Onboarding. Policy updates. Process training. Compliance tracking. Role-specific learning paths for different teams. All using content that your team is already maintaining as part of their normal knowledge base workflow.

The honest bit

Knowledge Paths doesn’t replace formal learning and development programs. It won’t produce certificates that satisfy external accreditation bodies. And it relies on your knowledge base content being good. If your articles are vague, outdated, or poorly structured, a path through them won’t fix that. It’ll just make it more obvious.

What it does well is remove the gap between “the stuff we train people on” and “the stuff we expect people to reference afterwards.” When those are the same thing, maintained in one place, the whole system stays healthier. Training stays current because your knowledge base stays current. And your knowledge base stays current because people are actively using it, not just for reference, but for learning.

That’s the idea. Training and knowledge in one place, maintained once, used for both.