How Many People Does Your Company’s Future Walk On?
A company’s critical functioning always depends on someone. It becomes a problem when it depends on very few, and that knowledge is written down nowhere. A concentration of critical skills in a handful of heads is a risk that appears in no register, until one of those people leaves. At that point the company’s future turns out to be more fragile than the org chart suggested.
The Standard, London. Photo by Raissa Pardini
The customer you knew no longer exists
In Italian small and midsize companies, expertise lives in people more than in systems. There is the production manager who also handles commercial emergencies, because they are the only one who knows the real lead times. There is the assistant who sorts the owner’s decisions, because they know who can do what. There is the engineer who keeps the most exposed clients, because they hold both the relationships and the competence to do it. On the org chart they are boxes among many. In practice, the company’s critical functioning walks on their feet.
This concentration begins as efficiency. In a company of this size, writing down what anyone can ask at the next desk would be a cost with no return. Decisions move, knowledge is within reach, the structure stays light. The arrangement holds as long as the company stays inside a certain perimeter. When the perimeter widens, through new clients, added complexity, or a new ambition, the same people hold more than is prudent, and the rest of the organization has learned to depend on them.
The Map That Counts Sits Beneath the Org Chart
The org chart describes hierarchy and roles. It says who reports to whom. It stays silent on who actually knows what, on who others turn to when something breaks, on who has to be in the room for a decision to close. The two maps rarely line up. A role can sit high on the chart and matter little in the work. A person can be nearly invisible in the structure and indispensable in the daily flow.
The gap matters because the risk lives in the second map. When expertise concentrates, the company develops load-bearing nodes. If one of them slows down, takes leave, or leaves, the effect shows up immediately in the work. A process that jams, a client with no point of contact, a decision left hanging because no one else can make it.
Leadership senses these nodes. They know that without Maria a department stalls, that Luca is the point half the company converges on. The intuition stays anecdotal, no one turns it into a map. Otherwise the nodes show only in moments of friction, when a task sits idle waiting for a single signature or a technical question bounces all the way to one desk. The rest of the time, concentration looks like reliability, and a machine that keeps running invites no one to look inside it.
The Continuity Plan
Almost every continuity plan assumes that knowledge is documented and transferable. It lists procedures, names backups, defines escalation paths. The assumption holds only when expertise actually lives in the system. When it lives in three heads, the plan describes an organization that is not there. The backup named on paper has never done the work. The procedure was written once and never updated. The plan guarantees continuity on paper while the organization stays exposed.
Documentation on its own records the dependency more than it dissolves it. What changes the picture is how knowledge moves. Whether a critical skill has more than one carrier. Whether the person who holds it can transfer it. Whether the structure pushes knowledge to circulate or rewards keeping it.
Manuals in a drawer and shared folders create the impression that the risk is covered. They cover the form. The substance stays in the conversations that pass through no file, in the exceptions only one person can handle, in the relationships that no signed document hands down.
Concentrated Critical Skills Cap Growth
Dependence on a few people acts as a strategic limit before an operational one. A company resting on a few people cannot scale faster than those people can absorb. Every new market, product, or client runs through the same bottleneck. The strategy can be clear and ambitious while execution stays calibrated to the capacity of whoever holds the knowledge.
The same holds for the transitions a company knows it has to face. A generational handover, a new partner coming in, a new site opening. Each of these moves shifts or replaces people, and tests how much company knowledge remains once they leave their former role.
This is also why the problem stays invisible until it turns acute. As long as the key people are present and willing, the machine runs and concentration looks like solidity. Often the cost begins before any announcement. Someone on their way out quietly pulls back, holds fewer relationships, declines the informal requests, and the company loses them piece by piece before they actually leave. By the time the exit is formal, the alternatives are already slow and expensive.
Designing the Future Means Depending Less on Who Is Here Today
Running a company by the org chart alone is like flying a plane by the map and never the instruments. For a board, the point is operational. Every strategic move, a new market, a launch, a generational handover, runs through people. If those people are few and hard to replace, the risk to executing the strategy is higher than the numbers reveal.
Reducing this risk starts with seeing the real structure. The map of who holds what, who depends on whom, where the load-bearing nodes sit. Once that map becomes visible, concentration stops being an abstract worry and turns into a set of specific choices. Which skills need a second carrier. Which relationships need redundancy. Which knowledge has to leave a few heads and enter the way the organization works every day.
Designing the future of a company means building a structure that holds without depending on whoever happens to be there today. The question worth asking is about the structure more than the people.