Plan a project backwards from the deadline instead of forward from today
Forward planning tells you when you'll finish. Backward planning tells you if you can.
- Use it for
- Anyone planning a project with a real, fixed deadline.
Forward planning — list the tasks, estimate each, add them up, see when you land — tends to produce an optimistic schedule that discovers it's wrong right when it's most expensive to fix, close to the deadline. Planning backward from the fixed deadline forces a different question from the start: given this end date, what has to be true at each checkpoint along the way, and does the real work actually fit — which surfaces a problem while there's still time to cut scope or push back.
This prompt builds the plan from the deadline backward, checkpoint by checkpoint.
When not to use this
If the deadline is soft or negotiable, backward planning's rigidity is more constraint than the situation calls for — forward planning with reasonable buffers is fine. This is for a genuinely fixed date you can't move.
Did this work?
You know, before starting, whether the deadline is actually achievable given the real work — not just an optimistic forward schedule that discovers the problem three weeks before the deadline.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.