Most project planning starts in the wrong place. You open a doc, list the tasks, assign them to people, and call it a plan. Six weeks later, the project is stuck and nobody is quite sure why.
David Allen’s GTD Natural Planning Model starts two steps earlier — at purpose and vision — because that is where the brain actually begins when it encounters a new project. Skip those steps and you are building on sand. Start there and every decision downstream gets easier.
The model has five steps. They are not invented — they match the way the mind naturally plans anything it cares about. The difference is doing them deliberately, in order, before the task list appears.
What Is the GTD Natural Planning Model?
The GTD Natural Planning Model is a five-step framework from David Allen’s Getting Things Done for turning any project — from a client launch to a home renovation — into a clear set of next actions. The five steps are: define the purpose and principles, create a vision of the outcome, brainstorm freely, organise what you captured, and identify the very next physical action.
Most people who struggle with project planning are not bad at execution. They are starting at step three — the brainstorm — without having done steps one and two. That produces lists of tasks that feel urgent but lack a gravitational centre. The project drifts because there is no agreed-upon destination pulling it forward.
If you use GTD alongside a Second Brain or any other capture system, the Natural Planning Model is how you process a project from idea to actionable — it is the planning layer that sits above your context lists and weekly review.
Step 1: Define the Purpose and Principles
The purpose is the WHY in one sentence. Why does this project exist? What problem does it solve? What becomes possible when it is done?
If you cannot state the purpose in a single clear sentence, the project does not have an anchor. Every decision made inside it will be made against a different implicit standard, depending on who is making it and when.
Principles follow the purpose. They are the constraints — the things you would never do, even under pressure, to make this project succeed. Speed at the expense of quality. Cost savings at the expense of the client relationship. Shipping before testing. Naming these early means you do not have to relitigate them mid-project when someone is tempted.
Purpose and principles together give the project its character. They are not a mission statement — they are a decision filter that you use throughout the life of the project.
Step 2: Create a Vision of the Outcome
The vision is what wild success looks like. Not a cautious projection — a vivid, specific picture of the completed project as if you are standing inside it.
What does the client say when they receive it? What does the team feel? What is different about how the business operates? What number appears in the report that makes everyone exhale?
The brain is extraordinarily good at navigating toward a clear picture. It fills in gaps, spots relevant information, and filters out irrelevance — but only when it has a destination to orient toward. A blurry outcome produces blurry thinking. A specific one produces traction.
Write the vision down. It does not need to be long — a paragraph is enough — but it needs to be concrete. The project team should be able to read it and agree: yes, that is what we are building toward.
Step 3: Brainstorm Without Filtering
Now, with purpose and vision holding the frame, capture everything that comes to mind about the project. Tasks, obstacles, questions, people, risks, resources, ideas, dependencies — everything.
The single rule at this stage is no filtering. Evaluation comes later. Premature evaluation kills the brainstorm because the mind starts defending each idea rather than generating the next one. The goal is to get the project entirely out of your head — the same principle that drives a full brain dump — so that nothing is sitting in your working memory waiting to be remembered.
This is the step most people are already doing, but doing alone, without the anchor of purpose and vision. When you brainstorm inside a clear frame, the quality of what surfaces is higher. You think of the obstacles that actually matter, not the ones that feel salient in the moment.
Step 4: Organise What You Captured
The brainstorm is now a heap. Step four turns it into a structure. Group related items. Identify the natural components of the project. Find the dependencies — what has to happen before something else can start.
This is not project management software territory yet. It is a simple act of sorting: these things go together, that thing blocks this other thing, this component can run in parallel with that one.
Most projects organise themselves into three to five components once the brainstorm is sorted. If you find yourself with twenty separate components, either the project is actually several projects bundled together, or the sorting needs another pass.
Sequence the components where sequence matters. Milestone thinking is useful here — not arbitrary deadlines, but natural handoffs where one phase has to be complete before the next can begin.
Step 5: Identify the Next Action
For every open component in the project, identify the very next physical action — the specific thing someone could do right now, today, to move it forward.
Not “draft the proposal” — that is a project. The next action is “open the template and write the executive summary section.” Not “sort out the website” — the next action is “email the developer asking for the current hosting login.”
These next actions land on your GTD context lists: the calls to make, the things to do at your desk, the items waiting on someone else. When the right context arrives — you are at your desk, or you have five minutes between calls — the action is already named and ready.
A project without a named next action is a stalled project. The weekly review exists partly to catch these — any project without a clear next action gets one assigned before the review ends.
Where Claude Fits Into This Process
Once you have completed steps one and two — purpose defined, outcome pictured — Claude becomes an extraordinarily powerful brainstorm and organisation partner for steps three and four.
Give Claude the purpose statement, the principles, and the vision. Then ask it to generate every possible obstacle, sub-project, risk, and action it can think of for a project like this. The output will not be perfect, but it will surface things you would not have thought of under time pressure — and it will do so in two minutes rather than twenty.
For step four, ask Claude to group the brainstorm into logical components and identify the dependencies. It will produce a rough structure you can review and adjust, rather than starting from a blank page.
The key is that Claude is working inside your frame, not making up its own. The purpose and vision you defined in steps one and two act as constraints that shape everything Claude generates. This is the “give Claude a job, not a question” principle applied to project planning — you are handing it a real brief, not an open prompt.
For ongoing projects, the purpose, vision, and open components live in a CLAUDE.md project file so that every new session starts with the full context already loaded. Claude functions as a genuine project manager when it has this context — not an assistant you brief from scratch each time.
The Natural Planning Model and Your Weekly Review
The most common symptom of a project that skipped steps one and two is that it goes quiet. Nobody is sure what the next meeting is supposed to decide. Tasks pile up but the project does not seem to be moving. People are busy but the outcome is not getting closer.
When you encounter a stuck project in your weekly review, the diagnostic is almost always in the first two steps. Either the purpose was never clearly stated — different people have different answers to “why are we doing this” — or the outcome is blurry enough that nobody knows what done actually looks like.
The fix is not a new task list. The fix is a thirty-minute session with the relevant people to align on purpose and vision, followed by a fresh brainstorm inside that frame. Projects that have felt stuck for weeks often become unstuck in that one session.
Build the Natural Planning Model into your weekly review as a check: for every active project, does it have a clear purpose, a named outcome, and a next action? If not, that is the work for the week.
The Productivity System Behind the Model
The GTD Natural Planning Model is one tool inside a larger productivity framework. It tells you how to plan a project. The Nerd Productivity System wraps around it — the capture habit that gets the project idea out of your head in the first place, the processing step that decides whether it becomes a project at all, and the planning and execution phases that the Natural Planning Model then governs.
If you are a business owner managing multiple projects simultaneously, the Natural Planning Model is not a luxury — it is the difference between projects that compound and projects that drain. The ones that were planned from purpose move. The ones that were planned from task lists stall.
The productivity framework for entrepreneurs integrates the Natural Planning Model into the Plan phase — it is where the three weekly Rocks get their clarity, and where the decisions about what to take on and what to decline get made from a principled base rather than instinct under pressure.
If you want to see the full system — how capture, processing, planning, and execution connect, and where the Claude layer sits across all of it — the free NP System course covers each phase in detail. It takes about twenty minutes per module and gives you the structure to start building before you finish the last one.
To see the model applied step by step to a real project, read the GTD Natural Planning Model example — it walks through all five steps for a consultant launching a group programme.
Grab the free NP System course here.
Frequently Asked Questions
What is the GTD Natural Planning Model?
The GTD Natural Planning Model is a five-step project planning framework from David Allen’s Getting Things Done. The steps are: define the purpose and principles, create a vision of the outcome, brainstorm freely, organise what you captured, and identify the next physical action. The model works because it mirrors the way the mind naturally plans anything it cares about.
How is the Natural Planning Model different from normal project planning?
Most project planning starts with tasks and milestones — steps three and four of the Natural Planning Model. The Natural Planning Model starts with purpose and vision first, which gives every downstream decision an anchor. Without that anchor, task lists accumulate but the project lacks direction and tends to stall.
What is the most important step in the Natural Planning Model?
Step one — defining the purpose — is the most important step because it governs everything else. A clear purpose statement makes the brainstorm more productive, the organisation more coherent, and the next actions more obviously relevant. Most stuck projects are stuck because the purpose was never agreed upon, not because the task list was wrong.
How long does the Natural Planning Model take to apply?
For a simple solo project, you can run through all five steps in fifteen to thirty minutes. For a team project with multiple stakeholders, you might spend an hour on steps one and two alone — but that hour replaces weeks of misalignment. The brainstorm and organisation steps scale with complexity but rarely take more than two hours even for large projects.
Can you use the Natural Planning Model for small or personal projects?
The Natural Planning Model works at any scale. For a simple project — planning a holiday, running a client deliverable — a five-minute pass through all five steps is enough to get a clear purpose, a picture of done, and a named next action. For larger projects, you invest proportionally more time in steps one through four. The structure is the same regardless of scale.
The brainstorming and next-action steps in the Natural Planning Model are also where AI tools add the most leverage — see how to automate tasks with Claude AI for a practical walkthrough of using Claude to generate, filter, and sequence next actions within this five-step structure.
For a broader view of how to wire Claude into your project management workflow — including maintaining a context file per project — see how to turn Claude into a project manager.
