There’s a document on your machine you’ve opened maybe four times.
You know the one. It has a working title. It might have three paragraphs in it from 4 years back.
And here’s what makes it interesting rather than embarrassing: you are not a person who fails to do things. You shipped a project last quarter with a genuinely brutal deadline. You’ve handled worse than this, under more pressure, with less time, for people you don’t even like.
You can do hard things. Demonstrably.
You just can’t do this one. The one you actually want.
So you’ve concluded you must be lazy, or self-sabotaging, or afraid of success, or one of the other diagnoses the internet hands out for free.
All of those are wrong, and I can show you why in about a paragraph.
What the Fog Is
The Fog is the state produced when a goal is held at a level of abstraction too high to act on. A goal such as “write a book” or “start a business” is not a task but a category containing hundreds of unspecified actions, and the mind cannot execute a category. The resulting paralysis is not a motivation or discipline failure — it is an accurate refusal to run an instruction that has no defined first step. The Fog is recognisable by three signs: the goal feels physically uncomfortable to look at, thinking about it produces fatigue rather than progress, and the person experiencing it performs competently on comparable or harder work elsewhere. It dissolves through decomposition, in which the goal is resolved downward through milestone and module to the level of a moment — a single action small enough to begin within sixty seconds and finish without further decisions.
That’s the diagnosis. Now here’s why it’s good news.
Your Brain Is Working Correctly
This is the turn, and it’s the reason this article exists, so I’ll put it plainly.
The paralysis is accurate.
Try this. Right now, without preparing, execute the instruction: write a book.
Go.
You can’t. Not because you’re undisciplined — because that isn’t an instruction. There’s no first physical movement contained in it. Nothing to pick up, open, or type. It’s a label for an outcome, and you’ve been handing it to yourself as though it were a command.
Every morning you’ve looked at that label and something in you has correctly reported: this cannot be run.
And then, because you couldn’t see what was actually happening, you’ve taken the failure to run as evidence about your character.
It isn’t. It’s evidence about the instruction.
That’s the reframe. Your brain isn’t refusing to work. It’s refusing to execute an undefined operation, which is precisely what any competent system does. You’ve been furious at yourself for a filing error.
And this explains the thing that never made sense: why you can do harder work elsewhere. At work, someone else already did the decomposition. The task arrived pre-specified. “Prepare the Q3 analysis for Thursday” contains a defined output, a defined deadline, and an obvious first movement.
Nobody’s doing that for the thing you actually care about.
That’s the whole difference. Not motivation. Not passion. Somebody else was doing your decomposition for you, for years, and you mistook it for capability.
Why the Discomfort Is Physical
Worth explaining, because most people misread this signal badly.
When you look directly at an undecomposed goal, something unpleasant happens. Not a thought — a sensation. A weight, a slight aversion, the impulse to look at something else. People describe it as dread, and it arrives before any conscious reasoning about the goal.
That’s a load signal.
An unspecified goal has no boundaries, so the mind can’t estimate what it costs. And a mind that can’t estimate the cost of a thing prices it, sensibly, as very large. You get the fatigue of the entire project every time you glance at it, because there’s no way to load a part of something with no defined parts.
Which produces the strangest symptom in the whole territory: exhaustion before you’ve begun. You sit down to work on it and you’re already tired, having done nothing. That’s not a metaphor and it’s not weakness. That’s the accumulated cost of repeatedly loading an unbounded object.
And it’s why thinking about a goal for months changes nothing. You’re not making progress during that thinking. You’re paying the load cost, over and over, and getting no output for it. Some people do this for years and conclude they must not want it enough.
They want it fine. They’re just carrying it in a shape that can’t be put down.
Decomposition: Four Levels
Here’s the method. Four levels, and the whole thing turns on the fourth.
Goal. The outcome. “Write a book.” Not actionable, and it isn’t supposed to be. Its job is direction, and it does that job fine. The error is asking it to also be an instruction.
Milestone. A visible waypoint. “Finish the first draft.” Still not actionable — you can’t do a milestone — but it converts an infinite object into a finite one, and that alone reduces the load.
Module. A coherent chunk of work. “Draft chapter three.” Now we’re in recognisable territory, and this is where almost everybody stops. This is the level that standard advice means by “break it into smaller steps.”
And it’s still one level too high. That’s the entire problem with the standard advice, and it’s why you’ve tried it and it didn’t work.
Moment. A single action, beginning inside sixty seconds, finishing without further decisions. “Open the chapter three file and write the first sentence, however bad.”
The difference between module and moment is not a difference of size. It’s a difference of kind.
“Draft chapter three” still contains unresolved decisions — what goes in it, how it opens, whether the structure holds. Every one of those is a small fog, and you’ll hit them and stall.
“Open the file and write one bad sentence” contains none. There’s nothing left to decide. You can be doing it fifteen seconds from now.
The Sixty-Second Test
One test tells you whether you’ve gone far enough:
Could you begin this within sixty seconds, and complete it without making another decision?
Both halves matter.
If you can’t begin it in sixty seconds, there’s a hidden step in front of it — go find that step, and that’s your actual task.
If you can begin it but you’ll hit a decision partway through, you’ll stall at the decision, and the stall will feel like a return of the Fog. Because it is one. Just smaller.
Run the test honestly and you’ll notice something uncomfortable: most items on your to-do list fail it.
“Sort out the website.” “Look into pricing.” “Think about the structure.” Those aren’t tasks. They’re fog fragments with a checkbox next to them, and their real function is to let you feel organised while ensuring nothing gets done.
That’s why your list has items on it from March.
They were never executable. They’ve been sitting there, generating load, and their only effect has been to make you feel like someone who doesn’t finish things.
The Arithmetic
Now the part that converts this from a technique into a reason.
Say a project has ten steps and you’re roughly 70% confident about each — you know approximately what to do, you’d get there, probably.
70% ten times over is 2.8%.
Not 70%. Not “pretty likely.” Under three in a hundred.
Now decompose until each step is clear enough that you’re at 95%.
95% ten times is 60%.
Same project. Same person. Same effort. From a 3% chance of completion to a 60% chance, purely by resolving each step from approximately clear to obvious.
That’s the whole argument for granularity, and it’s why “break it into smaller steps” is right in direction and useless in practice. Smaller isn’t the variable. Certainty per step is the variable, and size is only a proxy for it.
This also explains something that looks like a personality difference and isn’t. The person who reliably finishes things isn’t more determined than you. They’re operating at a higher per-step certainty, which compounds across the project. From outside it looks like grit.
It’s arithmetic.
And it connects directly to the oldest material on this site: the causal chain, where outcomes aren’t random but the compounded product of a sequence of causes, and where the leverage is always in the sequence rather than in the outcome.
Which leads to the sentence I’d want you to keep:
Stop trying to make the outcome likely. Make each action certain, and the outcome takes care of itself.
Start With the Easiest, Not the Most Important
This instruction annoys people, and it’s the most reliably useful one here.
Everyone starts with the most important action. It’s also the least defined and the highest-load, so it fails — and now you have evidence that you can’t do this, which increases the load on the next attempt.
The easiest action has a different job. It’s not there for output. It’s there to break the state.
There’s a large practical difference between a project you haven’t started and a project you’re twenty minutes into, and almost none of that difference is the twenty minutes. Started and not-started are different psychological objects. The load on an active project is a fraction of the load on a dormant one.
So the first action’s purpose is to move the project across that line, and the cheapest action that does it is the correct one.
Trivial is fine. Trivial is preferred.
What This Is Not
Three hard lines.
It is not “break it into smaller steps.” That advice stops at the module level, which is one level above where anything becomes executable, and it stops there because module-level chunks look like tasks. This method has a defined bottom and a test for whether you’ve reached it. Advice without a test can’t tell you when you’re done, which is why you’ve followed it before and stayed stuck.
It is not time management or productivity systems. Those optimise the execution of tasks you can already start. If you can’t start, a better calendar is a solution to a problem you don’t have. Most productivity advice assumes the decomposition happened somewhere off-screen — usually because the person writing it works in an environment where someone else does it.
It is not a motivation problem. I’d argue this hardest, because the misdiagnosis is so expensive. If it were motivation, you wouldn’t want the thing. You do want it — you’ve wanted it for four years, which is considerably more evidence of motivation than most people ever produce. Treating an information problem as a motivation problem sends people to inspiration, which raises the load without resolving anything, and they crash harder. That’s a whole argument on its own: is procrastination a discipline problem or an information problem?
The Cost
Every method here names its price, and this one’s is peculiar. Most people don’t see it coming.
You lose the pleasure of having a big dream.
Right now, that undecomposed goal is doing something for you. Not much — but not nothing. It sits there being magnificent. You get to be a person with a novel in them, a business in them, a thing that would astonish people if they knew.
Undecomposed, it stays perfect. It can’t fail, because it hasn’t started. It’s pure potential, and potential is genuinely pleasant to own.
Decompose it and it becomes eleven modules and about two hundred moments, most of which are boring. The magnificence doesn’t survive contact. What you’re left with is “open the file and write one bad sentence,” on a Tuesday, in a mood.
A number of people discover at this exact point that they preferred the dream.
That’s worth knowing about yourself and it isn’t shameful — but you can’t find it out while the thing stays in the Fog, because the Fog protects the goal from being tested. It’s the most comfortable failure state available: you never have to find out whether you’d have finished, and you get to keep the identity of someone who might.
The second cost is smaller. This is boring work, permanently. Ten minutes of unglamorous resolution before anything interesting happens, every time. It doesn’t graduate into something more inspiring.
It just works, which is a different thing.
Common Questions
Why do big goals paralyse you?
Because they’re categories rather than instructions. There’s no first physical action contained in “start a business,” so there’s nothing to execute, and the mind correctly declines to run an undefined operation. The paralysis is a specification failure, not a willpower failure.
Why can’t I start something I genuinely want to do?
Usually because nobody else decomposed it for you. Work you complete easily arrived pre-specified by someone else — defined output, defined deadline, obvious first movement. Your own goals arrive raw, and the specification step is invisible enough that most people never realise it’s the missing piece.
Is procrastination laziness?
Rarely. Laziness would predict avoiding all effortful things, and most people stuck on a personal project are performing well elsewhere. That inconsistency rules out a general disposition and points at something local to the task — nearly always that the task isn’t specified enough to start.
Why does “break it into smaller steps” not work?
Because it stops one level too high. It gets you to chunks like “draft chapter three,” which still contain unresolved decisions and therefore still generate paralysis. It also has no test attached, so you can’t tell whether you’ve gone far enough.
How small is too small?
There’s a floor, and it’s when the decomposition itself takes longer than the action. If you spend four minutes specifying a thirty-second task, you’ve overshot. In practice almost nobody hits this — the overwhelming error runs the other way.
Why does thinking about a goal for months change nothing?
Because thinking about an undecomposed goal isn’t work on it. You’re repeatedly loading an unbounded object, paying the cost of the whole thing, and producing no specification. Months of that generate real fatigue and zero progress, which people then misread as evidence they don’t want it enough.
What if I genuinely don’t know what the next step is?
Then the next step is finding out, and that’s a real task with a real first action — usually a specific question aimed at a specific person or source. “I don’t know how to do this” is not a blocker. It’s an unstated task masquerading as one.
Where to Start
One thing. Ten minutes. This week.
Take the goal you’ve been carrying longest. The one with the document.
Write it at the top of a page. Then resolve it downward, in writing, until you have one action that passes both halves of the sixty-second test: you could begin it within a minute, and finish it without making another decision.
Not the most important action. The easiest one that’s genuinely part of the project.
Then do that one thing today, and stop.
Not because momentum is magic. Because you’ll have moved the project from dormant to active, and those two states have completely different costs, and you’ll feel the difference the next time you look at it.
The Fog doesn’t lift because you finally found the resolve. It lifts because a thing with no edges got given edges, and things with edges can be picked up.
I’ve spent twenty-five years working on how ordinary people develop capabilities that look impossible from the outside, and the single most common thing separating people who finish from people who don’t isn’t drive, talent, or discipline.
It’s that one group is working on tasks and the other group is staring at categories.