I’ll never forget the sound that binder made when it hit the conference room table. It was a heavy, dull thud followed by a tiny puff of grey dust that danced in the afternoon sunlight.
I was sitting in a cramped office with a non-profit Executive Director who was, quite frankly, at her wit’s end. She had pointed at this three-inch-thick white binder, the "Operations Bible", and said, "Brett, we spent twelve thousand dollars on a consultant to write this two years ago. I’m pretty sure the only person who has opened it since then was the spider I just saw crawling out of the spine."
Yikes.
If I’m honest... I’ve been that guy. Early in my career, I thought "Standard Operating Procedures" (SOPs) were the holy grail. I thought if I could just document every single click, every phone script, and every possible edge case into a beautiful PDF, the business would magically run itself. I’d spend weeks in a silo, typing away, feeling very productive... and then I’d hand it over, only to realize six months later that nobody was using it.
It’s a painful realization. But it’s one I see almost every time I walk into a new organization with Solved. Operations & Management Solutions.
The reality is that process manuals usually collect dust because they are built for compliance, not for people. They are written in a vacuum, far away from the "trenches" where the actual work happens. And when your SOPs don't match the reality of a Tuesday morning at 9:00 AM, your team will choose reality every single time.
The Great Disconnect (And Why It’s Costing You)
There is a massive gap between how we think work happens and how it actually happens. When that gap exists, your team stops looking at the manual. They rely on "tribal knowledge", which is just a fancy way of saying they ask the person sitting next to them, "Hey, how do we do this again?"
If that person is gone? The work stops. Or worse, it gets done wrong.
Research actually shows that this isn't just a minor annoyance... it’s a financial drain. A landmark study found that non-compliance due to outdated or impractical procedures can cost organizations nearly three times more than maintaining updated ones: think $14.82 million versus $5.47 million for larger firms. Even for a smaller shop, those ratios hold true. The lost productivity, the constant re-work, and the frustration that leads to turnover... it adds up fast.
Static documentation dies the second it’s printed. If your SOPs aren't "living" where the work happens: accessible, visual, and actually helpful: they aren't processes. They’re just expensive paperweights.
Caption: A visual representation of the gap between a rigid process manual and the dynamic, messy reality of daily operations.
Why We Get Into the Trenches
At Solved., we do things a little differently. I don't believe in sitting in a leather chair and "dictating" how your team should work. To be honest, I can’t tell you how to fix your workflow until I’ve stood in the kitchen, sat in the backseat, or watched your team handle a crisis.
We take an "in-the-trenches" approach. This means working alongside your staff to see where the friction is. Are they skipping Step 4 because it’s unnecessary? Or because the software changed six months ago and the manual was never updated?
When we help a client build out their operations, we use a framework I call Reduce → Route → Resolve. It’s a simple triage for everything that crosses your desk:
- Reduce: We look at the process and ask, "Does this even need to happen?" Half of the stuff in those dusty manuals is "busy work" that doesn't move the needle. We remove the clutter first.
- Route: If it needs to happen, who is the natural owner? We delegate it with the right context. Process manuals often fail because they try to make everyone do everything.
- Resolve: I only want you (the leader) handling the work that requires your specific judgment. Everything else should be handled by a system or a team member who has been empowered to act.
If you want to dive deeper into how this impacts your daily flow, check out our recent post on improving project management and follow-through.
The "Executive Director Independence" Test
One of the biggest reasons I’m obsessed with functional processes isn't just for efficiency... it’s for freedom.
I often evaluate an Executive Director or an owner based on one simple metric: How independent is the organization from you?
If you go on vacation for two weeks and the office burns down (metaphorically or literally), your SOPs have failed. If you are the only one who knows the password to the vendor portal or the "secret way" we talk to our biggest donor, you aren't a leader; you’re a bottleneck.
When we work together, we look for these independence indicators:
- Decentralized Decision Making: Are decisions being made at the appropriate levels, or does everything need your "blessing"?
- Distributed Relationships: Does the whole team know the key vendors and partners, or are those relationships concentrated solely in your head?
- Accessible Priorities: Is the "main thing" documented where everyone can see it?
- Absence Testing: Can the work continue smoothly while you’re gone?
- Succession Planning: Are we training the next version of you today?
True operational excellence means the business should hum along just fine without you. If it doesn't, we haven't solved the problem yet.
Moving from Binders to Behavior
So, how do we stop the dust from settling?
First, we have to acknowledge that process is about behavior, not just documentation. We’ve found that integrating things like the DiSC assessment into your processes makes a world of difference. Why? Because a "C" personality (high conscientiousness) might love a 20-page manual, but an "i" personality (high influence) needs a checklist or a quick video. If your SOPs don't account for how your team actually communicates, they will be ignored.
Caption: A team collaborating in a workshop setting, mapping out a workflow on a whiteboard rather than reading from a manual.
Second, we need to make the documentation "wet cement." It has to be easy to change. The moment a team member finds a better way to do something, the process should be updated. It’s not a sacred text; it’s a tool.
A Quick Confession...
Even as someone who has been around the block, I still struggle with this. Sometimes I find myself doing a task for the 50th time and I realize I never actually wrote down how to do it. I’m just "winging it." And every time I do that, I’m creating a "dusty binder" moment for the future.
It’s a constant discipline. It’s about being humble enough to realize that your "perfect" way of doing things might not be the most practical way for your team.
If you’re feeling overwhelmed by the "Bible" sitting on your shelf: or the lack of one: don't feel like you have to fix it all by Monday. Start small. Pick one thing that you’re tired of explaining and write down three bullets on how to do it.
Or, if you’re ready to actually clear the air and build something that sticks, let's talk. We love getting into the weeds (and the dust) so you don't have to.
I’d love to hear... what’s the most "useless" rule in your current manual? The one everyone knows to ignore? Drop me a line and let’s laugh about it (and then maybe fix it).
Brett Bortnem is the Owner & Principal Consultant at Solved. Operations & Management Solutions. He specializes in helping organizations move from chaos to clarity by working alongside teams to build practical, human-centered systems.
