To count the work bottleneck, keep one sticky note where you work and add a tally mark every time a task bounces back to you for a decision, an approval, or a fix. The task with the most marks after a week is your constraint. That number tells you where the process only exists when you are in the room.
- The work that keeps returning to you is the clearest signal of where your business depends on you personally.
- A sticky note and a pen can find your bottleneck without any diagnostic software or consultant.
- Every fix that requires your approval puts you right back in the middle of the thing you were trying to step out of.
- Counting beats guessing because the task you think is the problem is rarely the one with the most marks.
- The highest tally is your constraint, and a constraint moves. Solve one and the next one appears.
- The method ends on a number, not a solution, because the number is what you have been missing.
You know the feeling. You hand something off, you step back, and three hours later it is on your desk again waiting for your sign-off. So you fix it. Which, of course, puts you right back in the middle of the thing you were trying to step out of. The quiet thought that follows is the whole reason for this post. No, because then that puts me back in it. All right. So I’m trying to get out of it. If you want to count the work bottleneck in your business, you do not need a tool, a dashboard, or a diagnostic. You need a sticky note.
Here is what most owners get wrong before they even start. They try to reason their way to the bottleneck. They sit down, think hard, and name the task that feels heaviest. Then they build a fix around that guess. The guess is almost always wrong, because the heaviest-feeling task and the most-frequent task are rarely the same thing.
What is the work bottleneck?
The work bottleneck is the single point in your business where tasks pile up because they cannot move forward without you, and it is the one constraint that caps how much the whole system can produce no matter how hard everyone else works. It is the place where the process only exists when you’re in the room. Every system that routes a decision back to you has a bottleneck shaped exactly like you. The Theory of Constraints frames it plainly. A system has one weakest link that limits total output, and improving anything other than that link changes nothing.
The work that keeps coming back to you is not a to-do list. It is a map of where your business cannot function without you.
Why does counting beat guessing?
Counting beats guessing because the effort you spend on rework and approvals is invisible until you tally it, and invisible effort is the effort you never fix. The returns feel small in the moment. A quick approval here, a fast correction there. None of them feel worth tracking. That is exactly why they survive. This is sometimes called the hidden factory, the layer of workarounds and redoing that nobody measures because it never appears on a single report.
When you count, two things happen. First, you stop arguing with yourself about which task is the real problem. The marks decide. Second, you see the shape of your week honestly for the first time. The pattern I see across client engagements is that the task owners name as their biggest drain finishes third or fourth on the tally. The real bottleneck was something small and constant they had stopped noticing.
The counting method, step by step
This is the whole method. You can start it today with nothing on your desk but paper.
- Put one sticky note somewhere you always see it. Monitor edge, notebook cover, phone case.
- Every time a task comes back to you for a decision, an approval, a correction, or a question someone else could have answered, write one word for it and add a tally mark.
- If a task already has a word on the note, just add a mark next to it. Do not re-describe it.
- Do this for five working days. No analysis during the week. You are only collecting.
- On day five, rank the words by number of marks, highest to lowest.
That is it. A tally sheet is simply a tool for counting how often something happens, recorded in real time right where it happens. You are building one by hand. The counts can later be ranked so the biggest category stands out, which is exactly what you want.
If a task comes back to you more than any other, you are not the owner of that task. You are its bottleneck.
How do you read the number once you have it?
You read the number by ranking every word on your sticky note from most marks to fewest, and the one at the top is your constraint, the single place where stepping out of the work is impossible until that return path is redesigned. Ordering frequency counts this way is the logic behind a Pareto chart, where the most frequent category points straight at the problem to solve first. You do not need the chart. You need the ranking.
Here is how to think about what the ranking shows you.
| What the tally shows | What it means |
|---|---|
| One task far above the rest | A single clear constraint. Redesign its return path first. |
| Three or four tasks clustered at the top | A decision-rights problem. People route to you by habit, not necessity. |
| Marks spread evenly across many tasks | No handoff is defined anywhere. The system runs on you by default. |
Notice what this method does not do. It does not hand you a fix. That is on purpose. The moment you jump to a fix, you are back in the middle of the work, building the next thing that routes through you. The number comes first. The fix is a separate conversation, and it only works once you know which return path you are actually redesigning.
Why the fix usually makes it worse
Think about the last time you solved one of these. You probably built a step that said “send it to me when it’s ready.” That felt like delegation. It was not. You wrote yourself back into the process as the final checkpoint. Every fix that ends with your approval puts you back in it. The goal is not a faster path to you. The goal is a path that does not need you at all.
This is the quiet trap of being good at your own business. You are the best at the work, so the work keeps coming back to the best person. The tally breaks that loop by making the cost of your involvement countable. Once you can count it, you can finally decide to move it. Less mess. More momentum.
The tally mark system, grouping counts in fives with a diagonal slash across four lines, predates spreadsheets by centuries and is still used in clinical settings today precisely because it is fast, requires no tool, and is readable by anyone who walks up to the sheet. You can see the method documented in clinical quality tally sheets used to count events in real time.
Almost every time I open a client’s workflow, I find the owner has quietly become the approval step for something they swore they delegated six months ago. They did delegate the doing. They kept the deciding. On paper the task left their desk. In practice it visits daily. The tally always surfaces this one first, and the owner’s reaction is the same every time: “I didn’t realize it was that many.” That sentence is the whole point of counting. You cannot feel frequency. You can only count it.
How do I find my bottleneck without software?
Keep one sticky note where you work and add a tally mark every time a task returns to you for a decision or a fix. After five days, the task with the most marks is your bottleneck. No software, no dashboard, no consultant required. The counting itself is the diagnostic.
How long should I run the counting method?
Run it for five working days, or one full week. Less than that and a single busy day skews the picture. The goal is to catch your normal rhythm, including the small returns you stop noticing by Wednesday. One week is enough to surface a clear ranking.
What counts as the work coming back to me?
Any time a task returns for your decision, approval, correction, or a question someone else could answer. If it needs you to move forward, it counts. The small, fast returns matter most, because those are the invisible ones that keep you stuck in the middle of the work.
What if everything is tied for the top?
Evenly spread marks mean no handoff is defined anywhere, and the system runs on you by default. That is still a useful answer. It tells you the problem is not one task, it is the absence of decision rights. Start by defining who owns decisions, not by fixing any single task.
Why not just fix the task I already know is a problem?
Because the task that feels heaviest is rarely the one that returns most often. The frequent, forgettable returns are what trap you. If you fix the obvious one, you still spend your week on the counted-out ones. The tally shows you where your time actually goes.
Does the fix come after I have the number?
Yes, and keep them separate. Counting first means you redesign the right return path instead of the loudest one. Jumping to a fix too early usually rebuilds the bottleneck with you as the final checkpoint. Get the number this week. The fix is a different conversation.
Put the sticky note up today. One note, one pen, five working days. Write a word every time the work comes back to you, add a mark, and do not analyze until Friday. On day five, rank the words. The one on top is your answer.
Run it for a week, then DM me your number. I’ll tell you what it means.
… and see more of my posts in your Google results.
