Why Can't I Start Tasks Even When I Know They Matter?

Q: What helps with decision friction?

Write the physical first move, not the task: "Draft the proposal" is a project. "Open a blank doc and write three bullet headings" is an action. The rule of thumb: if you can't picture your hands doing it, it isn't specific enough yet. Decide the first step the day before: Defining the entry point costs the same effort whenever you do it, but doing it in advance means the moment you sit down carries no ambiguity. Deciding at the desk is what leaks the time. Lower the bar to something faintly embarrassing: Two minutes, badly. The goal is not progress but crossing from not-started to started, which is the only threshold this pattern struggles with. Once across it, the usual momentum applies. Notice which tasks stall: If your stalled tasks are consistently the vague ones and your finished tasks are consistently the well-specified ones, that is the pattern confirming itself — and it tells you the fix is upstream, in how you write tasks down.

Your mind stalls not from laziness but from the absence of a concrete starting point. Once the action is clear you move quickly. The delay lives in the gap between intention and first step. This pattern often masquerades as procrastination but is really a navigation problem.

How to recognise it

You reread the same task on your list for days without touching it.
Once someone tells you the exact first action, you do it almost immediately.
Vague tasks ("sort out the budget") stall; specific ones ("open last month's statement") don't.
You feel a small flare of resistance when you look at the task, and drift to something easier.
You are not avoiding the work itself — you'd happily do step four if you knew what step one was.

Why it happens

Starting a task requires holding an unclear goal in working memory while searching for an entry point. That search is effortful, and the brain treats effortful ambiguity as mildly aversive. Anything with a defined first move — email, messages, tidying — becomes comparatively attractive, so you drift toward it.

The important detail is that this is a navigation cost, not a motivation deficit. Motivation problems look like not caring about the outcome. Decision friction looks like caring a great deal and still not moving, which is why it produces so much guilt: the usual advice about wanting it more doesn't fit the actual failure.

What it gets mistaken for

Laziness, or a discipline problem. It is neither, which is why willpower-based advice reliably fails against it — you cannot push harder through an unspecified action.

What actually helps

Write the physical first move, not the task

"Draft the proposal" is a project. "Open a blank doc and write three bullet headings" is an action. The rule of thumb: if you can't picture your hands doing it, it isn't specific enough yet.

Decide the first step the day before

Defining the entry point costs the same effort whenever you do it, but doing it in advance means the moment you sit down carries no ambiguity. Deciding at the desk is what leaks the time.

Lower the bar to something faintly embarrassing

Two minutes, badly. The goal is not progress but crossing from not-started to started, which is the only threshold this pattern struggles with. Once across it, the usual momentum applies.

Notice which tasks stall

If your stalled tasks are consistently the vague ones and your finished tasks are consistently the well-specified ones, that is the pattern confirming itself — and it tells you the fix is upstream, in how you write tasks down.

How to know if this is really your pattern

Whether the days you rate low on focus are the days your intention was written vaguely. If specific intentions correlate with completed days and vague ones with stalled days, decision friction is the live constraint rather than energy or motivation.

Self-recognition is a starting point, not proof. Descriptions like this one feel true to a lot of people, which is exactly why the useful step is checking it against your own days rather than against how well the description reads.