What is the DRAFT model?
Turning vague intentions into plans that can actually be executed, reviewed, and improved. Its core process is: D = Define the objective
R = Reverse-engineer milestones and dependencies
A = Allocate owners, resources, and deadlines
F = Forecast risks and failure points
T = Test the plan against reality and revise
What problem is the DRAFT model designed to solve?
Turning vague intentions into plans that can actually be executed, reviewed, and improved.
What are the steps of the DRAFT model?
D = Define the objective
R = Reverse-engineer milestones and dependencies
A = Allocate owners, resources, and deadlines
F = Forecast risks and failure points
T = Test the plan against reality and revise
What is the master question for the DRAFT model?
What exactly are we trying to achieve, what must happen in what order, who owns each part, and where will this likely break?
When should I use the DRAFT model?
Use it for projects, launches, campaigns, operations, and personal plans that need more than good intentions.
What mistake does the DRAFT model try to prevent?
It prevents plans that sound impressive but lack ownership, sequencing, risk thinking, and practical realism.
What is the one-line rule of the DRAFT model?
Define the end, map the path backward, assign ownership, forecast failure, and revise before execution.
How do I know I am using the DRAFT model correctly?
You are using it correctly if plans become easier to execute, easier to monitor, and less vulnerable to obvious surprises.