Rewrite vague tasks so your brain knows what to do
A vague task like "deal with insurance" gives your brain nothing to grab onto, so it gets skipped in favor of anything more concrete. Rewrite it as a single action with an object: "call Blue Cross about the denied claim." If the rewrite still contains "figure out" or "deal with," it needs one more pass before it is usable.
A vague task is a to-do item written as a goal rather than an action, which is why it keeps getting skipped.
What makes a task vague
A vague task usually has one of two shapes: it names a subject instead of an action ("taxes," "garage," "insurance"), or it names an outcome instead of a step ("get organized," "sort out the car"). Either way, your brain reads the task and has to do extra invisible work before it can act: figuring out what "deal with" actually means today. That invisible work is often the entire reason the task has not moved.
Words that are a warning sign
A few words show up constantly in vague tasks and are worth treating as a signal to rewrite on sight: "deal with," "handle," "sort out," "figure out," "look into." None of these are wrong to think, but none of them belong in the task itself, because each one hides the actual action inside a vaguer verb. "Sort out the car" could mean scheduling an oil change, calling the mechanic about a noise, or renewing the registration. Until one of those is named, "sort out" is doing the job of hiding the decision rather than making it.
A quick test
Read the task and ask: could someone who knows nothing about my situation do the first physical action from this sentence alone? "Call Blue Cross about the denied claim" passes. "Deal with insurance" does not, because a stranger would not know who to call or why.
Before and after
- Vague: "Car." Specific: "Book an oil change at the shop on Fifth Street."
- Vague: "Follow up with Sam." Specific: "Text Sam asking if Thursday at noon still works."
- Vague: "Fix the website." Specific: "Find why the contact form is not sending emails."
- Vague: "Plan the trip." Specific: "Decide between the two flight options already saved in the browser tabs."
Notice the specific versions are not longer descriptions of the same problem. They name one action and one object. That is the whole rewrite.
A worked example: the insurance claim
Say a claim got denied two months ago and "insurance" has sat on your list since, migrating from this week to next week without ever being touched. Applying the test: could a stranger act on "insurance"? No, not even close.
Rewrite pass one: "deal with the denied claim." Better, but "deal with" still hides a decision. Rewrite pass two: "call Blue Cross about the denied claim from March." Now a stranger could dial the number and know what to say when someone picks up. The task did not get any smaller in terms of effort required, the phone call still has to happen and might take twenty minutes, but the barrier to picking it up dropped because your brain no longer has to invent the plan first.
It is worth noticing what changed between the two rewrite passes. "Deal with the denied claim" still describes a category of action. "Call Blue Cross about the denied claim from March" describes a single, executable one. The second pass is not more detailed for its own sake, it is detailed exactly enough to remove the last open decision.
Writing it this way from the start
Rewriting old vague tasks is useful, but it is even more useful to write new tasks this way the moment you capture them, before vagueness has a chance to set in. The habit is simple: when a task comes to mind, name the action and the object before you name the subject. "Call Blue Cross about the March claim" instead of "insurance." Naming an action forces specificity in a way that naming a subject never does.
This connects closely to writing the actual opening move of a task rather than its label. Writing the opening move, not the task takes that idea further, and if the task keeps stalling even once it is specific, finding the smallest next step is the next thing to try.
Giving the specific version a real time to live in
Once a task is written specifically, it is easier to give it an actual schedule instead of leaving it to float. In Drifta, any task can carry an earliest start time, a deadline, or both, set on the task's own edit screen. Attaching "call Blue Cross about the March claim" to tomorrow at 10am gives the specific, rewritten task a real place to land, instead of sitting alongside a vague one that never gets a time at all. A vague task rarely gets a real time attached to it in the first place, since it is hard to schedule something you have not actually named yet, which is one more quiet reason vague tasks tend to drift for weeks while specific ones get done on schedule.
Common questions
What is wrong with a task like "organize garage"?
It names an area, not an action, so there is no first move contained in it. Your brain has to invent the action itself before starting, which is extra work most vague tasks quietly require without you noticing.
How specific does a task need to be?
Specific enough that a stranger could do the literal first physical action without asking you a question. If someone would need to ask "which part" or "starting where," it is not specific enough yet.
Isn't rewriting every task extra work I do not have time for?
It takes longer to write "call the vet to reschedule Milo's checkup" than "vet," but it saves the much larger cost of a task sitting untouched for two weeks because it was never clear what doing it meant.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.