Staying Steady in the Storm: Why Knowledge Management is the Secret to 2026 Customer Service Resilience
In the world of customer service contact centers, companies spend considerable time and money forecasting contact volumes. But that can be all blown up when a single viral tweet or a minor software glitch in a partner’s API sends a contact center into a tailspin within minutes.
To survive, organizations are turning to a framework originally used by the military to describe the chaos of the battlefield: VUCA. One of the best tools to manage this is Knowledge Management (KM).
What is a VUCA World?
If you haven't encountered the term before, VUCA is an acronym that describes an environment that is:
Volatility: The speed, volume, and magnitude of change. In customer service, this looks like a sudden 400% spike in tickets due to an unforeseen global event.
Uncertainty: The lack of predictability. You know something might happen, but you have no idea when or what the impact will be.
Complexity: The "tangled web" of modern business. Problems aren't just A causing B; they involve five different third-party vendors, shifting regulations, and hybrid workforces.
Ambiguity: The "fog of war." Even when you have data, the meaning is unclear. There is no historical precedent for the problem you’re facing today.
The U.S. Army War College first used the term VUCA in 1987 to describe the shifting, post-Cold War world, replacing the stable US vs. USSR dynamic with a more chaotic reality where traditional military doctrine failed. By the early 2000s, and especially after the 2008 financial crisis, the concept entered the business world.
The same unpredictability and interconnectedness defining modern warfare are also defining features of the global economy. This requires companies to shift from rigid plans to agile, knowledge-based resilience. As new tools and new players drive change, organizations must become ever more adaptable.
The Resilience Gap
Resilience isn't just "bouncing back.” It's the ability to absorb shocks and adapt without service levels collapsing. Without a robust KM strategy, organizations face a resilience gap.
Here’s a volatile situation that will likely be familiar: Your contact center experiences a sudden, massive spike in volume. The speed and magnitude of this overwhelms your standard staffing levels and disrupts normal operations. Soon, your team figures out it’s related to a global platform outage caused by a faulty update. You’re uncertain how long the outage will last, or what the full impact will be on different customer segments.
Your teams are working to resolve the issue, but it’s a complex, tangled web involving third-party software vendors, internal IT departments, and maybe even shifting regulatory requirements. Agents have to navigate multiple systems and coordinate with various teams to provide even basic updates.
The ambiguity that arises is the fog of war. Early data from the field may be conflicting; a workaround that works for one customer might fail for another, and the meaning of the technical errors remains unclear in the first several hours.
When a VUCA event hits, shadow knowledge (the stuff only your senior agents know) becomes a bottleneck. If the experts are overwhelmed or offline, the rest of the team is left guessing. This leads to inconsistent answers, burned-out agents, and frustrated customers.
In this scenario, a robust KM strategy acts as a nervous system, allowing the organization to react in real-time by providing a centralized, living source of information for all agents as workarounds are discovered.
How KM Fosters Resilience: The VUCA Antidote
When things are volatile, they move fast, so knowledge must move faster. A centralized, cloud-based knowledge management system (KMS) ensures that as soon as a workaround is found for a new issue, every agent—whether in Lagos, Manila, or a home office in Texas—has it instantly.
Resilient organizations neutralize uncertainty with a living knowledge ecosystem. Instead of lengthy approval cycles, they centralize knowledge but decentralize authoring using frameworks like Knowledge-Centered Service (KCS), where agents update the knowledge base as they work. Documentation reflects the best known steps right now, which can be refined with new data.
Complexity often stems from information silos. By integrating your KMS with CRM and AI-powered search, agents don't have to hunt through five different tabs. Modern KM systems can reduce the time agents spend searching for info by up to 35%, freeing up cognitive bandwidth to handle the actual human element of the call.
In 2026, KM isn't just a library; it's a collaborative intelligence system. Modern platforms allow for subject matter expert (SME) tagging and real-time feedback loops. When a situation is ambiguous, agents can quickly provide feedback and document new workarounds that then flow immediately to the right person.
The 2026 Edge: AI-Augmented Knowledge
We can't talk about KM today without mentioning AI. In a VUCA world, AI acts as your "Sense and Respond" layer.
Generative Answering: Synthesizes complex articles into a single, actionable sentence for the agent.
Gap Analysis: AI identifies what customers are asking that isn't in your knowledge base yet.
Automated Translation: Instantly localizes emergency updates for global teams, removing language barriers in a crisis.
The KM Resilience Audit: Moving from Reactive to Proactive
To transition from merely reacting to navigating the storm with foresight, conduct a KM resilience audit. Your findings will allow you to assess the health of your knowledge infrastructure against VUCA challenges and identify specific, actionable gaps.
Audit for Shadow Knowledge: Formalize undocumented knowledge that creates single points of failure. Identify three critical processes that currently live only in the heads of senior agents. These are often complex, high-value, or high-risk scenarios like billing exceptions or coordinating a regulatory-sensitive customer complaint. Once identified, use KCS-aligned practices to document these processes into verified, centralized articles, mitigating the "team lore" bottleneck.
Check the Latency: Accelerate the time-to-knowledge in a crisis. Measure how long it takes from a new issue appearing to a verified solution or official workaround being available in your KB. A high latency indicates poor knowledge workflow. Implement a tiered documentation strategy where best known steps are published within minutes, followed by a more formal, refined article within hours.
Feedback Loops: Maintain the quality and accuracy of knowledge in a rapidly changing environment by ensuring agents can flag outdated content with one click. This immediate feedback mechanism shouldn’t interrupt the customer interaction, but it must instantly alert a designated Subject Matter Expert (SME). A robust feedback loop ensures the knowledge base is a dynamic, living system rather than a static repository, directly addressing the ambiguity and volatility inherent in a VUCA event.
Resilience isn’t a one-time project; it’s a cultural shift. By treating knowledge as a dynamic asset rather than a static filing cabinet, customer service organizations can stop fearing the "VUCA" world and start navigating it with confidence. When your team knows how to find what they need, the chaos of the world becomes a lot less intimidating.
Stop Counting "Page Views": How to Prove Your KB’s Value to the CFO
Picture this: a budget meeting where a well-meaning Knowledge Manager proudly displays a chart showing "Article Views" trending upward and to the right.
Now, picture this: The CFO’s eyes glazing over.
One thing I’ve learned in my time as a well-meaning Knowledge Manager: Your CFO doesn't care about page views. They care about the bottom line. If you want to secure a budget for a new platform or a dedicated Knowledge Curator, you have to speak their language. You have to stop reporting on activity and start reporting on value.
Here is how to calculate the real ROI of your Knowledge Base.
The Hard Metrics: Deflection and Efficiency
When you walk into that finance meeting, bring two numbers: Ticket Deflection and Average Handle Time (AHT).
Ticket Deflection is the holy grail. If a customer finds the answer on your self-service portal, that is a support ticket that never happens. It’s a cost avoided entirely.
AHT Reduction is where you prove efficiency. If your agents can find the right answer in 30 seconds instead of digging through a digital landfill for 3 minutes, you’re saving money on every interaction.
Let’s look at the math. In my book, MVP KB, I use a fictional company, Moxy Solar, to illustrate this. Let’s say a contact center handles 505,000 requests per year. If you implement a knowledge strategy that drives a 10% reduction in AHT, you aren't just saving time, you’re saving over $200,000 annually.
That’s a number that wakes a CFO up.
The Soft Metrics: The Human Element
While the hard dollars get the budget approved, the "soft" metrics determine if your system actually survives. These measure the health of your operation and the sanity of your team.
Time to Proficiency: How long does it take a new hire to stop asking their neighbor for help and start answering tickets solo? I’ve seen organizations where onboarding took 16 weeks because new hires had to rely on "tribal knowledge." A solid KB can cut that ramp-up time significantly, sometimes by as much as 25%,.
Search Failure Rate: This is a metric I watch like a hawk. It tracks how often a user searches for a term and gets zero results (or clicks nothing). A high failure rate means your agents are frustrated and your customers are dead-ends.
Employee Engagement: When agents have the tools to do their jobs, they stay longer. When they don't, they burn out. High turnover is a hidden tax on your budget that a good KB can help alleviate.
A Warning: Don’t Die by the Spreadsheet
Finally, a word of caution. While I love a good ROI calculation, focusing solely on ROI can backfire. If you treat knowledge management purely as a cost-cutting exercise, you risk stripping away the human judgment and wisdom that actually solves complex problems.
You need to pair your data with anecdotal evidence. Capture the wins. Did a specific knowledge article help an agent save a high-value account from churning? Did a new troubleshooting guide help the engineering team identify a bug faster?
ROI gets you the funding, but the stories are what build the culture.
Ready to build a business case that actually gets signed? Let’s talk.
Beyond the Checklist: The Truth About KM Maturity Models
Is it worthwhile to do a KM Maturity Assessment?
A client recently asked which maturity model would be best to follow when assessing an organization’s KM functionality. It’s an excellent question. Answering it is made all the more complex because of the debate around how useful a maturity model really is.
If you’re not familiar with what a maturity model is, think of it as a rating system for how capable an organization is for fulfilling some sort of function. In the business world, common frameworks include the Capability Maturity Model Integration (CMMI) for software development, the Business Process Maturity Model (BPMM) for process improvement, or the Agile ISO Maturity Model (AIMM).
In the knowledge management world, two of the better-known maturity models are the APQC’s Levels of Knowledge Management Maturity (LKMM) and the KMI’s Knowledge Management Maturity Model (KMMM).
Both are the same in that they assess organizational KM capabilities from level 1 (initial/ad hoc) to Level 5 (embedded/optimized). The two approaches have different labels for levels two through four, but the concepts are all fairly similar.
LKMM is highly detailed and focused on enterprise-wide initiatives; it’s great for a highly-structured, benchmark focused approach. KMMM, on the other hand, is more process-centered and feeds into a step-by-step approach for improving KM.
I’m partial to the KMMM model because I got my certification through KMI. It’s also lighter; there are 60 or so questions. LKMM is a mutli-sheet spreadsheet of multiple measures per tab – more than 100 all told.
In the KM world, there’s a fairly robust discourse around the pros and cons of maturity models. While they can be useful tools that provide great insights and clear metrics, it’s easy for them to become overly rigid and cause organizations to overlook less measurable things like culture.
That’s why I look at the maturity model assessment as one of many tools in the box. In my experience, KM isn’t often a “tree model” – it doesn’t grow in neat stages, like a tree adding rings. Instead, it’s more like a forest fire. It starts in small pockets and then (with the right conditions) it spreads throughout the org.
You need to understand the condition of your KM ecosystem, and a maturity model is one way to diagnose what’s needed; it’s not the whole treatment plan though. It’s a snapshot that’s useful in creating a shared understanding. It’s something that should be adapted to organizational reality and focused on enabling behaviors and culture, not just documenting processes and resources.
My approach with clients is to do a short survey of stakeholders and leadership using a KMMM-bassed questionnaire, and follow that with more in-depth conversations around KM with as many stakeholders as possible. I’ve found that approach gives a clear snapshot of the current state, but also lays the groundwork for the type of cultural change required for real KM transformation.
Interested in learning more about how to approach your own maturity assessment? Get in touch!
Your Knowledge Base Is Failing. The Reason Is People (And the Fix Is, Too).
One of the biggest misconceptions I see in customer service is the belief that creating a successful knowledge base is a technology problem. The thinking goes: find the right software, populate it with a few documents, and you're set. In my experience, this approach is one of the single biggest predictors of failure for a knowledge base project.
If you don't put serious thought into the people who will create, maintain, and share knowledge, your project is doomed from the start.
The "Set It and Forget It" Graveyard
I once met with a client in 2024 to discuss their knowledge management ecosystem. They showed me their knowledge base, and as I scanned the list of articles, I noticed the "published" date for nearly every single one was from 2017. I told them, "Well, I know why nobody wants to use your knowledge base. Your content is ancient.".
This is a classic example of the "set it and forget it" mindset that plagues so many organizations. They focus on the system and the initial content load, but give little thought to how that content will be managed over time. This reluctance to invest in the people who maintain the content is a critical mistake.
The Old, Broken Model
The legacy approach to knowledge management often involved fairly heavy staffing. You'd have a knowledge manager and a team of technical writers responsible for managing all, or at least most, of the content. When a new support issue was identified, a tech writer would have to work with a subject matter expert (SME) to get a draft into shape, often leading to a long back-and-forth process. After all that, the article would still have to wait for a manager's review before it could be published.
This system extends the content publishing cycle from what could be hours or days into weeks or even months. By the time the information is available, it might already be obsolete.
A Better Way: Source Knowledge from the Front Line
The solution is to flip the model on its head. Empower the people on the front lines—your agents and SMEs within that population—to create and share knowledge directly.
This doesn't mean every agent needs to be a polished writer. But every single agent is skilled at recognizing knowledge gaps or incorrect information when a supposed solution fails with a customer. More tenured agents, in particular, are perfectly suited to share new knowledge and help review updates.
This is why I strongly advocate for creating two key roles within your organization: the
Knowledge Contributor and the Knowledge Curator.
Knowledge Contributors: These are not full-time positions. These are roles filled by your experienced Tier 2 or Tier 3 agents who have the tenure and deep knowledge of how things are supposed to work—and what to do when they break. With modern, AI-infused knowledge management systems, these contributors don't have to be expert writers. AI can help format their insights, which can then be passed to a curator for review.
Knowledge Curators: Like contributors, curators are not full-time staff dedicated solely to the knowledge base. Curation is simply a subset of their job. They review contributions for accuracy and also manage the feedback coming in from the wider agent population. It's crucial that when a frontline agent provides feedback on an article, it doesn't just go into a void. Curators ensure that feedback is reviewed and applied, closing the loop and continuously improving your content.
From Top-Down to Bottom-Up
By adopting this approach, you stop pushing knowledge from the top down and start sourcing it organically from the bottom up. This has massive benefits. Companies that adopt similar people-centric approaches like the Knowledge-Centered Service (KCS®) methodology have seen a 30–50% reduction in time to resolve issues, a 20% improvement in employee retention, and 70 percent faster time to proficiency for new agents.
This model engages your employees in a powerful new way. It allows them to share their hard-won expertise and develop new skills, helping them to further their careers. Even newer agents can be engaged by giving them easy-to-use tools to provide detailed written feedback on articles, knowing that a curator will see it and act on it.
Stop thinking about your knowledge base as a library and start thinking about it as a living, breathing part of your team. Invest in your people, and you’ll build a knowledge practice that actually works.