Process Maturity: Is Your Business Running on Systems or “Steve”?

Take a moment and recall the last time a key employee left your business. Maybe you didn’t even realize they fell into the “key” category until they left.

Did you learn (the hard way) that they were the only person who knew how to run that critical report? Or handle that odd customer situation? Or operate that temperamental piece of equipment?

Did you receive customer complaints regarding “the way things used to be done” – arrangements nobody else knew existed, or vaguely recalled, but each recollection was dramatically different from the others?

Did you watch your remaining team spend days digging through desk drawers and email folders, trying to play Dr. Frankenstein and piece together a process implemented by that person?

Did you ever have to tell a customer: “I don’t know, the person who handled that is no longer here”?

If any of these are hitting home, you’ve experienced what businesses call “knowledge loss” or “key person risk”. Those terms, unfortunately, are far too polite – sterilized for articles like the one you’re reading now to look objectively at a problem. That gut-wrenching feeling of panic, however brief? That is what you should recall distinctly. That moment when you discovered your business was more fragile than you thought – held together by one person’s memory, workarounds, and “hacks” that walked out the door with them. Let’s call them “Steve”.

This is a two-fold problem, because those employees don’t just leave gaps when they quit. They hide how broken your processes are while they’re still there. And this is not some sinister plot to hurt you, the team, or the business. This is human beings being human beings – solving problems they’ve solved a hundred times before, but never quite found the time to put down on paper. At that time, in solving THAT problem, they were not thinking about solving THIS problem – preventing leaving their team in a lurch when they depart.

I once worked with a company that had a 30+ year general manager everyone relied on. He knew it all. He handled things people didn’t even know needed handled. When he departed suddenly, the scrambling began. Weeks were spent digging through handwritten notes (some going back decades), old emails, and mountains of files, trying to fill in those gaps.

The real lesson of that ordeal was not what we couldn’t find – it was what we found. The GM had been making undocumented side arrangements with one of the company’s largest clients for years. Not shady deals involving gifts, cash, or anything self-serving in the least. These side arrangements were the well-intentioned efforts of a person who genuinely cared about making, and keeping, his customer happy and satisfied with their service. If the client’s budget ran short or they failed to place a timely order for supplies they’d need to utilize our company’s services, he’d personally loan them company owned materials – free of charge, no documentation, no tracking to ensure those assets made it back to the company. When it stopped after his departure, the client was furious.

“You want us to pay for this? We’ve never had to pay for this! You don’t care about us like he did. Maybe we’ll go elsewhere.”

Compounded, the company had no idea how much of these materials had walked out the door and never returned over the many years.

This example should serve to illustrate that the company didn’t just lose a GM in this ordeal. We discovered that our operation had been running on one person’s undocumented judgment calls, masking fundamental process problems that nobody could see until he was gone.

Sometimes knowledge loss isn’t so obvious, or so dramatic. Sometimes it’s being bled by a thousand small inefficiencies that nobody notices until they add up.

Consider this example, another one based on true events. A piece of equipment needs regular maintenance with a specific amount of lubricant that starts in powdered form and in a bulk container. The longtime technician tells the team “use the Gatorade bottle” to measure it. Simple enough right? Everyone follows the instruction given, no issues.

Somewhere along the way, years later and after some turnover, the original 12-ounce bottle gets lost. Someone else, being helpful, replaces it with a 32-ounce bottle they find in the break room. The maintenance team does exactly what they’ve been trained to do – they use “the Gatorade bottle”. Nobody told them the volume mattered. Nobody documented “Apply 12 ounces every 500 operating hours.”

Now the machine is burning through triple the lubricant cost. It’s oozing lubricant which causes other problems downstream. And this is not because the team is incompetent – they’re following the instructions they were given perfectly. But the process lived in someone’s head instead of being documented and readily available.

Before you think “MY team would never make such an obvious mistake” – yes, they would. And they are. Whether you are prepared to admit it or not, every business has these moments and the question that matters is whether or not you know where yours are hiding.

Think about your own “Gatorade bottle” moments:

• The machine setting that “just needs to be at 7”
• The tool where you “always use the blue-handled one”
• The report you “just run on the 15th”
• The customer exception you “handle the usual way”

Nobody knows WHY, they just know WHAT. When the day comes that the person who knew why inevitably leaves, suddenly you’re solving the same problem poorly, over and over, because the knowledge left with them.

When experienced employees leave, you lose more than you think:

Explicit knowledge is the easy stuff to identify – the procedures, the reports, the customer lists. This is documented somewhere, even if it’s hard to find.

Implicit knowledge is the killer – the workarounds, the judgment calls, the “here’s how we actually do it” versus “here’s what the manual states.” The understanding of WHY certain processes exist, WHICH customers need special handling, what that weird noise from the equipment MEANS, HOW to handle the situation when two procedures conflict.

