Take a week off and find out what you actually built

Quick answer: Tally every question your people ask you for five days. Turn the repeat ones into written rules with a dollar limit, name a backup for every seat, then step out for one day and see what breaks.

You don't have a team that runs without you until you've watched it do that. Until then you have a team that waits for you.

Count the questions

Get an index card. Put it by your phone. Every time someone asks you something, a tick mark and three words about the question. "Which supplier for gaskets." "Refund or credit." "Can I leave early." Do it for five working days and don't change how you answer.

By Friday you'll have a number, and it'll be uglier than you guessed. Most owners find that a handful of questions account for most of the ticks. The same ones, in different mouths.

That's your map. Those questions are where you're the bottleneck, and you built the bottleneck yourself, one helpful answer at a time. Every time you said "just ask me," you taught somebody that asking was the job.

Sort the card into three piles

Pile one: the answer never changes. Where the spare key lives. How a warranty claim gets logged. Which vendor gets the order. These need a written rule, one page at most, and then nobody should ask you again.

Pile two: the answer depends, but inside limits. Refund or credit. Waive the late fee or don't. Pay the overtime or push the job. This is where most of your time goes, and it's where most owners refuse to let go.

Pile three: only you. Hiring and firing. Pricing changes. Taking on debt. Anything that signs your name to a legal document. Keep these. There should be fewer than you think and more than zero.

Put a number on pile two

"Use your judgment" isn't a delegation. It's a guess your employee has to make while worrying about being wrong.

Give them a number instead. Say, anybody on the crew can spend up to $200 to make a customer whole, no call needed. Over $200, they call you. A shop foreman might get $500 for parts. A front-desk hire might get a $50 credit.

Pick the number by asking what mistake you could live with. If somebody burns $200 on a bad call, you'll grumble and move on. That's the price of training them. If the number makes your stomach turn, it's too high. Cut it in half and raise it in six months.

Then write it down. One page titled "What you can decide without me." Tape it inside the cabinet door or pin it in the group chat. Add to it every time a new question shows up twice.

Name a second for every seat

Your bookkeeper gets the flu. Your best installer breaks a wrist. Your office manager has a baby, which is a good thing and also a Tuesday you didn't plan for.

For every role that matters, there should be a named second who can do it badly but do it. That's the bar. Not well, just without the place shutting down.

Cross-training costs something. The second person spends a few hours a month shadowing, and the primary person has to be willing to teach. Some won't. A person who guards their job by keeping it a secret isn't protecting the company, and you should know that about them now. Better now than the morning they don't show up.

Pay for the training. Time, a small raise, a title. If you ask someone to learn a second job and give them nothing, you've borrowed from them. Pay it back before they ask.

Hold the line when they hand you the monkey

Here's where good owners fail. The system is written. The limits are set. And then someone walks up and says, "Hey, quick question," about something inside their limit.

The easy move is to answer. It takes ten seconds, and you feel useful.

Don't. Say, "What would you do?" Then wait. Let the silence go longer than is comfortable. When they answer, and they usually have one, say "Do that." If it's about 80 percent as good as what you'd have done, that's a pass. The other 20 percent is the tuition.

This will cost you some money and some pride. A person will make a call you'd have made differently, and a customer will get a $40 credit you'd have refused. Eat it. Serving your team means building people who can stand on their own, and that means letting them make small mistakes where small mistakes are cheap.

It also takes a backbone. Some people have learned that pushing the decision up is safer than owning it. Being kind to them doesn't mean carrying their load. Be warm, and keep sending it back.

Show them the scoreboard

People can't run something they can't see. If the only person who knows whether the week was good or bad is you, they're flying blind. Put the numbers where they can read them. Run your week off one page of numbers walks through building that page, and a version of it belongs on the shop wall.

When people see the score, a lot of questions answer themselves.

Run the test

Start small. Pick a Friday. Tell the team a week ahead that you'll be out and unreachable except for three things: someone's hurt, someone's threatening a lawsuit, or money over a set amount is at risk. Write those three on the same page as the limits. Everything else waits.

Then turn off your phone. Not silent. Off.

Don't peek at email on a bathroom break. Peeking tells the team you don't trust the system, and they'll feel it when you're back.

If that Friday goes fine, take a Monday and Tuesday. Then a full week, once a year. You'll learn more from that week than from any book on management. You'll find the rule you forgot to write. You'll find the person who rose to it, and the person who froze.

When you get back

Don't undo anything. Walk in, ask for the list of what came up and how it was handled, and say thank you before you say anything else. Praise the call they made, even if you'd have made a different one. Fix the gap in the rulebook, not the person who fell into it.

And leave the place better than you found it. That's the old code. The business you hand back to them on Monday should have a clearer rulebook, a sharper backup plan and a bit more trust than it had on Friday.

Some people won't make it. You'll give one the limit, the page and the patience, and they'll still need you for every call. That's a different problem, and how to fire someone without wrecking them or your team covers it. But be sure it's them and not you. Plenty of "weak" employees were just never allowed to decide anything. A lot of late payments work the same way: most late invoices are a process problem, not a people problem, and most dependent employees are a process problem too.

The goal isn't to disappear. It's to be able to leave, and to come back to a place that's still standing and a bit better for it.