Why Big Goals Stall in the First Week

The book, the course, the business, the renovation. Whatever the big one is, it has a folder, and the folder has been opened maybe nine times this year.

Some of those nine were spent planning. Some were spent trying to begin. What almost never happens is both, and that is closer to the whole problem than it sounds.

Two jobs that cancel each other out

Planning and starting want opposite things.

The planning instinct wants every variable accounted for before anything is committed, which is why it keeps pushing the start date outward. There's always one more thing to resolve, and resolving it is genuinely useful, and it also means today is not the day.

The starting instinct wants motion right now, which produces plans thin enough to fall apart the first time reality disagrees. Three weeks in, something obvious surfaces that a week of thinking would have caught, and the whole thing loses its footing.

Run them at the same time and they cancel. You plan badly because you're impatient to start, and you start badly because the plan is thin. Then the folder closes for another two months.

Bent Flyvbjerg and Dan Gardner looked at more than sixteen thousand projects across dozens of countries, at every scale from kitchen renovations to Olympic Games, and found a consistent pattern in what blew up. The failures were rushed in the doing and thin in the planning. The successes ran the other way around.

Plan slow, while planning is still free

There is exactly one phase of any project where changing your mind costs nothing, and it's the phase before anything is committed. On paper, in a sketch, in a document nobody has seen. Being wrong there is free. Being wrong in execution costs real time, real money, and some amount of your willingness to try again.

So do the thinking exhaustively while it's cheap. Not for a year. But if the thing has sat for eighteen months, two focused weeks of planning is not procrastination, and treating it as such is how the folder stays closed.

One part of that planning is worth doing deliberately, because instinct gets it wrong: estimate from the outside. Before locking any timeline, go find out how efforts like this actually went for other people. Not how you feel it will go. Your inside view is a story you're telling yourself, assembled from best-case pieces. Other people's results are data, and the data is almost always slower than the story.

That's Plan Slow, Start Small, and the second half is what makes the first half survivable.

Start small enough that it isn't a decision

Once the plan is thorough, the daily ask should be almost embarrassingly modest. The plan is carrying the ambition. The first move doesn't have to.

But "small" gets misread as "vague," which is where the second idea earns its place. The unit you repeat should be a brick: something you finish, look at, and judge.

Not "write for an hour." An hour produces no finished thing and teaches you nothing you can repeat. One clean paragraph is a brick. It ends somewhere. It can be assessed. Doing it twice tells you something doing it once could not.

Size it between two failure modes, and both are easy to read:

• If it never finishes, bleeding past the sitting and never resolving into something you'd call done, it's still a fragment rather than a unit.
• If the tenth repetition looks exactly like the first, it was too small to carry any signal, and you've been logging time rather than learning.

The right brick is done by the end of the sitting and visibly better by the tenth. That's The Repeatable Brick, and it's the same logic that gets bridges built. A one-of-a-kind project has to be right the first time. A repeatable unit gets to be wrong cheaply, over and over, until the pattern that works shows itself.

What this looks like on the folder you've been avoiding

A course that had been "almost ready to start" for a year got two weeks of nothing but planning. Full outline, every module named, the actual scope written down where it could be looked at.

The outside-view check was the uncomfortable part. Comparable courses took their makers four to six months, not the six weeks the folder assumed. The timeline doubled before a single lesson existed, which felt like a defeat and was the opposite.

Then the brick: one complete lesson, script and slides, finished in one sitting. The first was slow and not good. The fourth was quick. By the ninth there was a repeatable pattern that hadn't existed at the start and couldn't have been designed in advance.

The order matters

Plan until the thinking is genuinely done, and estimate from what happened to other people. Then shrink the daily unit until refusing it would take more effort than doing it, and make sure it's a thing that finishes.

Nothing about the ambition shrinks. What shrinks is the size of the thing you have to face on a Tuesday morning.