Bottleneck Resource

Adding capacity anywhere else only creates idle slack. Work still queues behind the same scarce resource, so total output does not move, and the money or effort spent elsewhere buys nothing.

Naming the resource honestly lets a founder raise the ceiling on growth instead of working harder around it. The answer is often uncomfortable. In many small businesses the resource is the founder, and the fix is to stop doing something they enjoy or are proud of.

There is also a cost argument. An hour lost at the bottleneck resource is an hour lost for the whole business. An hour lost anywhere else is only an hour lost. That is why a founder's time spent on invoicing or tidying a spreadsheet is more expensive than it looks, if the same hour could have gone to the work only the founder can do.

A Bottleneck is the limiting step in a process. The bottleneck resource is the scarce thing that step depends on. It might be a founder's own hours in a one-person business, a single software licence, one machine, or a specialist that every job has to pass through.

The difference matters in practice. A step is fixed by changing how the work flows. A resource is fixed by adding supply, protecting its time or taking work off it.

• Naming the busiest person. Busy and bottleneck are different things. The resource is where work waits, not where people look stressed.
• Buying more of something that is not scarce. A second licence or a faster laptop does nothing if the real limit is one specialist's calendar.
• Keeping the resource busy with low-value work. Admin, status meetings and tasks others could do all use time that sets the pace for everything.
• Letting it run empty. A bottleneck that waits for input from an earlier step loses output for the whole business. Keep a small queue in front of it.
• Fixing it once and moving on. Once the resource has more capacity, the limit moves to another one. Check again after each fix.

• Follow one piece of work from start to finish and note where it waits longest.
• Ask whether the answer is your own time. In most one-person businesses it is.
• List what that resource does in a week and mark each task as either only it can do, or someone or something cheaper could do.

• Stop spending its time on work a cheaper resource could do.
• Protect what is left for the work only it can do, using blocks of uninterrupted time.
• Take it off the critical path through Delegation, a better tool or automation.
• Write down the repeatable parts as a Standard Operating Procedure (SOP) so others can take them on.