For the second time in four years, I took a two-week vacation.
I didn't take my computer or buy an international data plan. I checked my email but there was nothing urgent and I didn't reply to anyone until I returned.
It still kinda blows my mind that I was gone that long and actually let work go. Nothing fell apart while I was gone and I didn't come back to an out of control calendar trying to make up for lost time.
The idea of you doing the same either excites or terrifies you.
It either seems within reach or unimaginable that you might not call in for a meeting while driving to the lake house for a four-day weekend or get an "I hate to bother you" email from an employee who should know how to make the decision they're asking you to make.
Either way, your ability to step away from your business for a few days or a few weeks reflects how you've intentionally or unintentionally built your business.
Don't get me wrong, we all start out at the center of our businesses. Early on, being reachable and capable of solving problems is exactly what let the business grow. Being essential and indispensable was a feature not a flaw in the design.
But as your business has grown there have been opportunities to change the design. These inflection points may have been subtle, making it hard for you to realize that you were making a choice to maintain the status quo. Or maybe you knew the moment was right to add someone or delegate more responsibilities but it felt better to keep going full steam ahead and do the transition and expansion work later.
Now you're starting to resent that people still come to you for everything. No one seems to be thinking for themselves or taking initiative. You're still stuck writing proposals, catching mistakes, and answering questions when there's a policy and procedure handbook everyone can reference.
Now having you at the center of everything is a design constraint that will keep your business from growing while eroding the personal freedom and professional satisfaction you want from your business at this stage.
Like delayed pricing changes and personnel decisions, the failure to intentionally delegate and relinquish control over key functional areas of the business doesn't start out looking like a bad decision. The costs might not seem too significant at the beginning. But when deferred, decisions like these end up costing you more than R&R.
You've built your business around you, and as it grows, it will only become more owner dependent without intentional changes to organizational structure, documentation and training, hiring and delegating, and how you personally relate to the business.
Just adding more people won't solve the design problem on its own. Your behavior has to change too. Like a deferred pricing decision or an unresolved people decision, this one compounds too. Every time you step in to catch a mistake, answer the question yourself, or take the call because you're not sure your team member will get it right, you reinforce the same design a little more.
Your team learns you'll show up before they have to figure it out. You learn that stepping in is faster than teaching. Both of you keep making the choice that makes sense in the moment, and the business quietly doubles down on needing you exactly as much as it does today, for another year or more.
Ultimately, it shows up in a lower valuation, because a lender or prospective buyer factoring in the risk of having you at the center of everything will err on the side of caution when estimating how fragile your recurring revenue and net income projections really are. Every relationship that you hold exclusively, the decisions only you can make, and every piece of institutional knowledge that lives only in your head, is something they have to discount for.
None of that resolves with time. It only gets more entrenched, because the same daily choices that feel efficient today are the ones building the design you'll be stuck with tomorrow. The design doesn't change until you decide, on purpose, to change it. You didn't start this business to be the only person who knows how it runs.
Delegation is not abdication. Whether you're adding someone to the senior management team, promoting a team member with leadership potential, or more fully utilizing the operational and administrative support you already have, delegation often means:
Before you decide what to hand off next, take stock of what you're already carrying.
Ask yourself:
However you answer those questions, treat them as information, not an indictment of your leadership. The goal isn't to prove to yourself that you should have redesigned your business sooner. It's to see clearly what the current design is costing you and all there is to be gained by making your business less dependent on you.
In the next article in this series, we'll look at another decision owners tend to leave in the planning stage: when and how to start preparing for a transition, even when leaving is nowhere on the calendar.
1. How do I know whether I have a delegation problem or a hiring problem?
Not every capacity issue means you need to hand off more. A team that doesn't yet have the skill or judgment a task requires has a development or hiring gap, not a delegation failure. Delegation works when you're handing something to someone capable of growing into it, with the support to actually get there.
2. Why does delegating feel harder than it should, even when I trust my team?
For many owners, delegation isn't just a task-management decision. It's an identity decision. Being needed can feel like proof of your value to the business, and stepping back can feel like giving that up. Those feelings are real, but they often lead owners to keep work they could hand off, at real cost to their time and their team's growth.
3. How does owner dependence affect the value of my business?
Buyers, successors, and lenders price risk, and a business that only works because of you carry more of it. Documented processes, clear decision rights, and a team capable of operating without your constant involvement all increase what the business is worth and how easily it can be transferred.
4. What's the first step before delegating something I've always done myself?
Get specific about what "done well" actually looks like for that task, since that's what you'll be delegating against. Then decide which decisions the person can make independently and which ones still need to come back to you. Clarity on both makes the handoff far more likely to succeed the first time.
