Vol 1 · Issue 85 · Monday, August 3, 2026

A guy I worked with last spring ran a commercial landscaping company. Good business. Eleven employees, roughly $180K a month, the kind of operation that looks perfectly healthy from the outside.

He called me because revenue had been flat for fourteen months and he was working more hours than he did back when he was a one truck operation.

I asked what he thought the problem was. He said he needed better people.

I have heard that one about four hundred times. It is almost never true.

So I gave him homework instead of advice. For five business days, keep a log. Every single time somebody came to him with a question, a decision, an approval, a "hey, quick thing," he writes down three columns. What they wanted. How long it took. And whether he was genuinely the only human being on earth who could have answered it.

That is it. No strategy. No org chart redesign. Just a tally.

Friday afternoon he texted me a photo of a legal pad with seventy one entries on it.

Seventy one interruptions in five days. Call it fourteen a day.

Here is the part that made him go quiet on the phone. When he went back through and honestly marked the ones that actually required him, he came up with eight.

Eight out of seventy one.

The other sixty three were things like approving a $340 equipment rental, deciding whether to push a Thursday job to Friday, and telling a crew lead it was fine to buy mulch from the backup supplier because the first one was out of stock.

Sixty three decisions that anybody with two years of experience and a little permission could have made without him.

He did not have a people problem. He had a permission problem. And permission problems always look like people problems from the inside, because the symptom is identical. Nothing moves unless you touch it.

Nobody sets out to build a business where they are the switchboard. It happens by accident, and it happens for a reason that is actually kind of flattering.

In the early days, you were the only one who could make the call. That was true. You knew the margins, you knew the clients, you knew which vendor would screw you on a rush order. So every decision routed to you because routing it to you was correct.

Then you hired people. And the routing never changed.

Your team learned, very quickly and very rationally, that the safe move is to ask. Asking costs them nothing. Guessing wrong costs them a conversation they do not want to have. So they ask. Every time. And you answer, because you are helpful and it takes eleven seconds and the alternative feels like abandoning them.

Eleven seconds, fourteen times a day, is not the real cost. The real cost is what those interruptions do to the shape of your week.

You cannot think about pricing while you are approving mulch. You cannot build a referral system in nine minute gaps between questions. The work that actually grows the company requires uninterrupted blocks, and the switchboard job destroys uninterrupted blocks by design.

That is why you have been flat for fourteen months. Not because your people are bad. Because the only person allowed to work on the business spends the whole day working in it.

When I dig into this with owners, it almost always sorts into one of three buckets. Most people have two of them running at once.

The approval bottleneck is where you start, because it is the one you can fix this week without hiring anybody, writing anything long, or having an uncomfortable conversation.

Here is the whole system. You are going to sort every recurring decision in your business into three tiers, and you are going to tell your team which tier each one lives in.

Green. Do it. Do not tell me. These are decisions where the cost of being wrong is small and the fix is easy. Rescheduling a job. Buying supplies under a dollar threshold you set. Comping a small charge to keep a client happy. Answering a routine client question. Your team makes the call and moves on, and you never hear about it.

Yellow. Do it. Tell me after. Slightly bigger stakes, still reversible. Issuing a partial refund. Bringing on a temp for a week. Agreeing to a scope tweak that does not change the price. They act, then they log it somewhere you can see it. Notice the order. They act first. The telling is a record, not a request.

Red. Ask me first. Genuinely hard to undo, genuinely expensive, or genuinely mine. Firing someone. Signing a contract. Changing pricing. Taking on a client in a category we have decided we do not serve. Anything above a real dollar number.

The sorting rule is two questions. How expensive is it to be wrong, and how hard is it to undo? If it is cheap and reversible, it is green. If it is expensive and permanent, it is red. Everything in the middle is yellow, and yellow should be your biggest list.

Now here is the move that makes this actually work, and it is the part everybody skips.

You write the Red list. Only the Red list. Then you tell your team that anything not on that list is theirs to decide.

Most owners do this backwards. They try to write out every green decision, get eleven items deep, realize the list is infinite, and quit. It is infinite. That is the point. You cannot enumerate everything your team might face, but you can absolutely enumerate the fifteen or twenty things you actually need to be consulted on.

