Task avoidance isn't a planning problem

I keep a return package by my front door. It’s been there eleven days. The label is printed, the box is taped shut, and the post office is four minutes away on a route I walk twice a week anyway. Every time I pass it I register the same flat thought — I’ll take it Thursday — and then Thursday arrives and the box is still there, slightly more embarrassing each time I step over it.

That’s task avoidance, and it’s the kind of thing people search for at two in the morning, half diagnosing themselves. There’s a lot of good writing on why it happens: the task carries some emotional charge — boredom, mild dread, the vague sense that starting requires more of you than the task actually deserves — and the brain routes around it the same way it routes around any source of discomfort. The explanations are solid. What’s missing is the mechanism of the fix, because the fix everyone reaches for doesn’t actually fix it.

Why decomposition stalls

The standard advice is to break the task down. Turn “deal with the package” into a list: find the receipt, confirm the return window, repackage if needed, walk it over. This is supposed to lower the barrier, and on paper it does — each line is smaller than the whole.

But a list is still a decision. You’ve replaced one decision — should I deal with this — with another one that’s structurally identical: should I do step one. Step one still has to be chosen, still has to be evaluated, still competes with everything else you could be doing in that moment. If the task was being avoided because starting felt costly, decomposition hasn’t removed that cost. It’s relocated it to the first line of the list, where it sits just as heavily.

This is the part that gets skipped in most advice on the subject: the initiation cost of a task isn’t proportional to the task’s size. A five-minute errand and a two-hour project can carry the same weight at the threshold, because the weight isn’t coming from the work — it’s coming from the decision to begin. A list of five small steps still asks you to decide, five separate times, whether now is the moment. That’s not less friction. It’s the same friction, spread out.

What actually lowers the entry point

If the problem is the decision, the fix has to remove the decision, not just shrink the task around it. That means the entry point can’t be a step you evaluate and choose. It has to be small enough, and specific enough, that there’s nothing left to weigh.

In practice this looks like something you could do in about ninety seconds, involving one physical action, with no branch point inside it. Not “start on the package” — pick the package up and put it by the door you leave through. Not “deal with the laundry” — open the machine and put in the first three items your hand touches. The test is whether the instruction still contains a decision. If it does, it’s not small enough yet, no matter how short it sounds on paper.

This is different from motivation, and it’s different from willpower. It’s closer to removing a design flaw. The flaw is that most task-starting advice asks you to evaluate before you act. A real entry point asks you to act before there’s anything to evaluate.

Three ordinary examples

A return sitting by the door. Not “take it to the post office.” Pick it up and put it in the bag you carry when you leave the house. That’s the whole first move. Whether you go today or tomorrow is now irrelevant to whether the box is in motion.

Mail you’ve been avoiding. Not “handle your mail.” Open the one envelope on top of the pile. You’re not committing to read it, respond to it, or file it — just to see what’s inside. Most of what follows tends to happen on its own once the envelope’s open.

A load of laundry that’s been sitting for days. Not “do the laundry.” Carry the basket from the bedroom to the machine. Nothing about sorting, washing, or folding is decided yet. The basket just has to move.

None of these are smaller versions of the task. They’re a single motion that happens to be adjacent to the task, chosen because it requires no judgment call to perform.

I built it after noticing that my own task lists were full of things I agreed with and never touched. The app takes whatever you’re stuck on and returns one physical move, not a plan — the kind of instruction you can act on without first deciding whether now is a good time. It’s a narrow tool built around one mechanism, and it only does the one thing.

Where this doesn’t help

This approach is aimed specifically at initiation — the moment before a task starts. It has nothing useful to say about tasks that are hard because they’re genuinely difficult, ambiguous, or long-running once underway; shrinking the entry point gets you moving, but it won’t write the report or resolve a decision that legitimately needs more information. It’s also not a substitute for addressing why a task keeps generating dread in the first place, if the dread is about something real — a hard conversation, a financial problem, a diagnosis. In cases like that, the entry point can still get you to open the document or make the call, but what happens after is its own separate problem, and no amount of first-move design touches it.

Sometimes people are avoiding a task because they don’t have the information they need to do it. In that case the fix is information, not a smaller first step, and treating it as an initiation problem just delays the moment you notice what’s actually missing.