Every week I come across questions from business owners that reveal the same underlying problems showing up in different forms. This week I want to work through five of them, as they are a in some ways variations on a theme.
Why does everything fall apart when I take a day off?
There are two sides to this. First, ask yourself: is everything actually falling apart, or are things just being done differently to how you'd do them? If the outcomes are fine but the method isn't exactly yours, that's a you problem, not a business problem. Either you create the systems and processes to ensure things are done your way, or you accept that there is more than one way to get the desired results.
If things genuinely aren't getting done, then the reality is that it is largely on you as the owner. Not as a criticism, but as a practical observation, and you need to take responsibility. If your team has no systems, no processes, and no automation to rely on, then of course they rely on you. You're the system. The moment you're not there, the system goes offline.
The fix isn't complicated, even if it takes effort. Start by mapping out the basic outline of what needs to happen in the business each day. Then use automation to generate the tasks for whoever needs to execute them. Whether your team works from desks or out in the field, technology exists to handle this. And if your business isn't at that stage yet, then at minimum, before you take a day off, sit down the afternoon before and write out what needs to happen the next day. Pre-empt the questions. Give people the answers before they ask them. It's not elegant, but it works while you build something more durable.
The goal, though, is a business where your team relies on what you've built, not on you being present.
Is it naive to think I could step back from the day-to-day?
Yes, if you haven't done the underlying work. No, if you have.
What I see often is business owners convinced that hiring one good person, often a general manager or operations lead, will be the thing that transforms everything. But that person walks into a business with no structure, no processes, and no automation, and they end up in exactly the same position you were in, except they don't have the ownership mindset to push through it. The business still relies on you, just indirectly.
For the business owners I know who have genuinely stepped back and installed a manager to run things, that hiring decision was the last thing they did, not the first. By that point they already had a trained team, documented processes, and automation handling the repeatable work. The manager came in to manage a functioning business, not to firefight a chaotic one.
Stepping back is completely realistic. But it does require you to build the business in a way that it can be run by someone else.
How do I document a process so someone can follow it without asking me?
Business owners consistently overestimate how unique and complex their businesses are. Most processes can be documented clearly enough for someone else to follow, if you're willing to actually sit down and do it.
Think about two ends of the scale. At one extreme, aircraft maintenance engineers follow a checklist for every single task, regardless of how experienced they are. Nothing gets done without marking it off. At the other extreme, something as simple as signing children into a camp, confirming a waiver was signed and telling parents when pickup is, is also a process. Small, but important. Easy to follow. Easy to see when it hasn't been followed.
The resolution you document at depends on what you need. A kitchen design and installation company I worked with ended up with a physical folder for each job containing nine sheets, one for each stage from initial enquiry through to completed installation. Each sheet had a checklist and space for notes. Anyone could open a folder and immediately see where a job stood, what had been done, and what hadn't. No software. No training in new tools. Completely analogue, and it worked.
Start with the big stages. Get clear on what defines the move from one stage to the next. Then add the sub-steps within each stage. Some steps will be mandatory every time, others will be conditional. Once you've got the structure mapped out, you can decide how much of it to put into software and how much to leave as it is.
One important principle: design your processes away from any tool. If you design inside the software, the system you end up with is shaped by what the software can do, not by what your business actually needs.
How do I know if I'm ready for automation, or if my processes need fixing first?
The question assumes these are sequential. They're not. They work together iteratively, and each one improves the other.
You don't need perfect processes before you automate. In fact, trying to perfect your processes before adding automation is one of the more reliable ways to never actually automate anything. The moment you do add automation, you'll find gaps in the process you didn't see before, because the automation makes them visible.
Take a simple example. Once you define that a job moves from stage one to stage two, you can automate a task for someone to send a confirmation email to the client. You don't have to make the email go out automatically at first. You can have a human review it. Once you're confident the process is working and the email is right, you remove the manual step and let it run. That's the iterative approach, and it's far more effective than spending six months designing the perfect system before anyone uses it.
Think about how good software gets built: not in a two-year big-bang project that's out of date before it launches, but in six-week cycles, getting something usable in front of people quickly and improving it based on what you learn. Your systems and processes work the same way. Start, learn, improve.
What makes this different from working with a traditional business coach?
Honestly, I don't see what I do as business coaching. It's more technically hands-on than that. The work involves identifying what processes and systems a business actually needs, designing them together, and then getting involved in implementing them, not just generating ideas and leaving the owner to figure out how to make them real.
The result, done this way, is that over the course of a year a business looks fundamentally different from what the owner imagined it would be when they started, because it's grown organically through doing rather than planning. That, in my experience, is how lasting change actually happens in owner-managed businesses.
If any of this resonates, a good place to start is understanding where value is leaking from your business right now. Take the free Value Leak Assessment at blindspotworks.com/value-leak-assessment.