This morning my system woke up, looked at every project it runs, and did nothing. Not one step. Three separate programs were live and healthy, and all three were frozen.
Nothing was broken. That is the part worth sitting with. This was a textbook approval bottleneck — four separate decisions were parked, and every one of them was parked on me.
What an approval bottleneck actually looks like
It rarely looks like a crisis. There is no alarm, no angry client, no error message. It looks like a quiet morning where nothing moves.
Here is what was actually sitting there:
- A batch of finished social posts for a woman-owned self-care brand, written and waiting to publish.
- Two finished pieces of work for a wellness clinic, waiting to be sent and waiting to be cleaned up.
- A phone number for that clinic, waiting to be paid for.
- Payment copy for the same clinic, waiting to be published.
Every one of those items was done. Built, tested, checked. They just needed a person to say yes.
If you run a small business, you already know this feeling. Your designer is waiting on your feedback. Your bookkeeper is waiting on one receipt. Your installer is waiting on you to pick the colour. Nobody is idle by choice — they are idle because you are the only one who can unblock them.
Why does the bottleneck always end up being the owner?
Because you are the only one holding the whole picture, and because most of these decisions genuinely are yours. Money leaves. Something goes out under your name. A client sees it. Those are exactly the calls that should stop and wait for a human.
The problem is not that the gates exist. The problem is that they queue up quietly, one at a time, until the whole business is stalled behind a person who does not know they are the wall.
I designed my system so that nothing gets sent, paid, published or deleted without me. I still think that is right. But it means I have to actually show up and clear the queue, or the machine just sits there being very well-organised about doing nothing.
The third strike rule that saved me a week
A related step in that same clinic build had a twist worth sharing. A payment step could not be completed the way it was designed — the software genuinely cannot do the thing I asked it to do. It had now failed three times.
The old instinct is to try a fourth way. Instead, the rule I follow now is: after three honest attempts, stop and hand the decision back with options.
So it came to me not as "it failed again," but as a choice: send that invoice by hand and let the reminders chase it, or rewrite the process so it never needs that step. Two clear paths, one decision, thirty seconds of my time.
That is the difference between a blocker that costs a week and a blocker that costs a coffee break.
How to keep the queue from filling up
Three habits I am putting in place, all of them boring on purpose:
Put the queue in one place
If your approvals live across texts, email, a chat thread and someone's memory, you cannot see the pile-up. One list, one place. I get a written receipt of every open gate whether or not anything moved.
Book a slot for saying yes
Not "when I get a minute." An actual fifteen minutes, same time, most days. Approvals are not deep work — they are fast when batched and expensive when scattered.
Demand options, not questions
"What should we do?" costs you twenty minutes. "A or B, I recommend A" costs you ten seconds. Train everyone who works with you to bring the second kind.
The uncomfortable takeaway
I have built a system that runs projects while I sleep, and it still spent a whole morning doing nothing, because four yes-or-no answers were sitting in my head instead of in a text box.
You can automate almost everything in a small business except the moment where somebody has to take responsibility — so the real job is making that moment as cheap and as frequent as possible.