How to Tell a Capacity Problem From a Flow Problem
How to tell a capacity problem from a flow problem: one needs fewer commitments, the other a better process. More evenings fix neither: check where time went.
To tell a capacity problem from a flow problem, check how much of a typical item's life was spent not being worked on. Mostly waiting means flow, and the fix is process. Worked steadily and still too much to do means capacity, and the fix is fewer commitments or a longer timeline.
How to tell a capacity problem from a flow problem in your own business
"I'm not shipping fast enough."
You have said it. Everyone building alone has. It sounds like one problem. It is two, and their fixes point in opposite directions.
Capacity problem: there genuinely are not enough evenings for what you've committed to. Flow problem: the evenings exist, but work stalls, gets started before something else finishes, or waits on a decision.
Fix a capacity problem with process tweaks and you gain nothing, because the load was simply too big. Fix a flow problem by working more evenings and you make it worse, because you pour extra hours into a leaky system.
Here is the uncomfortable bit. Without data you can't tell which one you have. So you pick the default. And the default is always capacity.
Why you always blame the evenings
Because it is the only hypothesis available.
Run on feel, and every conversation about speed turns into a conversation about effort. You feel behind. The obvious cause is that you haven't worked enough. So the plan is: find more hours. Earlier mornings. Later nights. Weekends.
That plan so rarely helps. If the real cause is flow, extra hours go into the same stalls. You finish nothing faster, you get more tired, and the tiredness itself slows you further. Then you conclude you need even more hours. It's a loop, and it ends in the version of you who can't open the laptop.
If you want to scale without hiring, this loop is the thing to break first. Scaling means more out of the same evenings. You can't get that by pushing harder through a blockage.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →The test: where did the time go?
One question separates them. Take a typical item that felt slow. How much of its life was spent not being worked on?
Measure the elapsed time from start to done. Then ask how much of that was real work. The gap is waiting. On a decision you kept deferring. On something external. On an evening that never came.
Most people measuring this for the first time are startled. Most of an item's life was spent untouched. If that's your picture, you don't have a capacity problem. You have a flow problem wearing a capacity costume.
Now put the signs side by side:
| What you see | Points to | The fix | What makes it worse |
|---|---|---|---|
| Items sit untouched for long stretches | Flow | Find the stall, usually a deferred decision | More evenings |
| Lots started, little finished | Flow | Limit work in progress | Starting something new to feel progress |
| A few items took far longer than the rest | Flow | Investigate each slow item individually | Looking only at the average |
| Work is steady, nothing stalls, there is simply too much | Capacity | Fewer commitments or a longer timeline | Squeezing in extra work |
| Pace is creeping later into the night | Either, and a warning | Diagnose now, before you stop | Treating it as a character test |
Read the first three rows. They look like laziness or lack of time. They are not. They are the shape of a process problem, and a process problem has process fixes.
Two archetypes, same complaint
Picture two solo operators who both say they are too slow. The first has a tidy board. Each item gets worked in a run, goes live, and the next begins. There are just more promises than evenings. That is capacity. Cut something.
The second has a board that looks busy. Plenty started. Several items untouched for weeks, one waiting on a choice about pricing she keeps postponing. Her evenings are fine. Her flow is clogged. Extra hours would vanish into the same clog.
Same sentence, opposite cures. Only the numbers show which one you are.
Check the three usual suspects first
When flow is poor, the cause is nearly always one of three. Check them in this order before reaching for anything exotic.
Too much in progress. Everything started, nothing finished, every session spent reloading context. Count what is open. It is almost always higher than you think. The remedy is covered in how to limit work in progress.
Stalled on a decision. The work is waiting on something you haven't decided. And it will wait indefinitely, because nobody is chasing you. This is the quiet killer of solo businesses. Nobody asks "have you decided yet?" so the answer is never forced. Look at the slowest items. How many were waiting on you to choose?
Items too large. A piece of work that can't be finished in the sessions you actually have will sit half done for weeks and rot. If your working time comes in short blocks, an item that needs a long unbroken run will never finish. Cut it down.
These three account for the large majority of flow problems, and all three are fixed by how you work rather than by working more. Only after they come up empty should you suspect capacity.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →What a genuine capacity problem looks like
It exists. Do not read this post and decide flow is always the culprit.
A capacity problem looks like this: work moves when you touch it, items rarely sit idle, your board is tidy, and the sum of what you've promised still exceeds the evenings you have. No stall to find. The arithmetic simply doesn't work.
That is a different conversation. Fewer commitments, or a longer timeline. Say no to something. Push a launch. Drop the thing that sounded good in January. It's less satisfying than a process hack, because it asks you to want less. But it is the honest fix, and it is cheaper than a burnout.
The surprising bit: you can have both. Often you do. A real capacity squeeze with a leaky process on top. In that case fix the flow first. It's free, it's quick, and you may discover the squeeze was smaller than it felt. The full decision about what to cut belongs in your monthly look, covered in how to review your work system every month.
Do the diagnosis once a month, not in a panic
The worst moment to diagnose is when you feel behind and tired. Your instinct is already shouting "more hours". Do it on a calm day, in the monthly hour, with the numbers in front of you.
- Look at the distribution and the tail, not the average.
- Investigate the slowest few items one by one. Blocked on a decision? Far too large? Started and abandoned?
- Check whether work in progress is rising.
- Work out how much of a typical item's life was not spent being worked on.
- Only then decide: flow fix, capacity fix, or both.
The tail does the heavy lifting. Averages hide everything that matters. The things that took five times longer than the rest are where the systemic problems live. Each one is individually investigable. How to read them is in how to read delivery data without averages.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →Change one thing, then look
Pick one fix. Make it. Wait long enough for the signal to move. Check.
If you limit work in progress and settle two stalled decisions in the same week, you won't know which one worked. And you'll carry both forever, because you can't justify dropping either. One change and a check, repeated, builds a real understanding of how you actually work. It also gives you something rarer than new habits: the confidence to drop the ones that don't help.
And if the data says capacity, believe it. That is not a failure of the method. It is the method doing its job. It stopped you spending a year looking for hours that were never the problem, or a year cramming more into hours that were already full.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
Can I have a capacity problem and a flow problem at the same time?
Yes, and it is common. Fix the flow first, because it costs nothing and may shrink the apparent capacity gap. Whatever remains after that is the real capacity question.
Why is capacity the default assumption?
Because without data, effort is the only hypothesis available. A feeling of being behind points straight at not working enough. That is why the usual response is to find more hours, and why it rarely helps.
What if I don't track time at all?
You do not need hours worked. You need start and finish dates for each item and a sense of how much of that gap was real work. Hours are on the list of things not to measure.
What is the quickest check I can do today?
Take your slowest recent item and ask what it was waiting on. A deferred decision, an external dependency, or being too large to finish in your sessions. That one answer often tells you which problem you have.
The full method, with the checklists, is in The Delivery Metrics Playbook, a free 21-page playbook.
How trapped are you, really?
Take the Corporate Suffocation Index, the free solopreneur readiness assessment.