How to Limit Work in Progress as a Solopreneur
How to limit work in progress as a solopreneur: count what is started and unfinished, cap it, and finish before you start. It is free and shows in a fortnight.
To limit work in progress as a solopreneur, count everything you have started and not finished, then set a ceiling and finish something before you begin anything new. It costs nothing, and cycle time shortens within a fortnight. If you measure only one thing, measure this.
Why you should limit work in progress as a solopreneur before anything else
You are not slow. You are spread thin.
That is the usual diagnosis. Not too few hours. Too many open doors. Everything started, nothing finished, and every session spent working out where you left off.
Work in progress is the number of things you have begun and not completed. It is the least glamorous signal you can track. It is also the most powerful, and the reason is mechanical. More things in flight means more context switching. Context switching is expensive when your working session is ninety minutes after dinner. Every time you sit down, the first stretch goes on remembering.
So cycle time stretches. Not because you got worse. Because the system got heavier.
Limiting it is the highest-leverage change most solo builders can make. It costs nothing. No tool, no course, no subscription. And you see a result inside a fortnight.
Count it first. You'll be annoyed.
Do this before you read another word. Open your board, your notes, your head. List everything that has been started and is not done.
Include the half-built feature. The client onboarding you redesigned and left. The article at the draft stage. The integration you opened "just to look at". The automation that mostly works.
Then look at the total. It is almost always higher than you believe. That is not a character flaw. Starting is rewarding. Each new thing arrives with a rush of possibility, and finishing arrives with a pile of dull details. So you start.
Make it a number, not just a list. A list can sprawl forever. A number can be compared to last month.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →Spot what too much in progress looks like
| What you notice | What is probably happening | The move |
|---|---|---|
| Busy all week, nothing shipped | Effort split across too many things | Pick the closest to done and finish it |
| Every session starts with "where was I?" | Context reload eating your ninety minutes | Cut the number of open items before the next session |
| Old items on the board nobody touches | Started, abandoned, never admitted | Finish, shrink or delete. Do not leave it half alive. |
| Cycle time creeping up | Queue lengthening faster than you finish | Stop starting. Only finish. |
| The pile rises while little closes | You are absorbing a system problem with effort | Treat it as an early warning, not a work ethic test |
That last row matters most when you limit work in progress. Work in progress rising while nothing finishes is one of the signs that you are carrying a system problem on personal effort. That carrying is finite. When it ends, it does not end gradually.
Why it feels productive and isn't
Ten things moving a little feels like momentum. It isn't. Nothing reaches a customer until it is done, and a business only earns from done. Work in progress is cost with no return yet.
Say you run a small subscription product and a content engine side by side. You are mid-way through a new pricing page, a rebuilt onboarding email series and a fix for a flaky export. Each gets one evening a week. All three take a month. Finish them one at a time and the first lands in a week, the second in two, the third in three. Same hours. Earlier results. Less reloading. That is the whole argument.
Set a ceiling and keep it
A limit is a rule with teeth. "I will have no more than this many things open." Then you obey it.
How many? The guide does not hand you a magic figure, and I won't invent one. Start lower than feels comfortable, because your instinct has been wrong for months. You can raise it later if the data says you have room. You will almost never need to.
The rule that follows is simple and a little brutal. When you are at the ceiling, you may not start something new. You must finish something, or consciously drop something, first. Not "pause". Drop.
This is the part that feels wrong. A new idea arrives, and it is a good one, and you are told to write it down and wait. Yes. Write it down, put it in a list that is not "in progress", and keep going. The idea will survive a fortnight. Your focus might not.
Finish before you start: how to do it on Monday
Plain steps. Do them in order.
- List every open item. Count it. Write the number down as your baseline.
- Sort by distance to done. Closest first.
- Pick the ceiling. Lower than you want.
- Choose what to finish, what to shrink and what to drop. Everything over the ceiling goes to a waiting list.
- Finish the closest item before you begin anything new.
- Look at the number again in a fortnight, and at your cycle time beside it.
Be ruthless about step four. Half-finished things are not assets. They are inventory, and inventory has a carrying cost. It occupies your head and lengthens everything else. If something has gone cold and you don't know when you'll return to it, dropping it is the productive move.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →The big items are secret work in progress
One of the three usual causes of poor flow is items that are too large. A piece of work that cannot be finished in the sessions you actually have will sit half done for weeks and rot.
So a limit alone isn't enough. If every item is huge, your ceiling gets stuffed with three monsters and nothing moves. Cut the work so a piece can finish inside the evenings you realistically have. Then the ceiling does its job.
The three usual causes together: too much in progress, work stalled on a decision, items too large. Check them in that order every month. They explain the large majority of flow problems, and every one is fixable by how you work, not by working more.
What about work that waits on someone else?
Some things stall for reasons outside you. A supplier, a platform review, a reply you are waiting for. Count them honestly, but do not let them hide inside the number as permanent residents. If an item has waited so long you have forgotten why, it is not in progress. It is stuck. Either chase it, park it visibly, or let it go. Pretending it is moving is how the count creeps up while nothing closes.
What you should see when you limit work in progress
Within a fortnight, cycle time should start to shorten. Not because you are working harder. Because less is competing for the same ninety minutes.
If it does not move, you have learned something. Maybe the stall is a decision you've been dodging. Maybe the items are too large. Maybe the real problem is capacity, not flow. The way to tell is in how to tell a capacity problem from a flow problem.
Change one thing, then check. That is the discipline. Limit work in progress, wait long enough for the signal to move, and look. Do not also change your tools, your planning ritual and your calendar that same week. You will learn nothing and you will keep practices you can't justify. The full routine for that monthly look is in how to review your work system every month.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →Limit work in progress: the honest limits
A limit will not fix everything. It will not fix a bad idea. It will not fix a week with no evenings in it.
It also should not become a stick. If you break your own ceiling on a rough week, that is data about the system, not a verdict on you. Ask why the ceiling failed. Was it too high? Did something urgent land? Did you have a decision you couldn't make? Then adjust the system, not your self-opinion.
And keep the number visible. Work in progress shown as a number, not just a list, is part of the instrumentation checklist for a reason. You cannot manage what you only feel. The wider picture of why the metrics are worth keeping at all is in are delivery metrics worth it for a solopreneur.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
What counts as work in progress?
Anything you have started and not finished. Half-built features, drafts, abandoned experiments, tasks waiting on a decision. If it occupies your head and isn't done, it counts, whether or not it appears on your board.
What limit should I set when I limit work in progress?
Lower than feels comfortable. The right figure is the one that lets things finish in the sessions you actually have. Start low, watch cycle time, and raise it only if the data shows you have room.
What do I do with new ideas while I'm at the limit?
Write them on a waiting list that is not in progress. A good idea will still be good in a fortnight. Starting it now just makes everything else slower.
How fast will I see a result?
Usually within a fortnight, in a shorter cycle time. If nothing moves, check the other two usual causes: work stalled on a decision, and items too large to finish in your sessions.
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.