You sent the email on the 3rd. It's now the 22nd.
Nothing has come back, and in the meantime the project it belongs to hasn't moved, which is fair enough, because it can't. You're waiting. That's the accurate description, and if anyone asks, it's the one you'll give.
It's also, by about the second week, no longer the whole truth.
The two halves of waiting
There are always two things going on when a goal is blocked, and they get treated as one.
The first is the dependency itself. Someone owes you a file, a decision, a signature, and until it arrives you cannot do the work. That's real, and no amount of effort on your side changes it.
The second is the chasing, which is entirely yours. Following up, escalating, setting a date after which you go around the problem — none of that is blocked by anything. It is available to you every single day of the wait.
What happens is that the first quietly gives cover to the second. Because the work is genuinely impossible, the chasing stops feeling like something you're neglecting — it gets filed under the same heading as the work, and the whole goal moves into a category marked not my move. Two weeks later the honest description isn't that you're waiting for Priya. It's that neither of you has done anything, and only one of you knows about it.
Why chasing is the bit that gets dropped
Chasing is a small, unpleasant task, and small unpleasant tasks lose to almost everything.
It's socially awkward, and the awkwardness is real rather than imagined. You're implying someone hasn't done something, which is true but rude to notice. There's an easy story available — they're probably busy, it's probably coming — and that story is comfortable, costs nothing, and has the advantage of usually being correct.
It's also invisible when skipped. Nobody sees an unsent follow-up. There's no output, no failure, no consequence today. And it produces nothing when done: you send the email and the thing you wanted still hasn't arrived, so the reward for chasing is precisely zero at the moment of chasing.
Meanwhile, the goal has dropped out of your attention entirely, because attention follows action, and there's no action. This is the quiet part. You didn't decide to stop chasing. You stopped thinking about the goal at all, and the chasing went with it.
There's a further stage, and it's the one worth watching for. After a few weeks, a stalled dependency starts to become convenient. The goal was going to require something difficult of you once the file arrived, and while it hasn't, you're excused. Nobody admits to this, and most people don't consciously experience it, but you can detect it in a small reluctance to chase harder than politeness requires — a sense that the follow-up can wait until next week, applied every week. If chasing feels disproportionately unappealing for something that takes two minutes, it's worth asking what arrives when the blocker clears.
Writing the blocker down properly
The fix is a sentence, and it works because of what it forces you to be specific about.
Not waiting on the surveyor. Instead: waiting on the surveyor for the valuation report, requested 3 August, said it would be a week.
Three things become visible immediately that were comfortably vague before.
Whether it's reasonable, which you cannot judge without a date. Eight weeks for a planning decision is the process working. Nineteen days for a report promised in a week is not the process; it's something that has slipped and stayed slipped.
Whether you actually asked. A surprising proportion of blockers turn out never to have been requested — the goal has been waiting on an email nobody sent, sometimes for months, and the moment you try to write down when you asked, you discover you didn't.
And what the next action is, which is the important one. With a name and a date on the page, wait stops being a valid answer. The next action becomes chase on Thursday, which is a real task that can be done and finished.
How to chase without being unbearable
Four escalations, in order, and most things resolve at the first.
The gentle nudge, after whatever interval was promised plus a few days. Short, no reproach, and offer a reason it might not have happened: did this get lost? happy to resend if easier. This clears the majority, because the majority genuinely is forgetfulness rather than reluctance.
The second one, a week later, adds a consequence — not a threat, just information. I'm holding the schedule for this; if it's going to be after the 30th let me know and I'll plan around it. People respond to the shape of someone else's plan far more reliably than to a request.
Third, change the channel. An email ignored twice will be ignored a third time. Ring them, or catch them where they are. This resolves a surprising number of things that two weeks of email did not.
Fourth, route around. Ask someone else, find another surveyor, do the version of the work that doesn't need the thing. This is the one people skip, and it's often available much earlier than it feels — the dependency you've been treating as fixed is frequently just the most convenient of several options.
The decision to make at the start isn't which of these to use. It's the date at which you move to the next one, written down at the same time as the blocker.
The case for leaving people alone
There's a decent argument against most of this, and it deserves stating.
Chasing has costs that don't appear in your project. Relationships aren't only throughput, and someone who follows up on day four of a favour teaches people to avoid doing them favours. Plenty of the things you're waiting on are goodwill — a friend reviewing a draft, a colleague doing something outside their job — and the correct interval for those is much longer than for a paid supplier, sometimes indefinite.
There's also the genuine case for patience. Some processes take the time they take, and a person who chases a statutory eight-week decision in week three has simply announced they don't know how the thing works.
The distinction that matters isn't how long it's been. It's what was agreed. A supplier who said a week is late at ten days. A friend who said sure, sometime is never late, and treating them as though they were is a mistake that costs you more than the draft is worth. Write down which kind you're dealing with when you write down the blocker, and half of this resolves itself.
Nineteen days, two goals
Two blocked goals in the same list, both nineteen days quiet.
Flat revaluation — the surveyor was asked on the 3rd and said a week. Nineteen days is twelve days past what was agreed, so this isn't waiting any more, it's a lapse. One email today, and a date on Friday at which a different surveyor gets called. Total cost: four minutes.
Feedback on the manuscript — sent to a friend who reads slowly and offered no deadline, because there wasn't one to offer. Nineteen days is nothing. The correct action is none, and the correct feeling is none either. It's marked blocked, the note says no date agreed, don't chase before October, and it can sit there quietly for another six weeks without costing anyone anything.
Same silence, same number, opposite responses. The number told you to look. What was written underneath it told you what to do.
That's the whole mechanism. goaldrift won't guess which of your silences are yours — it can't, and an app that tried would be wrong constantly and insufferable about it. It asks for a name and a date, and then it shows you how long it's been. The judgement stays yours; the number just makes sure the question gets asked before it's a year old.
Related: Stalled vs blocked: the difference that changes what you do next · The anatomy of a stuck goal · Logging beats tracking
Share: