"The last time I was away from the company for more than three days was when my mom was in the hospital. And during those three days, I averaged forty-some phone calls a day."
An owner who makes industrial parts said this less than ten minutes after sitting down for our first meeting. He said it without emotion, like reading a weather report. His sales support staff added: "We're not trying to bother him. But some things really can only be decided by him."
First, something in the owner's defense: "only I can decide" is usually true in the moment. He knows this customer paid late several times last year. He knows which customer will return the batch if this part number is swapped for a substitute. He knows which line on the margin sheet the discount the salesperson just promised will hit. It's not that he loves control. This information really does live only in him, and it has never been written down. So he can't take a vacation, and it's not because his staff won't improve. It's because the company's decision system is him.
The real reason you can't take a vacation: "what to decide in which situation" has never left your head. Most owners' delegation fails because what they hand over is "tasks," not "judgment." They hand over the quotation, but not the quotation thresholds. They hand over purchasing, but never spell out what to do with exceptions. They hand over customer complaints, but never name who makes the final call. To be able to take a vacation, you don't need to find someone whose mind works like yours (you won't find one). You need to break your judgment into three parts that can be written down: thresholds, exceptions, and the decision-maker. Once those three are written down, running, and leaving a record, your instinct becomes the company's system. As for judgments that can't be broken down, those were never meant to be delegated. What you should do is shrink them into a very short list, short enough that you can clear it in ten minutes while on vacation.
I'm Johnny Yang, Brightstream Technology, Taiwan. I've led my team through implementation work for seven years, handling 252+ projects across 32+ industries. The method below is something I've used over and over on site. It has nothing to do with which module a system vendor wants to sell you.
1. First, admit it: your company runs on asking you
To find out whether you're a single point of failure, you don't need a survey. Scroll back through the past week of your messaging apps, pick out every message that asks you something, and sort them. You'll see three kinds. The first is notifications: no reply needed, he just doesn't dare not tell you. The second: he actually knows the answer but wants your sign-off, because he's afraid of getting scolded if he gets it wrong. Only the third is judgment that truly only you have.
In the projects I've seen, the third kind is usually the smallest. But because the first two are mixed into the same chat window, it feels to the owner like "everything comes to me." The damage isn't the time. It's that it leaves you without the energy to even tell them apart. Every message looks equally urgent, so you carry all of it yourself, and after long enough you reach a conclusion: this company can't run without me.
Worse, this structure trains your staff in reverse. When the shortest path for everything is "send it to the boss," nobody is foolish enough to take on the risk of judging it themselves. You think they're afraid to decide. In fact they learned long ago: deciding brings no reward, deciding wrong brings punishment, so don't decide. The busier the owner gets, the further staff pull back. It's a loop that speeds itself up.
2. Take a decision apart and it has only three parts
That "here's how I'd handle this" in your head sounds like experience, like instinct. But when you actually take it apart, you'll find most of it can be stated clearly. It has just three pieces: within what range this can be done directly (threshold), what to do when it falls outside that range or something unfamiliar comes up (exception), and who has the authority to call it when an exception happens (decision-maker).
| Part | The question you must answer | What happens without it |
|---|---|---|
| Threshold | Under what conditions can this be done without asking me? | Everything becomes a request for approval, staff won't move, you can't take a vacation |
| Exception | For cases that don't meet the threshold, which path do they take? How soon must there be an answer? | Every exception flows back to the owner, and the threshold might as well not exist |
| Decision-maker | When an exception happens, who has the authority to decide? What about when that person is out? | Everyone waits on everyone else, and the case gets stuck in the middle with no one responsible |
The table looks simple, but in practice you'll get stuck on one thing: you can't state your own thresholds. That's normal, because nobody ever forced you to say those conditions out loud. On site, I don't ask the owner "what are your rules." I take five to ten real cases from the past and go through them one by one: "How did you decide this one, and why?" By the seventh or eighth, the rules surface on their own, and they're usually simpler than the owner thought.
One more thing has to be set up alongside: a trail. Every delegated decision has to record who made it, when, and on what conditions. Otherwise, when something goes wrong, all that's left is finger-pointing, and next time you'll take the authority back. The trail isn't for catching people. It's so that when you come back from vacation, you can understand what happened that week in ten minutes. This is also why delegation almost always ends up in some system. Not because systems are magic, but because verbal delegation leaves no record and doesn't survive the third dispute.
3. Don't set thresholds by amount; start from what happens if it goes wrong
Most owners' first instinct when setting a delegation threshold is to pick an amount: below this much, you decide yourself. Amounts are convenient, but they're only a proxy, and they often miss the point. The same small sum spent on switching packaging material might be fine. Spent on a substitute for a critical part number, it might get an entire batch returned by the customer. And the same large sum paid to a fixed supplier under contract carries little risk.
The real questions are three. First, if this goes wrong, can it be undone? Reversible things (a discount can be credited afterward, a schedule can be changed) get looser thresholds. Irreversible things (shipping, putting material into production, external communications, signatures) get tighter ones. Second, who pays for the mistake? If it only affects internal efficiency, loosen. If it can hurt customer relationships or receivables, tighten. Third, does it compound? Extending one customer's payment terms once is fine. Without a rule, three months later you'll find half your customers are on extended terms.
Look again through those three questions and your thresholds will read more like conditions than numbers: "If stock on hand is sufficient, the customer has no overdue receivables, and the discount is within the set range off list price, the salesperson can close directly." The benefit of writing it this way is that it can be checked, and it can be built into a workflow. If you want to know which process to tackle first, I covered the order of judgment in "Which process first? Implementation order decides success or failure". The same applies to thresholds: start with the high-frequency, reversible ones. Don't go after the most sensitive ones first.
4. Exceptions are the real test of delegation
For many owners, delegation stops at thresholds and goes nowhere. Two months later they declare it a failure. The reason is almost always the same: exceptions have no path. Rules handle the cases that look alike. What makes owners anxious was never those. It's the ones that don't look alike. If everything that doesn't fit goes to "find the boss," you've only delegated the part that didn't need delegating.
For exceptions to be delegated, three things have to be added. First, an entry point: what counts as an exception has to be stated in one sentence, for example "fails any of the conditions above." Don't leave it to staff discretion. Second, an escalation path: who the exception goes to first, how soon they must answer, and who takes over when they're out. Third, and most often missed: a default action. If no one responds within the time limit, what happens by default?
A rule without a default action is no rule at all. Because once nobody replies, the floor falls back to the old habit: calling the boss. The default action can be very conservative, such as "hold the shipment and tell the customer when to expect an answer." Conservative is fine. What matters is that it's a "decision," not a "wait." For those two hours you're at the beach with no signal, this one line is what the company runs on.
One more warning: the exception list grows. The first time you run it, there will be so many exceptions you'll question everything. That's not failure. That's you finally seeing how much was stored in your head. The right move is to review the exception log once a week and promote any exception that shows up three or more times into a new threshold clause. After two or three months, exception volume drops noticeably, and what's left is what truly needs a human to judge.
5. Which judgments should never be delegated
Turning judgment into a system doesn't mean handing over every judgment. There are a few categories I never recommend owners let go of. It's not about trust. It's that the shape of the error cost is wrong.
The first is pricing structure and business model. A single quotation can be delegated, but "how we charge, who we sell to, how we deliver" cannot. Mistakes here don't blow up on the spot. They show up six months later as margin slowly bleeding out, and by the time you can see it, it's too late to change. The second is people coming in and going out. Who to hire, who to let go, who leads which team: this is how company culture actually gets defined. Hand it over and you've handed over the culture. The third is long-term external commitments: contract terms, exclusivity, payment-term policy, large prepayments. What these share is that they're irreversible and they lock up your future options. The fourth is the first public statement in a crisis. When something goes wrong, the first thing the company says shapes its position for the next three months. That sentence has to be the owner's.
What these four share: irreversible, cross-departmental, limited upside when done right, unlimited downside when done wrong. Asymmetric calls like these are exactly what the owner is supposed to carry. But "not delegated" doesn't mean "handled on vacation." What you actually need to practice is making them deferrable: mark these four clearly as "waits for the owner," and send everything else through the rules. Whether your vacation gets interrupted depends on how clearly that line is drawn.
By the way, this is the same problem as succession. Most family businesses can't hand over, not because the next generation isn't smart enough, but because the previous generation never wrote their judgment down. I covered the same structure in "Digitizing succession: keeping the previous generation's judgment". Whether you can take a vacation is really a small-scale succession drill.
6. So what should you do now
Starting tomorrow, do three very boring things.
First, start a log. For one full week, write down every time someone comes to ask you something. Just two columns: what they asked, and how you answered. Don't fix processes along the way. This week you're only collecting data. Second, on the weekend, lay the log out, pick the three things that come up most, and for each one write three lines: threshold, exception, decision-maker. If you can't write them, go back to real cases and ask yourself, one by one, why you decided the way you did. Third, trial-run it the following week, and deliberately make yourself an observer: when someone asks, first ask back, "Going by the rules, what would you do?" Unless they get it wrong, you don't give the answer.
After a full month, you'll have two things: a set of rules that work, and an honest exception list. Then schedule your first time away. Start with three days. Don't try for two weeks at once. When you come back, read the trail and turn what went wrong into the next version of the rules. Delegation is never handed over in one go. It gets refined round by round.
If you want to confirm which decision to start breaking down before you begin, book a free 30-minute diagnostic. I'll work through it with you and pick out the three things that eat the most of your time.