Default is theirs. Exceptions are yours. Not the other way around.

They will. Let us just sit with that for a second, because it is the real objection and pretending otherwise is insulting.

Somebody is going to comp a charge you would not have comped. Somebody is going to reschedule a job in a way that annoys a client. Somebody is going to buy the more expensive thing because they did not know about the vendor discount.

So price it out. Genuinely. What does a bad green decision cost you? A couple hundred bucks? An apology email? Fine.

Now price out the other side. Fourteen interruptions a day, every day, for the last fourteen months, and a company that has not grown a dollar in that time. What did that cost?

It is not close. It has never once been close in any business I have looked at.

And there is a second thing that happens, which nobody warns you about. When somebody makes a bad call and you do not take the decision back, they get dramatically better at making that call. That is the entire mechanism by which people develop judgment. You cannot train it in a meeting. You train it by letting somebody own an outcome and feel it.

Every time you snatch a decision back after a mistake, you reset that person to zero and you re hire yourself for the job.

One rule that keeps this sane. When a green decision goes sideways, you are allowed to ask exactly one question. "What would you do differently next time?" Then you shut up. You do not fix it for them, you do not add it to the Red list, and you do not tell the story at the next team meeting.

A decision framework that lives in your head is just a mood. Your team cannot read your mood, so they will keep asking, and you will get frustrated that they are still asking, and you will conclude, again, that you need better people.

Put the Red list somewhere everybody can see it. A pinned message. A single page in whatever your team already opens. The back of the schedule. I do not care where, as long as it is one place and it is not an email from four months ago.

For the yellow log, keep it stupid. A shared sheet with date, what happened, who decided. If you want it to run without anybody remembering to update it, you can wire the notification up in Make.com so that the moment somebody issues a refund or opens a scope change, a line lands in the sheet automatically. Ten minutes of setup, and it stops being a habit anybody has to maintain.

If you want to know where your hours are actually going before you start, Rize will tell you honestly, and honestly is the operative word. Everyone thinks they know how their day breaks down. Almost nobody is right. It is a genuinely uncomfortable week and worth every minute of it.

And if a chunk of your interruptions are decisions that get made verbally in meetings and then evaporate, record the meetings. Fathom will capture them and pull the action items out, so the decision exists somewhere other than four people's memories. A shocking number of "quick questions" are just somebody trying to reconstruct what was agreed to on Tuesday.

Run the tally. Five business days, three columns, a legal pad or the notes app. What they wanted, how long it took, did it need you. Do not change your behavior while you are logging. You are taking a baseline, not fixing anything yet.

Friday, sort it. Count how many genuinely needed you. I will bet you a bourbon it is under twenty percent.

Then write the Red list. Fifteen to twenty items, no more. If it runs past twenty five you are hedging, and your team will read a twenty five item list as "ask about everything," which puts you right back where you started.

Send it out with one sentence. Something like: here is everything I need to be looped in on, and anything that is not on this list, you have my full backing to decide.

Then, and this is genuinely the hardest part, when somebody comes to you with a green decision, do not answer it. Ask them what they think they should do. They will tell you. It will be right. Say "sounds good, go do it," and then let them.

You will do that maybe forty times before the asking stops. Forty conversations to buy back fourteen interruptions a day for the rest of the life of the company.

The landscaping guy got his tally down to four a day inside a month. He used the reclaimed mornings to build a maintenance contract offer he had been meaning to write for two years. That offer added about $40K a month by the fall.

He did not need better people. He needed to get out of their way.

On Wednesday we are going after the second bottleneck, the one where the answer lives in your head and nowhere else. Because you can hand out all the permission you want, but if nobody knows how the work is supposed to get done, permission just means they get to guess faster.

Reply to this one with BOTTLENECK and I will send you the decision tier worksheet I use with clients. It is one page, it has the two sorting questions on it, and it has a starter Red list you can cross things off of instead of staring at a blank page.

Talk Soon,
Dan
Dan Kaufman
Founder, Dead Simple Growth and Pinnacle Masters

P.S. If you read that whole thing and thought "my situation is different, my team genuinely cannot make these calls," go run the five day tally anyway. Not to prove me right. To find out whether you are describing your team or describing a habit you built. The legal pad does not have an opinion, which is exactly what makes it useful.