A bottleneck is the point where work slows down because capacity, information, or a decision is missing. In a small business it is rarely obvious from the org chart. It shows up as requests that sit for days, people who are always busy but never finished, and a sense that the same problems keep returning.
This guide describes a simple way to find them without buying software or hiring consultants for a long project.
Start with one real piece of work
Pick a workflow that happens often and matters to clients or revenue. Examples include onboarding a new client, handling a document request, processing a bill, or completing a recurring report. Choose one workflow to begin. Trying to map everything at once usually produces a diagram nobody uses.
Map the steps as they actually happen
Ask the person who does the work to walk you through the last few instances. Write down each step in order. Include the informal steps: the check-in with a colleague, the email that gets forwarded, the spreadsheet that gets updated by hand.
Avoid describing the process as it should work. The map is only useful if it matches reality.
Mark four things at every step
For each step, record:
- Handoffs: where the work passes from one person or system to another.
- Waiting: the time work spends in a queue, an inbox, or a pending state.
- Rework: anything sent back, corrected, or done twice.
- Ownership: who is accountable for the step, and who covers it when that person is away.
Bottlenecks usually appear where waiting and rework cluster around a single handoff or a single owner.
A starter checklist
Use these questions to review your map:
- Does any step depend on one person who is not always available?
- Is there a queue (email, paper, a shared folder) where requests wait without a visible owner?
- Do the same details get typed or checked more than once?
- Is there a step where people regularly ask “where is this now?”
- Are approvals or reviews scheduled, or do they happen whenever someone notices?
- Which steps cause the most rework, and what usually triggers it?
- Would a new employee be able to follow this workflow using written instructions?
If several answers point to the same step, that step is a strong candidate for attention.
Prioritize before you change anything
Not every bottleneck is worth fixing first. Consider how often the problem occurs, how much time it consumes, how much risk it carries for clients or compliance, and how difficult the change would be. A simple grid with those four factors is often enough.
Agree on one or two measures before any change, such as the number of days a request waits or the number of handoffs before completion. Measuring the baseline lets you tell whether the change helped.
Where to go next
Bottleneck reviews work best when they lead to clear owners and a short improvement plan. Our Business Process Optimization service is designed for this kind of review. You can also talk with us first if you are unsure where to begin.
This article is general operational education. It is not legal, tax, accounting, or financial advice.