Stalled vs blocked: the difference that changes what you do next

Two goals, both untouched for twelve days.

The first is a report you're meant to be writing. Nobody is stopping you. You've opened the document twice and closed it twice.

The second is a planning application. You submitted it twelve days ago. The council will respond when the council responds.

Every tracking app treats those the same way. Twelve days is twelve days, so either both get a red mark or neither does. But they're opposite conditions. One is a goal you're avoiding. The other is proceeding exactly as it should, in silence, without you.

What happens when you can't tell them apart

Guilt gets spread evenly, and stops meaning anything. If the planning application is scolding you the same way the report is, the marks on your list are noise. You learn to disregard them — and once you're disregarding them, you're disregarding the report too. A system that flags everything flags nothing, and the cost is paid by the one goal that genuinely needed flagging.

Then there's the expensive one. Avoidance gets somewhere to hide. I'm waiting to hear back is the most comfortable sentence in project work, and it's very often true — just not as true as it was. You were waiting. Then you stopped chasing, the waiting became mutual, and it has now been three weeks in which the honest description is that nobody is doing anything. If your system can't distinguish waiting from avoiding, neither can you, and the goals you're avoiding will present themselves as the goals you're waiting on.

The distinction, and the obligation

Stalled means the next move is yours and you haven't made it. The silence belongs to you.

Blocked means the next move belongs to someone or something else. The silence isn't yours.

One question separates them. If you sat down right now with a free hour, could you move this forward? Yes, and you haven't — stalled. No, genuinely no — blocked.

Blocked is not a resting state, and it's the most abusable label on the list, because it's the only one carrying no fault. Anything with no fault attached will attract goals that don't deserve it.

So marking something blocked comes with a requirement: write down what you're waiting for and who owes it. Not waiting on the council but waiting on the council's decision, submitted 14 July, statutory period is eight weeks. Not waiting on Priya but waiting on Priya for the signed build, asked on the 3rd.

Written in that form, three things become visible that were comfortably vague before.

Whether it's reasonable. Eight weeks for a planning decision is the process. Eleven days for a colleague to send a file is not the process, it's something you've let slide.

Whether you've actually asked. A surprising number of blockers turn out to be things nobody has ever been asked for. The goal has been waiting on a request that was never sent.

And what chasing looks like. Once there's a name and a date, the next action isn't wait. It's chase on Thursday if it hasn't arrived. You can't do the work, but you can always do the chasing — blocked never means there's nothing to do. It means the thing to do is smaller and more annoying than the work, and it's usually one email.

Three that look blocked and aren't

Waiting for feedback on something you haven't sent. The draft is finished, sitting in a folder, and you're waiting on a reader who doesn't know they're a reader. That's fear wearing the dependency's clothes, and the next move is entirely yours and takes ninety seconds.

Waiting for the right time. No named person, no date, no request outstanding. The block is a season or a mood. That's ambiguity or capacity, and calling it blocked files it somewhere you'll stop looking.

Waiting on a reply from three weeks ago, chased once. This genuinely was blocked. It became stalled at roughly the point you decided not to send the second email. The dependency is real and so is the avoidance, and the avoidance is now the larger part.

The pattern in all three is the same: a real dependency at the start, and a label that outlives the reason for it. Anything blocked for more than a fortnight is worth re-testing.

The argument for not bothering

There's a reasonable objection here, which is that this is bookkeeping. Two states, a written blocker, a chase date — for a personal goal list, that's a lot of admin to avoid the mild indignity of a red mark you could simply ignore.

It's fair for small things. If your list is four goals and you can hold the whole state of each one in your head, the distinction adds ceremony and nothing else. Nobody needs to formally document that they're waiting on a plumber.

Where it earns its place is at the point your list outgrows your memory, which happens sooner than people expect — somewhere around eight or nine live goals, or any goal with more than two people in it. Past that, you stop being able to recall which silences were yours, and the default assumption becomes I'm probably waiting on someone, because that's the assumption that feels best. The bookkeeping isn't there to organise the list. It's there to stop you lying to yourself at the exact moment lying is most attractive.

The other honest limitation: the distinction only works if you're truthful when you mark it. A person determined to avoid a report can mark it blocked and invent a dependency. No system fixes that. What it does do is make the lie explicit — you have to type a name and a date — and most people won't.

Twelve days each, three months apart

The report and the planning application, followed through.

The report goes untouched for twelve days, then nineteen, then twenty-six. It's stalled the whole time and never marked anything, because there's no one to name. At twenty-six days it's at the top of the list, which is where it finally gets looked at properly, and the diagnosis takes about forty seconds: the next step is clear, nobody's blocking, and the thought of dropping it is horrible. Fear, then. The move isn't to write the report. It's to open it and add one sentence to the section on costs, which takes four minutes and sets the counter to zero.

The planning application is marked blocked on the day it's submitted, with the line council decision, submitted 14 July, eight-week statutory period. It then sits there for seven weeks doing nothing and costing nothing, because the silence has a reason attached and the reason is reasonable. In the eighth week the date does the work — the blocker's own timeline says the period is up, so the next action appears on its own: ring the planning office.

Same twelve days at the start. One needed a diagnosis, the other needed a calendar. Neither needed guilt, and only one of them was ever about you.

Put plainly: a stalled goal is asking a diagnostic question. Why hasn't the next move happened? Ambiguity, fear, wrong goal, no capacity. Answer it and the goal moves.

A blocked goal asks something far simpler: is it time to chase? No introspection needed. Look at the date, decide, send the email or don't.

That's why they have to be separated. They aren't different intensities of stuck — they're different questions. Mix them and you'll spend energy interrogating goals that need a follow-up email, and send follow-up emails about goals that need you to be honest with yourself.

How goaldrift handles it

Days-since drives the states: nought to three days moving, four to seven easing off, eight or more stalled and sitting at the top.

Blocked sits outside that. Mark a goal blocked and it stops being described as your silence — the app shows what you're waiting on and how long it's been, which is the number that matters once someone else has the ball. Clear the blocker and the goal returns to zero days quiet, exactly as if you'd written a note, because clearing a blocker is real progress and should be recorded as such.

You mark it yourself. That's deliberate. An app that guessed which of your silences were your fault would be wrong constantly and insufferable about it. The claim is yours to make. It only asks you to say who you're waiting on and since when, which is the part that keeps the label honest.

---

Related: The anatomy of a stuck goal · Quitting is a skill · Logging beats tracking