The funnel article made the argument: fix the narrow part of the business before pouring more into the top. This article is the how. Set aside an hour, grab whoever actually does the work, and follow the steps. No software required, a whiteboard and honesty will do.
Step one: pick one value stream
Do not map the whole business, map one journey: the main path from a customer wanting something to the customer having it and you being paid. For a trades business that might be enquiry, site visit, quote, job, invoice, payment. For a clinic: referral, booking, appointment, notes and claims, recall. One stream, end to end.
Step two: list the real steps
Write each step as it actually happens, not as the procedure manual claims. Include the unglamorous ones people forget: "waits in Sharon's inbox", "sits in the ute until Friday", "gets re typed into the other system". The re typing steps and the waiting steps are usually where the story is.
Step three: put two numbers on every step
For each step, estimate:
- Touch time. The minutes of actual hands on work
- Wait time. How long the job sits before that work happens
Rough numbers are fine, argue to the nearest half day. Then add up both columns and brace yourself, because in almost every business I have mapped, the touch time is a few hours and the elapsed time is weeks. Work does not take long in most businesses. Work waits long. That gap is your opportunity, and seeing it on a whiteboard for the first time changes how a team talks about their own business.
Step four: find the constraint
The bottleneck announces itself with signals:
- The step with the longest queue in front of it
- The person everyone is always waiting on, often the owner
- The step where "sorry for the delay" emails originate
- The step that overtime never quite fixes
Circle one step. Not three, one. A system has one primary constraint at a time, and effort spent anywhere else is, for throughput purposes, decoration.
Step five: squeeze before you spend
Before buying anything or building anything, get more from the constraint as it stands. Protect that step from interruptions, move any task off it that a less loaded step could do, stop feeding it low value work, make its inputs arrive complete so nothing bounces. This is free, it is fast, and it frequently buys back twenty or thirty percent.
Then, and only then, point AI at it. If the constraint is quoting, that is your first build. If it is the owner approving everything, the build is drafts and summaries that make approvals take seconds. The bottleneck article you are holding is the targeting system for every use case article later in this series.
Step six: expect it to move
Widen one narrow point and the constraint migrates somewhere else, that is the funnel working as intended. Re run this exercise each quarter. Businesses that make it a habit stop guessing where to improve, and their AI spend lands where it multiplies instead of where it decorates.
A completed bottleneck worksheet on a whiteboard
Found yours? The next article puts numbers around fixing it: what AI actually costs, and how to do the ROI maths without a spreadsheet degree.