When someone leaves, a huge portion of what made them effective – their judgment, their relationships, their understanding of context – leaves with them. Their replacement has to relearn it from scratch, making expensive mistakes along the way.

The full cost isn’t just recruitment and training. It’s:

• Mistakes made due to missing knowledge
• Time wasted recreating information that already existed
• Customer relationships damaged by inconsistent service
• Equipment damage from improper operation
• Materials wasted from incorrect processes
• Decisions made without full context

Most companies don’t separately measure knowledge loss from general turnover costs, which is what generally leads to the problem persisting and going unnoticed.

You know you need documentation and you’ve probably tried creating it. You’ve probably watched it fail – manuals nobody reads, procedures nobody follows, documents nobody can find when they eventually need them.

I’m going to share five documentation mistakes that waste everyone’s time:

Your official procedure says “Submit requisition form X to Accounting.”

Clean and pretty.

“Steve” says “Email Sarah, CC Mike, and if it’s over $5K, walk it to Sarah’s desk because the system flags it and she needs to pre-approve before it hits the queue.”

Document reality, not fantasy.

“Set temperature to 350 degrees” tells someone what to do. It doesn’t tell them why 350, what happens at 340 or 360, or how to adjust if conditions change.

Document the judgment, not just the action.

A 47-page standard operating procedure for a 15-minute task guarantees nobody will ever read it. They’ll ask someone instead, who undoubtedly asked someone else, which defeats the entire purpose.

 Document what truly matters, not everything possible.

“It’s in the shared drive somewhere” means it doesn’t exist. If people can’t find it in 30 seconds, they won’t look. Documentation needs to live where the work happens, not buried in folder structures that made sense to whoever created them years ago. If the work happens in a fully digital space, a knowledgebase or directory PDF with clickable links is critical.

The process changed six months ago but the documentation still shows the old way. Nobody trusts any documentation anymore, because they have no idea if it’s current. Documentation requires maintenance or it becomes worse than useless – it becomes misleading.

Good documentation isn’t about creating binders that sit on shelves. It’s about capturing knowledge in a way people use when they need it.

But documentation is just one dimension of true process maturity. Even perfect documentation won’t save you if only one person understands the process, if there’s no training system, if errors go untracked, or if the process breaks under volume.

If your processes depend on specific people knowing things in their heads, they’re not processes – they’re just “how Steve does it” documented as official procedure.

After working through thousands of operational processes across multiple industries, I’ve identified 12 critical dimensions that determine whether a process can survive someone’s departure:

1. Documentation – Is it written down? Current? Accessible? Does it include decision criteria and visual aids where appropriate?

2. Ownership & Accountability – Who owns this process? Do they have authority to change it? Is there a backup person designated?

3. Training & Knowledge – Is there formal training? Can multiple people perform the process? Is institutional knowledge (the WHY) captured?

4. Error Handling & Quality – How do you detect errors? What happens when things go wrong? Are errors tracked and analyzed?

5. Metrics & Performance – What gets measured? Is performance visible to the team? Are metrics used to drive decisions?

6. Capacity & Scalability – What’s your maximum capacity with this process as defined? Where are the bottlenecks? Can the process handle volume increase without becoming a new process?

7. Dependencies & Integration – What happens upstream and downstream? What breaks if dependencies fail?

8. Standardization & Consistency – Is it done the same way every time? How are exceptions handled?

9. Technology & Tools – Are the right tools available? Are they integrated? What happens if they fail?

10. Compliance & Risk – What are the regulatory requirements? Are risks identified and mitigated?

11. Customer Impact – How does this affect customers? Are service levels defined? Is feedback captured?

12. Continuous Improvement – Is there regular review? Are improvements captured and implemented?

Many businesses may score well on 2-3 of these dimensions and assume they’re fine. They’re not. A process that’s well-documented but has no error handling will fail differently than one with good metrics but no training. But let me be clear – both will fail.

Asking dozens of questions across 12 dimensions for every process in your operation feels overwhelming. It is overwhelming. Which is exactly why most businesses never do it.

Ideally, every process musters and can be defined as fully mature. But I am writing about reality, not fantasy, so here is my advice on how to prioritize: run each process through a much smaller filter that evaluates it on three factors.

What happens if this process stops working? Revenue stops? Customers leave? Safety incidents? Regulatory violations?

Rank them: High impact (business-critical), Medium impact (painful but survivable), Low impact (inconvenient).

How many people can run this process competently? If the answer is one, or “one person plus someone who kind of knows it,” that’s high risk. If it’s “anyone on the team can do it,” that’s low risk.

