What Is Cycle Time for a Solopreneur? Define It Once
What is cycle time for a solopreneur? The days from real start to genuinely done. Pick both ends once, write them down, and watch the spread, not the average.
What is cycle time for a solopreneur? It is how long a piece of work takes from the moment it actually starts to the moment it is genuinely done. The number matters less than your two definitions. Choose them once, write them down, and never quietly change them.
What is cycle time for a solopreneur, in plain words?
Start. Finish. The gap between them.
That is it. A piece of work begins, it ends, and you count the days in between. Cycle time is the oldest, dullest, most useful number in delivery. It is also the one you should measure first.
Why first? Because it is a fact about your system. How many things you finished is a fact about how you sliced the work. Slice finer and the count goes up. Nothing improved. Cycle time is harder to fake, because the clock runs whether you like it or not.
If you only take one thing from this post, take this. The number is not the point. The two definitions behind it are the point.
The definition is the answer
Here is the catch nobody tells you. Cycle time has no single correct version. The definition you choose decides the number you get.
When does the clock start? When you decide to do the thing? When you add it to the board? When you first open the editor?
When does it stop? When it works on your machine? When it is deployed? When a real user can actually use it?
Pick any answer. There is no universally right one. There is only a consistent one. But look at how much the answer moves:
| Choice | Clock starts or stops when | What it flatters | What it hides |
|---|---|---|---|
| Early start | You decide to do it | Nothing. It counts the waiting. | Nothing, but the number looks long, because ideas that sat there count too |
| Late start | You first open the editor | A short number | All the time the idea waited its turn |
| Early finish | It works locally | A short number | Everything between "works for me" and live |
| Honest finish | A real user can use it | Nothing | Nothing. It is the one that matches what you sell. |
Look at the pattern. The late start and the early finish both produce a lovely short number. Both quietly delete the part of the journey where work sits. And the sitting is exactly what you are trying to find.
My advice, and it is only advice: lean towards the honest ends. Start when you actually begin. Finish when it reaches a user. Your definition of done should match what reaches a customer, not what feels finished to you at ten at night.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →Write it down. Seriously.
Say you sell a productised service and you track each client delivery as one item. Last quarter you counted the clock from the signed agreement. This quarter, without thinking, you count from the first call. The line drops. You feel brilliant. Nothing changed except the date you picked. That is the whole risk, and it is invisible unless the definition is on paper.
You will not remember.
The version of you in three months will define "started" differently. Slightly. Without noticing. Then the trend will look strange, a line that bends for no reason, and you'll waste an evening hunting a cause that is just your own shifting definition.
Two sentences on a page. "The clock starts when I first work on it. It stops when a customer can use it." Done. Tape it next to the board.
A good test: could you produce the same number from the same data in three months? If not, the definition is not written down well enough. Another test: do you know what each status on your board is meant to mean? A column called "in progress" that holds both live work and things you quietly gave up on will wreck the number. Both tests sit in the first checklist of the guide.
Why a good average can still hurt you
Now the part most people get wrong. They compute the average, feel fine or feel bad, and move on.
The average is nearly useless for planning. What you actually want to know is: how long will this probably take, in the bad case? That answer lives in the spread.
Most things finish in a few evenings. Some take three weeks. The three-week ones are what break your plans. An average sands them down into a respectable middle figure that describes nothing you ever experienced.
So look at the shape. Which items sit at the short end? Which ones sit way out at the long end? A tight spread with a mediocre average beats a good average with a long tail. You can plan around the first. The second ambushes you.
The tail has its own post: how to read delivery data without averages. For now, remember one rule. When you open the numbers, go to the slowest few items first.
What cycle time tells you that you cannot see
It shows the drag.
Most of an item's life is not building. It is waiting. On a decision you keep deferring. On something external. On an evening you never got. From inside, you can't see it. You were busy with something else, nothing looked stuck, and the time melted into "it took three weeks".
Put the numbers next to each other. Time actually worked on it. Time from start to done. The gap is the drag. People who see this for the first time are often startled. Most of the life of an item was spent not being worked on.
That gap is the cheapest fix you have. No new tool. No new skill. A decision you've been avoiding, or something you started too early, or a task too large to finish in the sessions you actually have.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →How to start, this week
Keep it small. Comprehensive instrumentation is how measurement becomes a project and then an abandoned spreadsheet.
- Write the two definitions. Start, finish.
- Make sure every item on your board has a start date and a finish date. Not a perfect system. A date.
- Run it for at least a month before you change anything. You need a baseline.
- Learn your ordinary variation, so you can recognise a normal bad week when it comes.
- Record where you started, so any improvement can be checked.
Then sanity-check it. Does the data match how the month felt? If it doesn't, the instrument is probably wrong. Work happening off the board. A status that meant two things. That is a bug report about your measuring, not news about your talent.
What cycle time is not
It is not a score. Not a comparison with anyone else's. A friend's cycle time on a different kind of work tells you nothing.
It is not a target either. The second you say "my cycle time should be five days", you have told yourself to make the number look good. There is always a way to do that without improving anything. Items get split smaller. Done gets redefined. The line goes down and the business doesn't move. Keep it a baseline and a trend. Did the number shift after I changed something? That's all it's for.
And never read it alone. Next to the speed number, put a quality number. If cycle time falls and the amount of redoing rises, you did not get faster. You moved work into the future. That pairing is part of why delivery metrics are worth it at all.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →Cycle time and what is in progress
One more link, because it changes what you do on Monday.
The more things you have in flight, the longer each one takes. More context switching, more reloading of what you were thinking. When your working session is ninety minutes after dinner, that cost is brutal. So if your cycle time is long, the first suspect is not your speed. It is how many things you started and haven't finished. Limiting that costs nothing and shows up within a fortnight. The how-to is in how to limit work in progress.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
What is a good cycle time?
There is no good number to aim at. A target only invites gaming. What matters is your own baseline and whether it moves, in the right direction, after you change how you work.
Should the clock start when I decide to do something or when I begin?
Either is fine if you apply it every time. A start at the moment you begin working is easier to defend. What breaks the measure is changing your mind halfway through the year.
Why not just count tasks finished per week?
Because a count describes how you sliced the work, and slicing adjusts itself the moment it is counted. Cycle time describes how long work actually took to flow through.
How long before the number tells me anything?
Collect at least a month before changing anything. You need a baseline and a feel for ordinary variation, so you can tell a normal bad week from a real change.
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.