I’ve been rejected three times trying to reconnect a client’s bank feed to their accounting system. Not because of anything technical. Not because of a system incompatibility or a missing integration. Because of capitalization. A username that wasn’t cased exactly right. A name that didn’t match the name on the Bank of America account precisely.
Here’s what’s maddening about it: Bank of America clearly has the rules. Every time I get rejected, they tell me exactly why. The rules exist, they’re documented somewhere, and someone knows what they are. They just don’t share them upfront. You have to fail to find out. Attempt number four is upcoming. I’ll keep you posted.
I’m sharing this because it’s a perfect illustration of something I see constantly in the businesses I work with and it showed up again this week in a conversation with a prospect that crystallized it for me.
The Three Process Problems
There are three ways processes fail in a business. All three are liabilities. One of them is a profit leak.
Problem One: The process lives in someone’s head.
This is the classic one. A key person; a bookkeeper, an office manager, a long-tenured employee, knows how things work. They’ve been doing it for years. Everything runs smoothly because they’re there. And then they leave.
Maybe it’s a great thing; a promotion, a new opportunity, a full-time role they’ve been working toward. But when they walk out the door, the knowledge walks with them. The new person comes in eager and ready to work and has no idea where to start. The owner assumed the outgoing person would “train” the incoming one but training on undocumented processes is really just hoping enough osmosis happens before the transition is complete.
This week I met with a prospect in exactly this situation. Interior design firm, great business, solid revenue. Their part-time bookkeeper who knew everything, just transitioned to a full-time role elsewhere. A new person is coming in: eager, studying accounting, ready to learn. But there’s no playbook. No documented process. No clear picture of what needs to happen, when, and who’s responsible for it. That’s a vulnerable moment for any business.
Problem Two: The process doesn’t exist at all.
This one is quieter and more expensive. The owner of that same interior design firm suspects they’re missing billings. Freight charges. Storage fees. Things that should be getting passed through to clients but aren’t consistently showing up on invoices. Nobody’s sure how it’s supposed to work because nobody ever built a process for it. It just kind of happened when it happened and got missed when it didn’t. That’s not just a documentation problem. That’s a profit leak.
When a process doesn’t exist, the result isn’t chaos; it’s inconsistency. Sometimes things get done. Sometimes they don’t. And the owner has a vague feeling that something is wrong but can’t pinpoint exactly what or how much it’s costing. Missing processes are often invisible until someone goes looking. And most businesses don’t go looking until something breaks.
Problem Three: The process exists but nobody can find it.
This is the Bank of America problem. The rules are there. Someone documented them. But they’re not accessible to the people who need them at the moment they need them so every new user has to fail their way to the answer. This happens inside businesses too. The process is in an old email chain. It’s in a spreadsheet the previous person built that nobody else knows how to navigate. It’s in a folder with a name that made sense three years ago and means nothing now. Documentation that isn’t findable and usable isn’t really documentation. It’s just organized ignorance.
Why This Matters More Than You Think
Most businesses tolerate these problems because they’re not immediately catastrophic. The process lives in someone’s head, fine, they’re still here. The billing gets missed occasionally; it’s not that much. The documentation exists somewhere; we’ll find it if we need it. The problem is that all three of these situations compound over time. The person in whose head the process lives eventually leaves. The occasional missed billing adds up to real money over a year. The documentation nobody can find doesn’t get found until something breaks at the worst possible time. And if you’re trying to get a loan, like my prospect is, a bank is going to want to see that your business has real financial controls and documented processes. “Our bookkeeper knew how it worked” is not a compelling answer.
What to Actually Do About It
The good news: none of this requires a complicated system. It requires intentionality and a little time.
Start by identifying what exists only in someone’s head. Ask yourself: if this person left tomorrow, what would we not know how to do? Those are your highest-priority documentation projects.
Then look for the profit leaks. What should be getting billed that isn’t always getting billed? What should be tracked that isn’t consistently tracked? What decisions get made inconsistently because nobody wrote down how to make them? Those are your missing processes.
Then make your documentation findable. A process document that lives in a shared drive folder nobody opens isn’t useful. Build a system, even a simple one, where the right people can find the right process at the moment they need it.
A few tools we actually use:
Vinyl – we record walkthroughs of processes out loud and let the AI build the SOP from what was said. Talking through what you do is a lot easier than sitting down to write an SOP from scratch. The output is surprisingly good with minimal editing.
Karbon – we use work items to capture recurring tasks and ad hoc follow-ups so nothing falls through the cracks. It’s the difference between a task living in someone’s head and a task living in a system.
Simple checklists – sometimes the right tool is a Google Doc checklist. Don’t overcomplicate it. A documented process that someone will actually use beats a sophisticated system that nobody touches.
The Real Cost of Doing Nothing
Undocumented processes feel like a future problem. They’re not. Every day a critical process lives only in someone’s head is a day you’re one resignation away from a crisis. Every missed billing is money that’s already gone. Every process that exists somewhere but nobody can find is a failure waiting to happen at the worst possible moment. The businesses that run well, the ones that can survive a staff transition, pass a lender’s due diligence, and scale without chaos, are the ones where the knowledge lives in the system, not just in the people. It’s worth investing the time to build that. Before you need it.
Chris Geno is a CPA and fractional controller at High Rock Accounting, working with professional services firms on financial strategy, process documentation, and internal controls. If your business has processes that live in someone’s head or processes that should exist but don’t, it’s worth a conversation.