Make the Task Too Small to Avoid

The Real Reason You're Not Starting

You've looked at the task. You know what it is. You know it matters. And yet you're doing something else.

This isn't a character flaw. It's a sizing problem.

When a task feels large or undefined, your brain quietly files it under "later." Not because you're lazy. Because the brain prefers a clear, completable unit of work over a vague, open-ended one. "Write the report" is open-ended. "Write the first sentence of the report" is completable.

The difference between those two versions of the same task is everything.

The Uncomfortable Truth

Here it is: most of your procrastination has nothing to do with the difficulty of the work. It has to do with the size of the unit you're asking yourself to complete.

You've been treating task resistance as a motivation problem when it's actually a framing problem. Waiting to feel ready is waiting for something that often doesn't arrive on schedule — especially when the task is ambiguous or emotionally heavy. Fixing your framing is faster and more reliable than waiting for your mood to shift.

The Minimum Viable Action Framework

The framework is simple. Call it Minimum Viable Action, or MVA.

For any task you're avoiding, ask one question: What is the smallest version of this task that still counts as starting?

Not the smallest version that finishes it. Not the version that produces a great result. Just the version that counts as having started.

Then ask a second question: Can I reasonably refuse to do this right now?

If the answer is yes — the task is still too big. Shrink it again.

A few examples:

• "Send the proposal" becomes "open the draft and read the first paragraph."
• "Work out" becomes "put on your shoes and stand up."
• "Plan the project" becomes "write three bullet points about what this project actually is."

None of these complete the task. That's not the point. The point is that they make the excuse harder to justify than the action itself. Once you're in motion, continuation is far easier than initiation. That's not philosophy — it's just how directed attention tends to work.

Three Rules for Applying This

Rule 1: Define the task in physical terms, not outcome terms.

"Be productive" is not a task. "Open the document" is. "Focus better" is not a task. "Write one sentence" is. Outcomes are results of action. You can't do an outcome. You can only do a behavior. So write the behavior.

Rule 2: If you're still avoiding it after shrinking, shrink it again.

There is no floor that's too low. If "open the document" still feels heavy, the rule is: go smaller. "Move the file to your desktop." "Type the title." The goal isn't to feel proud of the step. The goal is to eliminate the gap between deciding and doing. Embarrassingly small still counts.

Rule 3: Do not negotiate the start condition.

The start condition is fixed: the smallest action you defined. You don't wait until you feel like it. You don't wait until the environment is perfect. You do the one small thing at the time you said you would. The negotiation happens before you set the task — not after. Once it's set, the only variable is whether you do it or not.

Why This Works in the AI Era Specifically

Right now, you're surrounded by tools that can generate, summarize, and draft almost anything. That's useful. But it also creates a new kind of avoidance: outsourcing the start.

You open an AI tool before you've thought for five minutes. You ask it to outline something you haven't tried to outline yourself. The output looks fine, but it doesn't connect to anything you actually know or care about — so you stall on the next step anyway.

The Minimum Viable Action framework keeps your thinking in the loop. You start first, even if the start is tiny. Then you use tools to extend, not replace, your initial effort. The thinking you do in those first two minutes of genuine work is what makes everything after it useful.

One Thing Worth Noting

This approach won't make hard things easy. A genuinely complex project will still require sustained effort, clear thinking, and real time. Shrinking the entry point doesn't compress the work itself.

What it does is remove the false barrier between you and the work. That barrier is almost always smaller than it feels. And the cost of leaving it there — day after day — compounds.

Reflection Question

What task have you been calling "too big to start" that you haven't yet tried to define in physical, behavioral terms — and what would the smallest possible version of it actually look like?