Is the key person involved with this process approaching retirement? Actively job hunting? Unhappy? Been in the same role for 20+ years and likely to coast to retirement?

This isn’t about being paranoid or de-valuing your people – it’s about being realistic.

• Address first: High impact + High knowledge risk + High departure likelihood
• Address second: High impact + High knowledge risk + Low departure likelihood
• Address third: High impact + Low knowledge risk (any departure likelihood)
• Address eventually: Everything else

You don’t need to fully assess every process tomorrow. Start with the three that would hurt most if someone left, or if your team absolutely butchered the execution. Build from there.

A mature process isn’t perfect. It’s resilient. When someone quits, the process continues without heroics or dramatic scrambling because the knowledge is built into the system, not trapped in someone’s head.

Here’s what that looks like in practice across three critical dimensions:

Immature: “Just follow Steve around for a few days and watch what he does. Ask questions if you’re confused.”

Mature: New employees complete structured training with documented curriculum. They’re certified competent before working independently. Multiple people can perform the process. Knowledge is captured in accessible formats – written procedures, video demonstrations, decision trees. When Steve leaves, the process continues because five other people can run it competently with virtually identical outcomes.

Immature: Errors get caught when customers complain or when someone notices something looks wrong. When mistakes happen, people scramble to fix them and hope it doesn’t happen again.

Mature: Quality checks are built into the process at critical points – not just inspection at the end. Errors are detected immediately, not three steps downstream. There’s a documented procedure for handling errors when they occur. Errors are tracked, analyzed for patterns, and root causes are addressed systematically. The process improves because failures drive changes, not just firefighting.

Immature: “How are we doing?” gets answered with “Pretty good, I think” or “Ask Steve, he’d know.” Performance data exists somewhere but nobody looks at it regularly. Problems get noticed when they’re already serious.

Mature: Performance metrics are defined, measured consistently, and visible to the team doing the work. Everyone knows the targets. Performance is reviewed weekly or monthly, never less than quarterly. Declining trends get caught early. Metrics drive decisions about where to improve, not just measure what already happened.

What I’m describing is not bureaucracy, it’s operational maturity. It’s the difference between “the business runs” and “the business runs only when the right people are here.”

Many companies can’t measure knowledge loss systematically because they don’t have a reliable way to assess it. They know it hurts when someone leaves, but they can’t quantify how dependent they are on individual knowledge versus documented systems.

Because of this, I’ve developed a comprehensive process maturity assessment tool. It evaluates any business process across all 12 dimensions with 75 specific yes/no questions, generating a maturity score that shows exactly where you’re vulnerable.

The tool helps you answer questions like:

• Which processes would completely stop if one person left tomorrow?
• Where are we dependent on individuals versus systems?
• What’s our biggest risk of knowledge loss in the next 12 months?
• Which processes should we document first for maximum impact?

The assessment will not fix your processes – but it makes the invisible risks visible so you know where to focus your effort.

If this article has struck a nerve and you know that this is a problem you’re facing, you have two real choices:

Option 1: Do nothing. Cross your fingers and hope that your key people don’t leave, retire, or get hit by a bus. Hope that the next time someone quits, the damage is manageable. Keep operating on institutional knowledge and personal heroics. It may have worked for your company thousands of times over the last hundred years, but remember that it only has to stop working once.

Option 2: Assess systematically. Use a structured framework to evaluate where you’re truly vulnerable, prioritize based on risk and impact, and build a roadmap for moving from hero-dependent to system-dependent.

The companies that survive leadership transitions, market changes, and growth aren’t the ones with one, or even a handful of “Steves” who can do it all. They’re companies whose operations run on mature, well-established systems and processes that result in developing many competent employees who can execute reliably.

Which category do you want to be in?

---

Want to evaluate your vulnerability objectively?

The Process Maturity Assessment tool is available free at thinkbuildgrow.net/resources. This is a comprehensive audit; expect 45-60 minutes per process to answer all 75 questions thoughtfully. No registration required, no email capture – just download and use it.

Staring at 75 questions across multiple processes and thinking “I don’t have time for this”?

Fair. Most business owners don’t. That’s exactly why businesses stay vulnerable – the work of building systematic processes gets perpetually back-burnered behind today’s fires. If you need this done but can’t afford to let it sit on your “someday list”, let’s talk about how to make it happen without consuming all your bandwidth. Contact me to schedule a free discovery call by providing some basic information on a secure form.

---

Thomas Geller is the Principal of TBG Advisory, specializing in operational and financial transformation for small and mid-sized companies. He’s spent over 15 years as COO and CFO watching businesses discover exactly how fragile their operations were when key employees walked out the door – and helping others build systems that survive turnover. His approach: Think Strategically. Build Deliberately. Grow Sustainably.