Why Employees Are Not Using the Knowledge Base
Craig, a customer support agent at a software company, needs to help a customer who was charged twice. He searches the knowledge base for “refund” and gets seven results. Two contradict each other, and none clearly indicates which is current. The customer is waiting for an answer. So, he asks a coworker in the team chat.
The next time a question comes up, he starts with the team chat.
Three years ago, the business launched a knowledge base with several hundred articles to help employees resolve customer issues like this one. Since then, new products have arrived and various teams have added content.
When employees aren’t using the knowledge base, the organization loses an important tool for maintaining messaging and process consistency. Instead of relying on a shared source of truth, employees may be working from different answers, processes, and sources.
Three areas are worth examining: findability, trust, and adoption.
1. People Can’t Find What They Need
When users search but don’t get the right answer, or get too many confusing results, this may be because the knowledge base hasn’t been structured with findability and usability in mind.
When Craig needed information quickly to help a customer with a billing adjustment, he typed “refund.” The article he needed was titled “Billing Adjustment Policy.”
Addressing Findability Issues
Structuring the content with search optimization in mind can transform the knowledge base from a large repository of information into a valuable business asset. Check for these elements:
- User-centered titles, keywords, and synonyms. Content should use words that users actually use to search rather than terminology used by a business unit or project team.
- Clear, scannable, and modular content so that a user can find the specific answer they seek rather than burying the answers in long content.
- Content hierarchies that allow users to intuitively browse or drill down from general topics to specific answers. Good taxonomy reduces time spent guessing where to look.
- Metadata that fills the gaps. Tag articles with the words people use that the title doesn’t.
2. People Don’t Trust What They Find
The knowledge base may have started strong, but products and processes change. When the knowledge base isn’t maintained, problems grow over time. Without regular review and clear content ownership, duplicates accumulate, old articles are never retired, and gaps emerge. Eventually, users don’t know which answer is authoritative. The knowledge base slowly turns back into a large unusable repository.
When Craig searched for refund information, he found two contradictory articles. The lack of clarity about which was current caused uncertainty and lessened trust.
Keeping Content Trustworthy
Clear content ownership and governance are essential to maintaining content quality. Regular review cycles help avoid duplicates and archive obsolete content. Search analytics, zero-result searches, usage patterns, and user feedback can help identify where employees are struggling and whether improvements are working.
3. People Avoid Using the Knowledge Base
Even when findability and content quality improve, employees may continue using other workarounds. Habits such as asking a coworker or digging through folders can persist. Employees may not know what is available in the knowledge base or how to use it effectively. They may not think of it as their first destination for answers.
After Craig lost trust in the knowledge base, he began looking for answers in the team chat. Workaround habits like that may persist even after the underlying problems are fixed.
Improving Awareness and Adoption
Building a useful knowledge base doesn’t automatically mean employees will use it. Awareness, training, and reinforcement can help establish the knowledge base as part of their everyday workflow.
- Reinforce the importance of using the knowledge base as a single source of truth.
- Demonstrate successful use cases.
- Incorporate the knowledge base into everyday workflows.
- Remind users how the knowledge base can save them time.
- Conduct ongoing training.
- Invite and respond to user feedback.
A knowledge base isn’t finished when it’s built.
Keeping it useful and trusted requires ongoing attention
to findability, content quality, and adoption.
A few months later, Craig again needs billing policy information for a customer on the line. He starts to look through old chat messages but remembers hearing about recent improvements to the knowledge base. He searches there instead and quickly finds one clearly titled, recently approved article with the procedure he needs.
Next time, he searches the knowledge base first.