← Journal

framework-deep-dives

The Approval Trap: why every decision still lands on your desk — and the one move that ends it

July 11, 2026

Your team is good. They follow the processes and they handle delivery. And every decision somehow still ends up on your desk. That is not a people problem. It's a power problem — and it has a name. The approval trap.

It's 4:47 in the afternoon and your phone buzzes. A team member needs you to weigh in on a pricing exception. You step away from whatever you were doing and you handle it. Two hours later it buzzes again — a client wants a project change. You handle that too. The next morning, before your coffee, a complaint lands in your inbox that needs a call from you. Each decision in isolation is small. None of them require you in any deep sense. Most of them your team could make. And yet every one of them still comes to you.

Somewhere in your head the question is forming: I have a team. I built systems. Why am I still the one deciding everything? The answer is not obvious — if it were, nobody would ever get stuck here.

The approval trap looks like a people problem. It isn't.

From the outside it looks like your team can't, or won't, decide. But they clearly can — the work proves it. They handle delivery every single day. They bring decisions to you for sign-off not because they are incapable, but because they do not know which decisions belong to them.

This is the defining problem of Power at Level 3, the Multiplier: authority is distributed, but it's reversible. You've handed the team some authority informally, but the rules for when you'll override them were never written down. So they'd rather ask — because asking is a lot safer than guessing.

Here's what the team learned, even though nobody said it out loud. Yesterday someone made a call on a refund, you found out later, and you reversed it. The next time a similar situation comes up, that person will not make the call. They'll come to you first, because they learned that decisions in that category are not theirs to make. Their hesitation is not their fault, and it's not exactly yours either. It's structural. The rules of authority were never written, and without rules every decision sits in a gray zone. In a gray zone, the safest move for any employee is to ask the boss.

Said plainly: your team is asking you to decide things they have the skill to decide themselves. The reason they keep asking is not competence. It's permission. They were never told — clearly, formally, in writing — which decisions are actually theirs. That is the approval trap, and inside it the team is behaving completely rationally against a set of rules nobody ever gave them.

The cost hides in a second trap: speed

There's a reason you keep choosing to just handle it yourself, and it's worth seeing clearly. When a decision lands on your desk, you resolve it in about 30 seconds — you've made this same call a hundred times, so you know the answer. Training a team member to make it takes longer. Maybe 30 minutes the first time: explaining the criteria, walking the tradeoffs, showing how you actually think about the problem.

Thirty seconds versus 30 minutes. In isolation, you do it yourself every time — it's 60 times faster. That's the speed trap, and it's the sibling of the approval trap. Here's what it hides: you are not making one decision. You are making the same kind of decision over and over — refunds, pricing exceptions, scope changes — the same handful of categories, for years.

So the real math is not 30 seconds versus 30 minutes. It's 30 seconds times a thousand future decisions you keep making forever, versus 30 minutes once. The break-even lands at decision number 61. Once a category comes up more than 60 times, training starts paying you back — and every recurring category in a real business hits 60 in a matter of months. The team's capability compounds. Yours does not.

What Level 3 actually asks of you

Years ago I ran a video production company called Lightabout, and most of the editing came through me. Not because I was the best technical editor — there were far better editors on the team. I held onto it because I believed clients were hiring the "Jonathan Lauer style," that what they paid for was me.

It took me longer than it should have to ask the honest question: were they hiring me, or were they hiring a great result? The answer was the result. Clients always hire the result. The story that they wanted me was one I needed to be true so I could feel important — but clients pay for outcomes. The moment I separated myself from the result, the work changed. I wrote down what my company's quality actually meant: pacing, cuts, audio principles, color-grade decisions. The things that lived in my head became principles on a page. Then I handed the editing off, and the team produced the same quality. Sometimes it got better — and clients never noticed, because what they were hiring was the result, not me.

That is the shift at Level 3: from "only I can do this right" to "I can define what right looks like." From the work to the standard. It's the same move I keep coming back to — that the hardest, highest-value work an owner does is the work only the owner can do, and deciding every refund is not it. It's also why seven figures of revenue can still leave you holding a sixty-hour job: the business grew, but the authority never left your desk.

The one move that ends it

You don't break the approval trap by delegating everything at once. You make one authority transfer formal and irreversible. Just one.

  1. Pick the smallest category — the one where, if a call goes wrong, nothing important breaks.
  2. Document how you decide it — the actual criteria, the real thought process, the conditions that drive a yes or a no.
  3. Name the person you'll trust with that category.
  4. Make it formal. Write one sentence and send it to the team: "From here on out, Marcus owns all time-off requests." That's it.
  5. Commit in advance and do not take it back. Write the commitment down for yourself, because the first imperfect decision is coming — not if, but when. The team is watching to see whether your behavior matches your words.

Then watch what happens the first time a decision in that category comes up and your phone doesn't ring. That quiet moment is what building decision-makers feels like. The goal is a company that doesn't need you to run — so you can give your time to whatever matters most. Which raises the only question that counts: what would you make the most important thing, if you finally had the time to make it the most important thing?


Not sure whether you're at Level 3 or somewhere else? Take the free 7-Level Assessment — it names your level, your current superpower, and the constraint holding you back. No guesswork. Or see the ways to work together.