The order came in at nine, and you didn’t ship it until the next day. The customer messaged twice — “any news?” — the manager checked with the warehouse three times, and the warehouse was waiting on accounting to confirm payment. Sound familiar? The question of how to find bottlenecks in your business processes usually shows up exactly when volume grows and your sense of control shrinks. The good news: the first and most useful pass, you can do yourself — no auditor, no tools, just a sheet of paper and a couple of hours of attention.
At LPF we’ve been building and maintaining digital systems for Ukrainian small and mid-sized businesses since 2018, and almost every project starts the same way — not with code, but with a simple drawing of how an order actually moves through the company. This article shows you how to make that drawing on your own.
Why it “feels fast” but really isn’t
Inside a business, time gets distorted. The owner remembers the active minutes — packing, calling, confirming. But the gaps, when the order just sits and waits, don’t register: during those minutes nobody’s doing anything, so there’s nothing to recall.
That’s where most of the loss lives. In a typical process, active work is the smaller share; the rest is waiting — for someone to open their email, to forward it to a chat, to “get around to it.” The customer, meanwhile, doesn’t feel your activity. They feel the full clock — from “I paid” to “I received it.” And they judge you by that.
So the goal isn’t to see how much you work. It’s to see where the order stands still. A bottleneck isn’t a lazy person. It’s a point where the flow narrows: everything reaches it fast, and past it, things trickle out one drop at a time.
Step 1. Draw the map of a single order
Take one typical product or service — not the hardest one, not the exception, just the thing that happens most often. Then walk one order through, from the very start to the very end, step by step.
Write each stage as its own box, left to right. For example: request comes in → manager sees it → clarifies details → issues an invoice → customer pays → accounting confirms → warehouse packs → handed to delivery → customer receives → deal closed.
The key rule: mark the handoffs. Every time a task passes from one person (or department, or program) to another, draw an arrow. It’s on these arrows, in the moments of handoff, that stalls happen most often — because nobody owns the gap “in between.”
Don’t try to make it pretty or “correct” right away. Draw it as it truly is, with all the little circles of “and here we wait for a Viber reply.” An ugly honest map is worth more than a pretty invented one.
Step 2. Write the time on every arrow
Now the important part. Next to each stage and each arrow, write two numbers: how long the work itself takes, and how long the waiting before it takes.
“Manager processes the request” — the processing takes 10 minutes. But the request landed at 9:15 and the manager opened their inbox at 11:00. So: work — 10 minutes, waiting — 1 hour 45 minutes. Write both down.
No exact data? No problem. Estimate by eye and mark it with a question mark. Often the very fact that you can’t name the time is the diagnosis: if nobody in the company knows how long an order sits between payment and packing, then nobody is controlling that stretch.
Once the map is labeled, add up all the work time separately from all the waiting time. Almost always the second number is several times the first. Now you can see the scale.
Step 3. Find the stall — where the queue is longest
Look at the map and hunt for three things.
First, the longest wait. The one stage the order sits in front of the longest is your main bottleneck. Don’t spread yourself thin: start there, because that’s what stretches your total time the most.
Second, the loops back. Arrows that go in reverse: “warehouse asked the manager again,” “accounting sent it back for clarification.” Every such loop is double work plus another wait. It’s usually a sign that the previous step was missing information.
Third, the points where everything depends on one person. If several arrows converge on one name and the process halts without that person — that’s a bottleneck even when it isn’t hurting right now. They get sick, go on vacation, and the flow stops.
That’s how to find bottlenecks in your business processes for real: not by guessing, but by reading them off your own map. They almost always turn out to be somewhere you didn’t expect.
Step 4. Count what the stall actually costs
An abstract “it’s slow” motivates no one. Translate it into two plain numbers.
Lost time. If an order sits half a day on average between payment and packing, and there are dozens of such orders a week — multiply it out. You’ll see not minutes but days and weeks that customers simply spend waiting every month.
Lost money and customers. A long wait isn’t just an inconvenience. It’s customers who didn’t come back, discounts given “for the delay,” hours of manager time spent replying “almost there.” Estimate, even roughly, what an hour costs for the people who service the stall instead of selling.
Once the number is on paper, the decision to change makes itself. And there’s a bonus effect: you stop hiring “one more manager” for a spot that doesn’t need more hands — it needs one unnecessary pause removed.
What to do with what you found
Most bottlenecks yield to simple principles. Cut the extra handoffs — if a task hops between four people, some steps can be merged. Make status visible — when everyone can see what stage an order is at, the “any news?” questions disappear, and with them the waiting. Remove the repetitive manual steps where all they do is move data from one place to another: that stretch is most often exactly the one a system closes without a human in the loop.
Some of this you’ll roll out yourself by tomorrow. But when the bottleneck is manual re-keying of data between spreadsheets, messengers, and programs that no one can see, that’s where systematic work begins: wiring the steps together so the order moves without being pushed by hand.
If you’ve drawn your own map and spotted the place where everything stops, that’s already enough to start a conversation. Send us that drawing, or describe the process in words, and we’ll look together at what can be cleared from that stall first — fastest, and with the most to gain.