The Procedure Changed. Half Your Floor Didn't.

A process change lands on Tuesday. Compliance has signed it off. The article is updated. Someone posts the link in Teams, a few people react, and by lunch it feels done.

By Thursday, QA is listening to calls where agents are still quoting the old rule. The cooling-off period. The hardship steps. The fee waiver threshold that moved last week. Customers are getting two different answers depending on who picked up.

The knowledge base is current. The floor isn’t. That’s the gap most teams treat as a training problem, or a people problem. It isn’t. It’s what happens when you treat a knowledge update like a software deploy. Push it, it’s live, job done. People don’t work like that.

Publishing is not landing

Most teams measure the update by the moment it went out. Email sent. Article saved. Link shared. The system says the new version exists, so everyone gets to believe everyone knows.

What actually happens is messier. The old answer is still in muscle memory. It’s on the printed cheat sheet taped under a monitor. It’s in the buddy they sit next to, who trained last year and hasn’t re-read the page. It’s in last month’s onboarding path that nobody sent people through again. Search still returns the new article, and the person who already thinks they know the answer never searches.

So you end up with two sources of truth. One sitting in the tool. One sitting in people’s heads. On a quiet day they match. On a change week they don’t, and that’s exactly when it matters.

This is worse in regulated work, because inconsistency isn’t just a quality miss. Two customers, same situation, different outcomes. That’s the start of a complaint, a remediation file, or a very awkward conversation with Risk.

What actually closes the gap

The teams that land changes do a few plain things, every time.

There is one current version. The old one is a record, not a search result that looks equally valid. If three pages still describe the process, two of them slightly differently, you haven’t updated anything. You’ve added a fourth opinion.

The people who need to know are asked, not hoped. A Teams post is a suggestion. Required reading with a list of who hasn’t confirmed is a job. You still can’t prove they understood it from a tick. We’ve written about that. You can at least stop pretending a thumbs-up in chat is a rollout.

Someone owns the page after it’s published. Review dates aren’t bureaucracy. They’re how you find the article that drifted while everyone assumed it was fine. An update without an owner is an update that will be stale again in six months, quietly.

The same change has to reach every door in. Humans searching. The widget in the CRM. Any AI sitting on the content. If the article is current and the bot is still answering from last month’s version, you haven’t finished the update. You’ve split the truth again.

None of this is clever. It’s the follow-through most wikis never grew, which is why they rot. “We have a knowledge base” and “the floor follows the current process” are two different sentences.

The honest bit

A tool can put the new version in one place, flag it as required reading, notify people, and show you who hasn’t confirmed. We built those things because I watched this gap eat quality scores for years.

What a tool cannot do is sit next to someone on the next call and stop them quoting Monday’s version. Coaching and QA still exist. A notification only works if someone looks at it. An acknowledgement is not a changed behaviour. Anyone selling you a product that “makes sure the floor always follows the latest process” is selling a fantasy.

The job is to close the gap a tool can close: one current version, a record of who was asked to read it, a review date so it doesn’t drift, and the same answer whether a human, a widget, or an AI is doing the looking. The last mile is still people. That’s not a cop-out. That’s just the job.

If you’re running quality on a contact centre floor, you already know this sentence: the process was published, and the agent didn’t follow it. The publication isn’t the failure. The landing is. That’s the gap we built for.

The KnowledgeScout Team