Review Your Work System Every Month:A One-Hour Agenda
How to review your work system every month: one hour, one agenda, one change. Read the slow tail, diagnose, check last month's fix and protect your pace.
To review your work system every month, book one hour on a day you aren't discouraged and run four steps: read the slowest items and the quality signal, diagnose against the three usual causes, make exactly one change, and check last month's change. Review the system, not the week.
How to review your work system every month
Most solo operators review their business. Revenue, leads, the pipeline. Fair enough.
Almost none review the machine that produces the work. So the same stall happens in March, again in April, again in May, and each time it feels like fresh bad luck.
It isn't bad luck. It's a process nobody inspects.
A monthly habit to review your work system fixes that. One hour. Same slot every month. A fixed agenda so you don't wander. And one rule that makes everything else work: you're reviewing the system, not the week.
That difference sounds small. It's the whole thing.
System, not week
Review the week and you get a list of incidents. Tuesday was a mess. Thursday went well. A client email derailed Friday. Interesting, forgettable, and it changes nothing.
Review the system and you ask different questions. What slowed me down repeatedly? Where did work stall? What did I start and not finish? What did I have to redo, and why?
Incidents produce a story. Patterns produce a change.
That's the test for whether your review is any good. At the end, is there one concrete change to how you work? If you finished with a mood and a vague resolution, you reviewed the week.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →Review your work system: set it up so you'll do it
A review you skip is worth nothing. So make it hard to skip.
- Same slot every month. Put it in the calendar like a client call. You don't cancel client calls.
- A day you're not already low. Reading numbers on a bad day turns them into a verdict. Pick a calm one.
- Four numbers or fewer. Each with a reason to be there. If one hasn't informed a decision in two months, drop it.
- The rule written down. These numbers describe the work, not your worth. Put it at the top of the page you review from.
And before the first review, you need at least a month of data to compare against. Otherwise you can't tell a normal bad week from a real one. A baseline is what makes next month's number mean anything.
The hour, step by step
| Step | What you do | The question you answer | Rough time |
|---|---|---|---|
| Read | Look at the spread and the slowest few items, work in progress and quality beside speed | What actually happened? | Fifteen minutes |
| Diagnose | Check too much open, stalled decisions, items too large | Why did the slow ones stall? | Fifteen minutes |
| Check | Look at last month's change against the number it should have moved | Did it work? | Ten minutes |
| Act | Choose exactly one change, and name the number it should move | What do I do differently? | Ten minutes |
| Protect | Look at the pace signals and ask whether you're covering a problem with effort | Is this sustainable? | Ten minutes |
Treat the times as a guide to how you review your work system. The order matters more than the clock. You read before you diagnose, and you check last month before you invent this month's change.
Read: the tail, never the average
Start with what finished. Look at the shape, not the middle. Then pick the slowest few and give each one a sentence: what was it waiting for?
Check whether work in progress is rising. Check the quality signal beside the speed signal. If you shipped more and redid more, you didn't get faster. You moved work into the future.
If this step feels unfamiliar, how to read delivery data without averages goes into it properly.
Diagnose: three usual causes first
Don't reach for anything exotic. When flow is poor, it is nearly always one of three:
- Too much in progress. Everything started, nothing finished, every session spent reloading context.
- Stalled on a decision. The work is waiting for something you haven't decided, and nobody is chasing you.
- Items too large. Work that can't be finished in the sessions you really have sits half-done and rots.
Also ask how much of a typical item's life was spent not being worked on. That number surprises people. And before you decide on a fix, separate a capacity problem from a flow problem, because they need opposite answers. The default assumption, absent data, is that you need more hours. It's usually wrong.
Check: did last month's change work?
This is the step almost everyone skips, and it's the step that makes you better rather than merely different.
Last month you picked one change and named the number it should move. Look at that number. Did it move?
If yes, keep the change. If no, drop it. Not "let's give it another month". Drop it. Practices pile up when nothing is ever removed, and a year later you're following rituals you can't justify.
Being willing to cancel your own idea is rarer and more valuable than coming up with new ones.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Act: one change only
Pick one. Write down what number should move and roughly when.
Four changes at once teaches you nothing. If the number moves, you won't know which change did it. If it doesn't, you won't know which to blame. You'll be left with a bundle of habits and no evidence for any of them.
One change, then check. Repeat for a year, and you'll understand how you actually work in a way no productivity book can give you.
Examples of a good single change: cap how many things you keep open at once; schedule a fixed slot for the decisions you keep deferring; cut anything that can't finish in one run of your real sessions. Pick the one the data points at. If the data points at open work, how to limit work in progress is the place to begin.
Protect: the part you will be tempted to skip
Finish by looking at pace. Are sessions creeping later? Is open work rising without anything finishing? Is the tail lengthening?
These show whether you're absorbing a system problem with personal effort. That absorption is finite, and when it ends it doesn't end gently.
Two questions to close on. First: has a bad month been read as information about the system, not about me? Second: has anything here become a reason to work later? If the answer to the second is yes, you've turned a tool for finding blockages into a way of finding more hours, and you should stop and rethink. The signals themselves are covered in how to spot burnout in your own work data.
A review in motion
Say you run a small training business on your own. You open the review and the slowest item is a course update that sat for most of the month.
You ask what it was waiting for. Not the content. A decision about how to structure the final module, which you kept meaning to make. Meanwhile three other things were open, so every time you came back to it you had to remember where you'd got to.
Diagnosis: stalled on a decision, plus too much open. Last month's change was to cap open work. You check: did the open count fall? A little. Did the slow tail shrink? Not yet. So you keep the cap and add one thing, a fixed slot each week to make pending decisions. Just one.
That took ten minutes, and it's a better use of an hour than any amount of staring at a chart. It also had nothing to do with how hard you worked.
When the data and your month disagree
It will happen. The numbers say calm, and the month felt like a scramble. Or the reverse.
Don't pick a side. Treat the mismatch as a bug report about your measuring. Work happening outside the system. Statuses that meant different things on different weeks. Something not moved on the board.
Fix the instrument. Don't dismiss your experience, and don't dismiss the data. If you decide it's all nonsense, you stop trusting the review, and then you stop doing it.
Free guide · 21 pagesMeasure the system, not yourself.The Delivery Metrics Playbook: is the machine healthy, without the stick.Get the free guide →Keep it small or it dies
The most common way this habit ends isn't a dramatic failure. It's drift. The review grows. More numbers. A fancier layout. Then it takes half a day, you skip a month, and the thing is quietly gone.
Keep to an hour. Four numbers. One change. If a review ever takes much longer than that, you added something you didn't need, so cut it.
Value lives in the reading, not the collecting.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
How long does it take to review your work system each month?
About an hour, in the same slot each month, on a day you aren't already discouraged. If it starts to run long, you have added numbers or steps that you do not need.
What should I review?
The system, not the week. Ask what slowed you down repeatedly, where work stalled, what you started and did not finish, and what you had to redo and why.
How many changes should I make each month?
Exactly one. Name the number it should move and roughly when, then check it next month. Several changes at once leave you with habits you can't justify.
What if I have no data yet?
Collect at least a month before the first real review, so you have a baseline. Until then you cannot tell an ordinary bad week from a genuine problem. Then review your work system with that baseline in hand.
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.