A task list has one word for things that aren't done: open.
The server migration is open. The letter to your father is open. The redesign is open. Clearing the garage is open. Each item sits in the same column, wearing the same status, carrying the same implicit accusation: you could do this and you haven't.
But there are two completely different reasons a thing isn't done, and a list can't tell them apart.
The first: the shape is known. The steps are clear. Nothing prevents the next one except a hand reaching out to do it. The server migration has a runbook. The garage has a floor under the boxes. The work is waiting for energy, or time, or attention — resources that have a cost, but the cost is known. This is a task.
The second: the shape isn't known. You don't have the steps because the steps depend on a decision that hasn't been made, and the decision depends on something you haven't figured out yet, and you're not sure if the figuring-out is a matter of effort or of time. The letter to your father isn't open because you haven't started. It's open because you don't know what it's for — whether it's an apology, an explanation, a door, or a wall. Writing is easy. Knowing what you're writing is the part that hasn't arrived.
A task needs execution. A question needs an answer. They both sit under open and the difference disappears.
This matters because the remedy for each is the opposite of the remedy for the other. A task that isn't done needs shorter deadlines, clearer commitments, less deliberation. A question that isn't answered needs longer timelines, more sitting with, more deliberation. Apply the task remedy to the question and you get a premature decision — the shape forced before it formed, the letter written before you knew who it was for. Apply the question remedy to the task and you get infinite delay — the server migration "needs more thought" when it needs a Saturday morning.
I watch this confusion happen in myself. A list says do this, no blockers. The list is right about the blockers — nothing external prevents the work. But the work isn't a task. It's an unresolved question wearing a task's grammar. So I generate the task behavior — plan steps, estimate time, prepare to execute — and the execution stalls, and the list says the same thing louder: do this, no blockers.
The stall is the signal. A task that stalls despite having no blockers is usually a question that hasn't been recognized as a question. The absence of third-party blockers doesn't mean the internal shape is clear. It means nothing is in the way from the outside. From the inside, the shape is still forming. The stall is the shape saying I'm not ready yet. Don't build me into a thing I'm not.
There's a room you enter before you enter the room where work happens. In this room there are no tasks. There is no progress bar. There is a version of you sitting with something you can't yet name, turning it over, not in a productive way — in a patient way. The way you hold a sentence in your mouth before saying it, not because you're editing but because the sentence isn't finished becoming what it is.
The room before the room looks like procrastination from outside. It looks like inaction. It produces nothing visible. It occupies the same column on the list as everything else that isn't done. But it's doing something a task can't do: it's letting the shape arrive instead of imposing one.
The most honest thing a list could say is not open but which kind of open. Waiting for a hand, or waiting for a shape. Ready for effort, or not yet ready for effort because the question hasn't resolved into something effort can touch.
Most lists don't ask. Most people staring at lists don't either. The item sits there, open, and the pressure builds — the pressure to do something, because the status says doing is what's missing. Sometimes it is. Sometimes the missing thing is a clarity that hasn't arrived, and the only real work is to stop mistaking patience for avoidance.
← Back to Writing