Backwards planning for big projects

“Launch the thing by June” is not a task — it is a fog bank. Your brain cannot start a fog bank, so it starts nothing while the deadline sits comfortably far away.

Big projects fail at the front, not the end. The panic at the finish line is all the postponed starting, arriving at once.

Forward planning makes this worse. Starting from today and listing steps toward a distant goal just builds a longer, vaguer blob — and a blob with no edges has no first step, so every day is a valid day to not start.

Start at the deadline and ask one question on repeat: what has to be true one step before this? You are not guessing durations in the abstract — you are anchoring each piece to a date that already exists.

If a step lands in the past, the deadline was never real — better to learn that now than in the final week.

• Write the deadline. That is the final milestone.
• Ask “what must exist one step earlier?” Give the answer a date.
• Repeat until you reach something you could do this week.
• Pad every step — things take longer than the plan says, every time.

Each milestone answers the next. The chain replaces the blob with small, dated, startable things.

The milestone nearest today gets shredded like any other task. “Draft the outline” becomes “open a blank document and write three ugly headers.”

A backwards plan only works if the first link is physically doable this week. Otherwise you have built a beautiful chain anchored to a fog bank.

• Put the milestone dates in your real calendar, where appointments live.
• Do the first small step today, before the plan cools into a document you never reopen.
• Tell one person the first milestone date — borrowed witnesses make dates feel real.
• Re-walk the chain weekly. Dates will move, and moving a date is planning, not failing.

A backwards plan is a map, not a prophecy. Redrawing it as reality arrives is the whole job. And a milestone with a date is something you can say out loud — said-out-loud things get done more often.