Stop half-finished work piling up

Open your task list and count how many items you’ve started.

Not how many are on it. How many you’ve opened, done twenty minutes on, and left. For most people it’s somewhere between six and fifteen, and the list doesn’t show it, because the list only knows two states: there, or gone.

That’s a problem, and it’s not a discipline problem. Work in progress is expensive. Every started-and-abandoned task holds a little context in your head, and when you come back to it you pay the restart cost again. Eleven open things means you’re paying that cost eleven times, and finishing roughly none of them.

A checkbox can’t tell you this is happening. That’s what stages are for.

What a stage actually buys you

A stage is a column your task moves through. The value isn’t the categorising. It’s that once work has a middle, you can see the middle, and the middle is where things go wrong.

Two things become visible immediately:

How much you have in flight. If nine tasks sit in “Doing”, that’s the answer to why nothing shipped this week. It’s not obvious from a flat list. It’s unmissable in a column.

Where things stall. If tasks pile up in one specific stage every week, that stage is your bottleneck. Waiting on other people, usually. Or review. Once you can name it, you can do something about it. Chase earlier, or batch the reviews, or stop starting new work until the pile clears.

Setting it up

In Niyoxa, stages live under Workflow. Two rules before you start.

Keep it to four or fewer. Five stages means every task needs four decisions to cross the board, and you’ll stop moving them within a fortnight. A workflow you don’t update is worse than no workflow, because now you’re reading stale information.

Every stage must answer a question you actually ask. If you never wonder “what’s waiting on someone else?”, don’t build a Waiting stage.

For most personal work, this is enough:

Stage	What it means
Next	Committed to, not started
Doing	Started. Context is loaded.
Waiting	Blocked on someone or something else
Done	Finished

Note what’s missing. There’s no Backlog stage, because that’s what the Inbox is for, and mixing “someday” into the same board as “this week” makes the board unreadable. Anything you’re not committed to this week stays in the Inbox.

The Waiting stage does the most work

If you only add one stage to a plain list, add Waiting.

Blocked tasks are the ones that rot. They sit in your list looking like work you’re avoiding, so you feel bad every time you scan past them, and the guilt makes you scan past them faster. Meanwhile the actual next action, a two-line email to whoever’s blocking you, never gets done, because it’s not written down anywhere. The task says “finish the pricing page.” It doesn’t say “chase Sam.”

Pulling those into their own stage does two things. Your active list gets honest, because it now contains only work you can actually do. And Waiting becomes a list you can sweep. Once a week, go down it and chase everything on it. Ten minutes, and it’s usually the ten minutes that unblocks the most work.

Put the date you started waiting in the task. Four days is a chase. Three weeks is a decision about whether the thing is happening at all.

Cap what’s in Doing

This is the rule that changes behaviour, and it’s the one people resist.

Pick a number for how many tasks may sit in Doing at once. Three is right for most people working alone. When you want to start something new and Doing is full, you have to finish something or move it back to Next first.

It feels restrictive for about a week. Then you notice you’re finishing things.

The reason it works is that starting is pleasant and finishing is not. Starting is possibility. Finishing is the last 20% where all the annoying details live. Without a cap, you’ll drift toward starting forever, because every new task is more appealing than the tedious end of an old one. The cap removes the choice.

If you find yourself constantly at the cap with everything genuinely blocked, that’s a real signal — you don’t have too much work, you have a dependency problem. Which is a different fix, and at least now you know.

When this is overkill

If you finish most of what you start within a day, stages are ceremony. You’ll spend more time moving cards than you save. A flat list and a weekly review is fine, and adding a board on top of that will make things worse.

Stages earn their keep when work spans days, when other people block you, or when you already know you start more than you finish. If you counted at the top of this post and got a number under four, close this tab.

For everyone else: planning on Friday rather than Monday pairs well with this. Stages tell you what’s in flight; the Friday close-out tells you where each of those things stopped. Together that’s most of what you need to restart a task quickly.

Start with three stages and a cap of three in Doing. Adjust after a fortnight, once you can see where things actually pile up.