Seven Executive Questions and Answers
Understanding Institutional Knowledge, key-person risk, and the experience organizations depend on.
1. How do we know if too much institutional knowledge is concentrated in a few employees?
Executive Overview - When the same few employees are consistently needed to answer difficult questions, make important decisions, or resolve unusual problems, your organization may be relying on knowledge that isn't widely shared. The concern isn't their expertise; it's what happens when they're no longer available.
A Closer Look
Think about the people in your organization everyone turns to when something doesn't go according to plan. It might be a longtime manager who remembers why a particular decision was made years ago. Maybe it's a technician who knows exactly what to do when a piece of equipment starts acting up. Or perhaps it's an employee who understands the history behind a difficult customer relationship. These people are valuable, and every organization needs them.
But here's a question worth asking: What happens when they're on vacation, unexpectedly absent, or decide to retire? If work slows down, decisions get delayed, or others struggle to find answers, you may have more knowledge concentrated in a few individuals than you realize. One way to recognize this is to notice how often the same names come up when employees need help. Look at which decisions consistently require certain individuals and which processes become difficult when those people aren't available.
The goal isn't to make experienced employees less important. It's to make sure the knowledge they've developed over the years doesn't become something the organization can no longer access when they're gone.
2. What happens when an experienced employee leaves and takes years of organizational knowledge with them?
Executive Overview - Replacing an experienced employee doesn't necessarily replace the knowledge they carried. Important customer history, decision-making experience, and practical understanding can disappear, leaving the organization to spend time and money rebuilding what it once knew.
A Closer Look
When an experienced employee leaves, most organizations focus on filling the position. They begin recruiting, redistribute responsibilities, and work to get things back to normal. But filling the position doesn't mean the new employee knows everything the former employee did. Consider a manager who spent twenty years building customer relationships. The new manager may be well qualified, but does that person know which customers require special attention, what promises were made years ago, or why certain decisions were made?
Or think about an experienced employee who knows how to handle unusual problems that rarely appear in a procedure manual. The organization may not recognize what's missing until something goes wrong. Suddenly, decisions take longer. Problems once resolved quickly now require additional research. Employees spend time searching for answers that someone in the organization already knew. And sometimes those consequences don't appear until months after the employee has left.
The challenge isn't simply replacing a person. It's understanding what knowledge and experience they may take with them and deciding how to preserve what matters before that happens.
3. How can we identify key-person risk before it becomes an operational problem?
Executive Overview - Key-person risk often goes unnoticed because everything appears to be working. One way to uncover it is to ask what would happen if a particular employee were unavailable tomorrow. Which decisions would stop, which relationships would suffer, and who else would know what to do?
A Closer Look
Most organizations have people who seem to know everything about a particular part of the business. They're dependable. They solve problems. Other employees trust their judgment. Over time, more and more responsibility naturally finds its way to them.
Because everything is working, nobody thinks much about it. But imagine that person doesn't come to work tomorrow. Not for a day or two, but for several weeks. Who takes over? Where do people go for answers? Which decisions have to wait? This is one of the simplest ways to begin identifying key-person risk.
It's also important to look beyond management positions. Sometimes the greatest dependency is a coordinator, technician, supervisor, or administrative employee whose knowledge has developed over many years. The organizational chart may show who reports to whom, but it doesn't always reveal who the business actually depends on when difficult situations arise. Once leadership recognizes those dependencies, it can begin determining which ones create meaningful exposure and what to do about them.
4. Why aren't our SOPs, training programs, and succession plans enough to protect institutional knowledge?
Executive Overview - SOPs explain how work should be done, training prepares employees to perform their responsibilities, and succession plans identify who comes next. But none of these necessarily captures the judgment, relationships, and years of experience behind important decisions. That's where organizations can still be exposed.
A Closer Look
Many organizations have invested considerable time and money developing procedures, training employees, and preparing future leaders.
Those are important investments, and they should continue. But think about the difference between knowing what a procedure says and understanding why someone might need to make a different decision when circumstances change.
An experienced manager may recognize that a particular customer requires a different approach because of something that happened years ago. A technician may notice an early warning sign that someone with less experience wouldn't recognize. These situations involve judgment developed through experience, and that judgment isn't always captured in a written procedure.
The same issue can arise with succession planning. An organization may know exactly who will replace a retiring executive. But has anyone identified the relationships, historical knowledge, and decision-making experience that executive relies on? Having someone ready to assume a position is important. Making sure that person has access to the knowledge needed to succeed is a separate responsibility.
The question isn't whether SOPs, training, and succession plans are valuable. They are. The question is whether they capture enough of the experience behind the work.
5. How can we transfer knowledge from experienced employees to the next generation of leaders?
Executive Overview - Knowledge transfer works best when experienced employees can share how they think, make decisions, and solve problems, rather than simply explaining how to perform a task. Mentoring, real-world examples, and conversations about past decisions can help preserve the understanding that years of experience have developed.
A Closer Look
Think about someone who has spent twenty or thirty years working in the same organization. Over those years, they've encountered difficult customers, unexpected operational problems, management changes, and decisions that didn't always turn out as expected.
They learned much of what they know from those experiences. Now imagine asking that person to write down everything they know. They probably couldn't. Not because they're unwilling, but because so much of their knowledge has become part of how they think and make decisions. That's why effective knowledge transfer requires more than asking employees to document their responsibilities.
Sometimes it means having an experienced manager walk a newer leader through a difficult decision and explain the reasoning behind it. Other times it means allowing someone to observe how an experienced employee handles an unusual situation. It can also involve discussing past mistakes, what was learned, and what the organization would do differently today.
The important thing is to create opportunities for that experience to be shared while the people who possess it are still available. You can't transfer thirty years of experience overnight. But you can start preserving the lessons, judgment, and understanding those years produced.
6. How do we determine which employee knowledge is important enough to preserve?
Executive Overview - Not all employee knowledge carries the same value or presents the same risk if lost. Prioritize knowledge that's hard to replace, held by few people, and essential to keeping the organization running. The greater the potential disruption, the more attention that knowledge deserves.
A Closer Look
If you asked every employee in an organization to document everything they know, you'd quickly create an enormous amount of information. Much of it would be useful. Some of it would already exist elsewhere. And some might never be needed again. The challenge is determining what really matters.
Start by asking what would happen if certain knowledge disappeared. Would an important customer relationship be affected? Would an operational process become difficult to manage? Could the organization repeat an expensive mistake because nobody remembers why a previous decision was made? Consider whether several employees already share that knowledge or whether only one person possesses it.
Also consider how difficult it would be to replace. Some information can be learned relatively quickly. Other knowledge may have taken decades to develop. And timing matters. If someone who holds important knowledge is preparing to retire, there may be less opportunity to preserve it. The objective isn't to capture every detail of an employee's career. It's to identify the knowledge that matters most to the organization and give it the attention it deserves.
7. Where should an organization begin if leadership suspects it has hidden dependencies?
Executive Overview - Start by examining one department or business function and identifying the people everyone depends on when something unexpected happens. Understanding who holds important knowledge, what could be disrupted if they're unavailable, and how that knowledge is shared gives leadership a practical starting point without launching a company-wide initiative.
A Closer Look
You don't need an organization-wide study to understand where important knowledge may be concentrated. Start with one department or business function. Talk with the people who work there. Ask what happens when something unusual comes up. Who do they call? Who knows the history behind certain decisions? Who understands the customer or vendor relationships that aren't fully explained in the company's records?
You may discover that some of the most important knowledge resides with employees who don't hold senior positions. Then ask a simple question: What would happen if those individuals were unavailable for an extended period? The answers can reveal where the organization depends heavily on knowledge that hasn't been widely shared.
From there, leadership can identify the most concerning dependencies, decide what knowledge to preserve, and determine who else needs access to it. There's no need to solve everything at once. The first objective is to understand where the organization may be exposed. Once those dependencies become visible, leadership can make informed decisions about what deserves attention.