The bottleneck signature

Part 3 of 9. Six tells. Almost every stuck process shows at least three of them.

Office Clones
October 20, 2026

A CEO removes bottlenecks. An owner pushes harder through them. The difference is not intelligence or stamina — it is where the attention goes.

The useful thing about bottlenecks is that they are not mysterious. They share a signature, and the signature is visible from the outside.

The six tells

Owner approval for small decisions. If a $200 refund, a schedule change, or a discount needs you, the bottleneck is you, and the process is a queue with one server.

No written process. If the answer to "how does this get done" is a person's name, there is no process. There is a person.

Too many tools. Every handoff between systems is a place work can be dropped. Five tools for one job is four places to lose things.

Unclear roles. "Everyone helps with that" reliably means nobody owns it.

Manual follow-up. Anything that depends on someone remembering is a bottleneck that only shows up on the weeks you are busiest.

Information that lives only in someone's memory. Including yours. Especially yours.

If a project's status only exists in your head, that is not a strength. It is an unowned process with a very committed volunteer.

Find yours

Run the signature across three places: intake, delivery, support.

Intake — how does a new enquiry become a contact with a follow-up on it? If the answer involves you noticing, that is the bottleneck.

Delivery — where does work sit waiting? Not "where is it hard" — where does it wait. Waiting is the tell.

Support — which questions repeat? Each repeat is either a missing document or a missing instruction, and neither of those is a workload problem.

Document the repeatable work

Anything that happens more than once deserves a written procedure. Not a manual. Seven lines:

1. What triggers it
2. Who owns it
3. The steps, in order
4. Which tools it touches
5. What "done" looks like
6. What to do when it breaks
7. When it gets reviewed

It does not need to be elegant. It needs to be findable and followable by someone who is not you. That is the entire specification.

Start with the one that generates the most repeat questions from your own team. It is almost never the hardest process — it is the highest-frequency one, which is why it feels like it is everywhere.

Reduce manual work

For each repeated task, pick exactly one: automate it, template it, delegate it, batch it, or eliminate it.

Most owner time is spent on tasks that were never decided on — they simply arrived one day, grew, and became routine. Naming the choice is the work. A saved response replaces rewriting the same answer for the tenth time. A follow-up workflow replaces memory.

The one-way door

Do one process properly before you start the next. A half-documented process is worse than an undocumented one, because it looks finished.

The test is blunt: can someone else run it on Monday while you are unavailable, and produce the same result without calling you? If not, it is not documented yet — it is annotated.

Do this today

Pick the process that generates the most repeat questions. Write the seven lines. Send it to whoever asks most often, and ask them to run it and tell you where it breaks.

Where it breaks is the next document.

What this is part of

Part three of nine in How to Be a Real CEO in 30 Days or Less. The Workflow Improvement Plan worksheet in the full guide walks the same seven lines, plus current owner, desired owner, delegable steps, and a review date.

[Get the full guide and the four worksheets →]

Next Thursday: why adding an offer is the most common way to make a business worse.