There is one in almost every finance organization. The person who always has the answer. Who steps in when there’s a fire. Who rescues the month-end close when the system doesn’t cooperate. Who knows why account 47 has carried a balance for three years that no one else can explain. Who arrives in the morning first and leaves last in the evening, not because they have to, but because they feel that without them something would fall apart.
This person is valuable. They are loyal. They are indispensable.
And they are the largest operational risk your finance organization carries.
That is no criticism of the person. It is a statement about the structure. A finance organization that rests on a single person is no organization. It is a system built on personal resilience and collapses as soon as that resilience fades.
The term for this is single point of knowledge. It describes the state in which critical knowledge, operational competence, or systemic understanding is so strongly concentrated in a single person that their absence threatens the functioning of the entire department.
This article is for CFOs and finance directors who know this risk, who have perhaps already felt it, and who want to understand how it arises, why it is so hard to address, and what concretely needs to be done to eliminate it permanently.
How the Single Point of Knowledge Arises
The mistake most organizations make is believing that a single point of knowledge is the result of a conscious decision. It almost never is. It arises through a combination of habit, time pressure, and well-intentioned shortcuts.
It begins with someone being especially competent. He or she understands a system better than anyone else, has built a closing process from the ground up, or was there when a critical system configuration was implemented. This competence is real and valuable. The organization relies on it because it works.
Over time something shifts. What used to be a special competence becomes a routine dependency. When it’s about system X, you ask person A. When the year-end is delayed, you call person B. When account Y has an unexplained balance, only person C knows why.
These dependencies are not consciously created. They arise through time pressure, because it seems more efficient to ask the person who knows the answer than to find or document the answer yourself. They arise through trust, because a proven person seems more reliable than a process that would first have to be built. And they arise through omission, because no one explicitly decided that knowledge has to be documented or shared.
The result is an organization that looks stable from the outside and is fragile on the inside. The numbers are right, the closings come in on time, audits pass without major findings. But all of that only works because the right people are available on the right day. It is not a system. It is luck wearing a professional coat.
Why CFOs Underestimate This Risk
There is a psychological reason why CFOs systematically underestimate the single point of knowledge: it is invisible as long as it causes no problems.
The dependency on a key person is not captured in any risk register. It appears in no KPI dashboard. It surfaces in no audit report as long as the person is available. And since the person is available as long as everything is going well, there is no immediate occasion to address the problem.
The human mind, and therefore the CFO, weights risks heavily by how immediate and visible they are. A risk that could materialize in ten years receives less attention than a problem on the table today. That is rational in a world of limited resources and competing priorities. But it is dangerous when the risk materializes without warning and quickly.
That is exactly the characteristic of the single point of knowledge. It does not warn. It does not unfold slowly. It hits when the key person becomes ill, resigns, breaks down from overload, or is on vacation and unreachable. At that moment the risk is already reality.
As an interim manager I have experienced several situations in which an organization slipped into an acute crisis, not because of an external shock, not because of a strategic misjudgment, but because a single person was unavailable. In those moments it shows how fragile an organization really is and how little substance lies behind the stability presented to the outside.
What Is at Stake
Before a CFO can engage in a discussion about knowledge transfer and documentation, they must understand what is concretely at stake. This is not abstract. The consequences of an unaddressed single point of knowledge are concrete, measurable, and regularly observable in practice.
Closing Risk
The year-end close is the most critical deliverable of a finance organization. It is produced under time pressure, involves many parties, and relies on a multitude of processes, controls, and system configurations. If a key person fails during this phase, for instance the only one who understands the consolidation logic or has configured the interface between two systems, the entire close is at risk. That produces not only operational stress. It produces costs, reputational risk, and in some cases regulatory consequences.
Audit Risk
Auditors ask questions. They expect answers that don’t depend on a single person. A finance organization that responds to an auditor’s questions with “Only Ms. X knows that, but she’s not currently reachable” sends a signal that auditors register very precisely. It signals missing governance and missing process discipline. That raises the perceived risk profile of the organization and produces greater audit depth, greater audit effort, and therefore higher costs.
Knowledge Departure
When a key person leaves the organization, not through breakdown but through a deliberate decision, they take their knowledge with them. What was not documented, what was not passed on, what existed only in their head, is lost. Or has to be reconstructed at significant effort. And the reconstruction is more expensive than the original documentation would have been.
Innovation Inhibition
An organization that depends on individuals cannot fully deploy these individuals. The key person is so deeply embedded in operational work that they have no capacity to improve processes, introduce new methods, or think strategically. They are the fire brigade, not the architect. That is a waste of competence with long-term consequences.
Loss of Motivation in the Key Person
This is most often overlooked. The key person themselves suffers from the dependency. They cannot take a vacation without phone calls. They cannot be sick without a guilty conscience. They are constantly confronted with the same questions and cannot develop further because the organization holds them in their current role. That leads sooner or later to exhaustion, inner resignation, or the departure the organization can least afford.
The Signals That Announce a Single Point of Knowledge
There are clear signals that indicate a finance organization carries a single-point-of-knowledge risk. As CFO these signals should immediately attract attention.
The first signal is linguistic in nature. When sentences fall regularly in an organization like “That only works with person X”, “Only person Y knows that”, or “We’d have to ask person Z about that”, that is a direct indicator. These sentences are not a harmless description of competence distribution. They describe a dependency that constitutes a risk.
The second signal is structural in nature. When controls exist in the form of verbal assurances rather than documented processes, when operational routines cannot be explained but only executed, when system configurations are fully understood by only one person, then the knowledge is not anchored in the organization. It is anchored in a person.
The third signal is cultural in nature. When in a team no one but one person is able to answer auditors’ questions, when the absence of the key person creates uncertainty that limits the team’s ability to work, then the organization is dependent on this person to a degree that is not acceptable.
The fourth signal is organizational in nature. When the key person’s vacations are repeatedly postponed, when sick days lead to crises, when the person regularly has to be available evenings and weekends to keep things running, then the dependency is already so deeply rooted that it is operationally felt.
Why Knowledge Transfer Fails
The natural reflex when a CFO recognizes the single point of knowledge is the decision to transfer knowledge. Create documentation. Describe processes. Run training. That sounds simple and still does not lead to the desired result in the majority of cases.
The most common reason is a misunderstanding of what knowledge is. Knowledge in a finance organization is not only what stands in process descriptions. It is also implicit knowledge, experiential knowledge, contextual knowledge. It is the knowledge of why a posting logic was chosen the way it was, which exceptions exist and why, what goes wrong in certain situations and how to avoid it, and which informal channels and relationships exist that keep the system running.
This implicit knowledge cannot be written into a document. It must be experienced, tried out, and gradually transferred. That requires time, structure, and an explicit decision by leadership that this transfer has priority.
The second common reason knowledge transfer fails is the attitude of the key person themselves. That is a sensitive topic that is not openly addressed in most organizations. A person who has been the indispensable expert for years may experience knowledge transfer as a threat. As a signal that they are to be replaced. As a loss of the recognition that comes with their uniqueness.
This perception is human and understandable. And it is wrong in most cases. But until it is addressed and resolved, it has effect. Knowledge is then not actively withheld, but also not actively shared. Documentation stays superficial. Training stays abstract. The transfer happens formally but not substantively.
The third reason is organizational in nature. Knowledge transfer requires capacity. The key person needs time to share their knowledge. Those who are supposed to absorb the knowledge need time to absorb it. And all of this has to happen in parallel with the ongoing day-to-day business that takes no breaks.
In a finance organization under pressure, this capacity is often not available. Or it is not explicitly created. Knowledge transfer is treated as a project alongside the day-to-day, and since the day-to-day always seems more urgent, the project systematically loses against the everyday.
What CFOs Concretely Must Do
Addressing the single point of knowledge is not an HR task and not a process optimization task. It is a leadership task. It begins with a decision by the CFO that this risk is unacceptable and that its elimination has priority.
This decision must be visible. It must be communicated. And it must be backed with resources, otherwise it is a statement of intent without substance.
What then concretely needs to be done can be structured in four phases that build on each other and that together ensure knowledge is sustainably anchored in the organization.
Phase 1: Make Knowledge Visible
Before knowledge can be transferred, it must be known what knowledge exists and where it is concentrated. That is no trivial task. Implicit knowledge is by definition not visible. It must be made explicit.
That begins with a structured analysis of the critical processes, systems, and decisions in the finance organization. For each of these areas the question must be answered: Who in the organization can fully explain this process, fully administer this system, fully justify this decision?
If the answer is “only one person”, that is a single point of knowledge. If the answer is “no one but person X really fully”, it is the same.
The analysis must be honest. That requires psychological safety in the organization. No one should be afraid to name a single point of knowledge because that could be interpreted as personal failure. The CFO’s task is to create that frame.
The result of this analysis is a map of critical knowledge in the organization. It shows where the largest risks lie, which processes and systems depend on individuals, and which areas need to be addressed with what priority.
Phase 2: Document and Structure Knowledge
Knowledge that has been identified must be documented. But not in the form most organizations understand as documentation: a Word document describing what someone does. That is description, not documentation.
Effective documentation describes not only what is done but why. It explains the logic behind decisions, the exceptions and their justifications, the risks that can arise at certain steps, and the control points that ensure the result is correct.
It also describes the contextual knowledge: Which systems are involved? Which interfaces exist? Which informal dependencies exist? Which historical decisions explain why a process is shaped the way it is?
This documentation must be created by the key person themselves, not by someone watching and writing down.
The reason is simple: only the key person knows the implicit knowledge that has to flow into the documentation. Someone watching sees what is being done. They don’t see why and they don’t see the exceptions that didn’t occur this week but can occur.
That means the key person needs capacity for this task. Time that is not filled with operational work. That is the first concrete resource decision a CFO must make.
Phase 3: Transfer and Anchor Knowledge
Documentation is necessary but not sufficient. Knowledge is not transferred through reading. It is transferred through application.
That means a second person must not only read the documentation but execute the process themselves, accompanied by the key person, with real data, under real conditions. Only when the second person is able to execute the process independently and correctly is the knowledge transferred.
This transfer process must be structured. It must occur in phases: first observe, then accompany, then execute themselves with support, then execute themselves without support. Each of these phases must be explicitly planned and time-anchored.
An important aspect is the role of the key person in this process. Their goal is no longer operational execution. Their goal is quality assurance. They check whether the second person executes the task correctly, give feedback when something is missing or wrong, and gradually withdraw when convinced that the knowledge has truly been transferred.
This role shift must be explicitly communicated and acknowledged. The key person gives something up. That must be recognized as a contribution to organizational strength, not as a loss of status or relevance.
Phase 4: Institutionalize and Maintain Knowledge
The most common mistake after a knowledge transfer is the assumption that the task is done. Knowledge ages. Systems change. Processes evolve. Regulatory requirements grow. What was documented and transferred today may no longer be current in two years.
Institutionalized knowledge management ensures that documentation is regularly reviewed and updated. It defines who is responsible for maintenance, in what rhythm the review takes place, and what process applies when something changes.
In addition, the transferred knowledge must be regularly activated. A second person who hasn’t executed the process they learned for a year may have forgotten parts of it. Regular exercises, simulations, or systematic rotations ensure that the knowledge stays alive and not just lives in a document.
The CFO’s Role as Architect of Knowledge Stability
There is a temptation many CFOs know: delegate the problem to someone else. To HR, to the head of accounting, to a process manager. That is understandable. The CFO has other priorities, other topics, other construction sites.
But eliminating the single point of knowledge is not a task that can be delegated. Not because execution has to be done by the CFO personally, but because the problem is not solved without visible prioritization by leadership.
The reason is the dynamic that arises around key persons. A key person has the implicit support of the organization for their status as the indispensable expert. They did not attain this status through a conscious decision, but they sustain it because it gives them a certain security. If knowledge transfer is driven only by a middle manager, the signal that leadership really wants this is missing. That is not enough.
When the CFO personally communicates that knowledge stability is a strategic goal, that the transfer should occur within a defined timeframe, and that the key person will be supported and not threatened in this process, the dynamic shifts. The key person understands that the decision has been made. The department understands that it is a priority. And all participants align their behavior accordingly.
What an Interim Manager Can Achieve in This Situation
There are situations in which knowledge transfer cannot be managed internally. That happens when the single point of knowledge has already materialized, meaning the key person has failed, the organization is in crisis, and there is no time to systematically build knowledge. It also happens when the internal capacity to structure and accompany the transfer is missing, or when the key person and leadership are caught in a dynamic that prevents open addressing of the problem.
In these situations an experienced interim manager can play a decisive role. Not as a replacement for the key person, but as a stabilizer who bridges the crisis and at the same time creates the foundations for a sustainable solution.
An interim manager brings the outside view. They see what is no longer seen internally because it has become normal. They can name the dependencies without being trapped in the internal dynamics. They can structure and accompany the knowledge transfer without threatening the key person, because they are not a permanent competitor.
And they can build the institutional memory that remains in the organization after their departure. Process documentation, governance structures, control mechanisms, training materials. What an interim manager leaves behind is not the solution to the problem itself. It is the structure that prevents the problem from coming back.
What an Organization Gains When It Solves the Problem
Eliminating the single point of knowledge is not a defensive measure. It is an investment in organizational strength that pays off across multiple dimensions.
A finance organization that has anchored its critical knowledge broadly is more resilient. It can absorb personnel changes without slipping into a crisis. It can handle vacations, illnesses, and departures without operations suffering. It is more stable, more reliable, and more trustworthy toward auditors and management.
It is also more efficient. When several people are able to execute critical processes, redundancy emerges that acts as a buffer. Bottlenecks become rarer. The load distributes more evenly. And the key person gains capacity for tasks that go beyond operational execution.
And it is more capable of innovation. Knowledge that is shared is questioned. Processes that several people know are evaluated by several people. That produces a healthy critical engagement that leads to improvements that would never emerge in a system where only one person understands everything.
What I Bring
I am Nicole Vekonj, interim manager for finance & controlling. I accompany finance organizations in identifying operational dependencies, transferring knowledge in a structured way, and building governance structures that ensure critical knowledge stays anchored in the organization, not in individual people.
My approach starts with an honest situational picture: Where are the real dependencies? Which knowledge is at risk? And what needs to be done before the risk materializes?
Asking these questions costs little. Not asking them can cost a great deal.
You recognize a person in your finance organization without whom nothing runs?
Let’s talk for 30 minutes before the worst case occurs.
Nicole Vekonj | Interim Manager Finance & Controlling | zahlenkompetenz.de
