The Strongest Operations I Have Seen Assumed Something Would Break
Seventy-one percent of small businesses depend on one or two key individuals for their success, according to a survey by the National Association of Insurance Commissioners. It is easy to read that as a succession question, something to address later. It is a design question, and it is being answered every day, by default.
Behind that figure are familiar arrangements: one person who holds the key supplier relationships, another who alone knows how the month-end close works. Those arrangements hold until the day that person is unavailable.
I spent more than a decade running the operations of international programs, with their budgets, offices, staff, and audits, in the Democratic Republic of Congo, Mali, Niger, Nigeria, and Afghanistan. Roads close for the rainy season. Networks drop for days. A key staff member may not be able to reach the office, or may leave for a better offer in the capital. In those conditions, an operation without planning spends its days putting out fires. The lesson I took from those years is simple: resilience is built through planning and systems, long before anything breaks.
How key-person dependency builds up
It rarely starts as a problem. When a business is growing and disruption is rare, working around a gap is faster and cheaper than designing it out. Each workaround makes sense at the time: the founder approves every expense because it takes a minute, the office manager keeps the vendor list in a personal inbox because it has always worked. Over time, those workarounds add up to a structure that depends on everything staying the same, and as long as things stay stable, nothing reveals it.
How to build a resilient operation
The operations that held up under pressure shared five design principles. Each one removes a dependency on a single person or a single step, and together they travel well from Kinshasa to the Research Triangle.
Map the process, then remove the bottlenecks. Many operations have never been mapped, so start by following how the work actually moves: who does what, in what order, and where it waits. Once the process is on paper, the bottlenecks are usually easy to see, and they are often people: the one manager every approval passes through, the one person who knows how a step is done. Remove them by redesigning the flow. Delegate the decisions the people doing the work can make, and set clear limits for the ones they cannot, so that no one signs a large contract or commits a major expense without anyone else knowing. A process that no longer waits on one person is both more efficient and more resilient.
Build a system that gives full visibility. When status, spending, and commitments are visible to the people who need them, the organization can plan instead of react. Full visibility shows what is coming this quarter and which activities need the longest lead time. Procuring goods and services, recruiting the right talent, securing a venue: many activities take weeks or months to prepare, and none of them can start the week they are needed. I build them into monthly and quarterly plans, together with the approvals they require. Visibility also brings problems to the surface while they are still small, before they stop the work.
Write procedures, and train people on them. Without written procedures, each person decides how things are done, and no one can tell when a decision crosses a line. For an educational institution, I developed a procurement manual that set out the procedures, roles, and responsibilities for purchasing. The approach applies anywhere: identify the main risks, such as conflicts of interest in contracting, and write those procedures first. Then train your staff on them, because a procedure no one knows protects no one. Procedures followed every day also make audits uneventful: across four portfolios, the systems I built went through audits without a single issue, including an audit by a US federal inspector general. The test is simple: could someone competent do this job next month from the procedures and records on file?
Rotate and backstop every critical role. Every task that stops the work or moves money needs a trained backstop, someone who can run payroll, approve payments, or access key systems when the usual person cannot. Rotating these duties periodically does two things. It keeps the backstop's skills current, and it is a standard control against fraud, because irregularities are hard to hide when someone else regularly does the job.
Build for the organization you intend to be in five to ten years. What works at one level of volume rarely survives the next. On one operation, annual spending grew fivefold while the structure stayed the same. The fix was a new layer of program managers and workstream sponsors, each with a counterpart at headquarters. A system that fits today is already behind if the organization plans to grow.
What a strong platform frees you to do
The operations that delivered and outperformed had one thing in common: a strong operating platform. It is what allowed leadership and their teams to focus on their respective work. Leadership could concentrate on the vision, the results, and the quality of implementation. Teams could concentrate on delivering. Without that platform, everyone's time went to the next emergency.
The question to ask first
Sooner or later, every organization faces a resignation, an illness, or a key person on a two-week vacation during its busiest month.
So ask a simple question: if your most indispensable person were unreachable for thirty days, what would stop? The answer is your operating system's real design, whether or not anyone chose it. Resilience is not what you do when something breaks. It is how you run when nothing has.
VLC Advisory helps growing organizations build operations that hold when people, markets, and plans change. A diagnostic starts with that thirty-day question, and I would welcome the conversation.
Source: NAIC survey (https://www.nationwide.com/business/solutions-center/risk-management/key-person-risks)