By Marie Greene, CPA
This is the second in a seven-part series exploring the everyday habits that can quietly become costly as a business grows, along with the practical steps leaders can take to address them.
Quick takeaway: If your business only runs smoothly because one person knows the history, the workaround, the file location, or the next step, that is not efficiency. It is hidden dependency.
Start by identifying the one task your team would struggle to complete if that person were unavailable. Then capture enough of the process so someone else can step in.
In Habit 1, we looked at how scalable businesses notice operational friction early, ask what it is costing them, and improve the process before the business is forced to. Habit 2 is about one specific kind of friction that is easy to miss: when critical knowledge lives with one person instead of inside the business.
Every growing company has someone the CEO or founder depends on a little too much.
You may see it in small moments: the only person who knows why a customer has special billing terms, the employee who remembers the exception in the payroll process, or the manager who knows where the renewal checklist lives.
It may also be the team member everyone calls because they know which report version is the final one.
At first, that’s a good thing. It usually means you’ve built a team of experienced employees who know your business well and take pride in their work.
The challenge comes when too much knowledge lives with one person.
At that point, the business becomes dependent on individuals instead of systems.
That dependency often goes unnoticed until the business starts growing—or until the one person everyone depends on is not available.
Experience Is an Asset—Dependency Is a Risk
Experienced employees are one of a company’s greatest strengths. They understand your customers, your operations, and the countless details that keep everything moving each day.
For a CEO or founder, the risk is not that these employees are valuable. The risk is that the business has become too dependent on knowledge only they hold.
When only one person knows how to perform a critical task, prepare an important report, or resolve a recurring issue, you have created a single point of failure.
A simple test: if that person were unavailable tomorrow, would the work continue, slow down, or stop completely?
For example, vendor payments may seem simple until the one person who knows the exceptions is out.
They know which vendors require backup, which invoices need special approval, which recurring charges are legitimate, and which questions usually come up before payment.
Without that context, invoices do not move slowly because the team is careless. They move slowly because the process was living in one person’s head.
The same thing happens with customers.
A client asks why their bill is handled differently, but only one employee remembers the original agreement. A renewal is due, but the person who knows the history is on vacation. A customer exception was approved two years ago, but no one documented why.
The issue is not customer service. The issue is that the context needed to serve the customer lives with one person.
That knowledge may be accurate and valuable—but if it is not shared, the business is relying on memory instead of a system.
Growth Exposes the Gaps
Like many operational challenges, this one becomes more noticeable as a business grows.
When a company is small, everyone naturally wears multiple hats. The owner can answer most questions, and experienced employees fill in the gaps wherever they’re needed. As the business grows, however, that approach becomes harder to sustain.
For CEOs and founders, that creates a visibility problem.
The company may look like it is scaling, while important decisions and daily execution still depend on a few informal workarounds.
Without documented processes or shared knowledge, questions keep flowing to the same people until those people become bottlenecks.
The business hasn’t outgrown its employees.
It’s outgrown the way information is managed.
As organizations grow, informal ways of sharing knowledge become harder to sustain. New employees need structure, managers need consistency, and owners need confidence that critical work can continue without depending on one person. That’s where documented processes and shared knowledge become an advantage—not because they create bureaucracy, but because they create stability.
The Cost Is More Than Lost Productivity
The cost usually does not appear all at once.
It shows up in the small pauses that happen throughout the week: a billing exception waiting for the one person who knows the customer history, a payment sitting because no one else knows what backup is required, or a new employee unable to finish setup because the steps were never written down.
Individually, each delay may seem manageable.
Together, they slow the business down. Projects wait for answers. New team members take longer to get up to speed. Managers spend more time fielding routine questions instead of coaching their teams. Customers can feel it too when a request sits because only one person knows how to handle it.
Eventually, the hidden dependency becomes visible. The person with the knowledge feels constantly interrupted. Everyone else feels stuck. And the CEO or founder gets pulled back into decisions the business should be able to handle without them.
No one designs the business this way on purpose.
It usually happens gradually as the company grows, the work gets more complex, and the same reliable people keep stepping in to solve the same recurring problems.
Building Systems Doesn’t Mean Creating Bureaucracy
When CEOs and founders hear the words process documentation, they sometimes picture thick binders full of procedures that no one ever reads—or a level of bureaucracy that feels at odds with a fast-growing company.
The goal is not to create a binder no one reads. The goal is to make sure important work can continue even when the person who usually handles it is unavailable.
Sometimes that means documenting month-end close procedures or creating a checklist for payroll. Other times it means cross-training employees so responsibilities are shared instead of concentrated. Small changes like these reduce disruption, improve consistency, and make onboarding new employees much easier.
Documentation doesn’t have to be complicated.
Start simple: write down the five steps to complete a recurring task, save the checklist where the team can find it, or record a short screen share while the work is being done.
My favorite tool is a simple checklist paired with short, one- to three-minute videos for each step. The checklist gives the team a clear path to follow, and the videos show the small details that are often hard to capture in writing.
The goal is not to document everything at once. It is to capture the knowledge that would create the most disruption if it disappeared.
Cross-training is equally important. When two or three people understand an important process, the business becomes more resilient. Employees feel more confident stepping in when needed, and managers have greater confidence that work will continue without interruption.
Sharing knowledge also benefits the employee who has been carrying the workload. Instead of being interrupted throughout the day with the same questions, they can focus on higher-value work, mentor others, and contribute more strategically. Building systems is not about replacing expertise—it is about making better use of it.
Start Where It Matters Most
The idea of documenting processes or cross-training employees can feel overwhelming, especially if your business has grown quickly.
Start with the work that would create the greatest disruption if one employee suddenly could not do it. For many companies, that means payroll, billing, cash receipts, month-end close, customer onboarding, vendor payments, or reporting packages that leadership relies on to make decisions.
Quick self-check: Think of the person your team asks for the same answer again and again.
Are they making a judgment call, or are they simply the only one who knows the steps, history, file location, password process, approval rule, or workaround?
If it is the second, that knowledge needs to move out of their head and into the business.
- Which tasks can only one person complete?
- What information exists only in someone’s head?
- Where do employees consistently wait for answers from the same person?
- If a key employee took two weeks off, what work would stop?
Those questions often reveal where your biggest opportunities are. Small improvements made today—whether it’s documenting a process, cross-training another employee, or creating a simple checklist—can prevent much larger disruptions later.
Strong Businesses Build Strong Systems
The goal isn’t to make people replaceable.
It’s to make the business more resilient.
When knowledge is shared instead of concentrated, experienced employees spend less time answering routine questions and more time using their expertise to move the business forward. CEOs and founders gain confidence that the business can continue operating smoothly as it grows, responsibilities shift, or key employees are away.
That’s what resilient, scalable businesses have in common. They don’t rely on one indispensable employee—they build systems that allow great people to do their best work.
So ask yourself: What important work still depends on one person knowing what to do next?
