The gap between your goals and your daily work is usually a project-planning problem. Most people write ambitious outcomes on a list, call them tasks, and wonder why nothing moves. In GTD, a project is any outcome you are committed to completing within one year that requires more than one action. That distinction — between a project and a task — is where the planning starts.
“Write the proposal” is not a task. It is a project. “Send the proposal to James” is a task. Getting that distinction right across your full commitments list is what the GTD system is built on, and it is where most GTD project planning breaks down before it starts.
The done-state test
Every GTD project needs a done-state sentence — one line that describes exactly what finished looks like. Not “finish the marketing”, but “Q4 email campaign drafted, reviewed, and scheduled in Kit by 15 October”. The specificity is not pedantry. It is the thing that makes planning possible.
Without a done state, you cannot identify the steps needed to reach it. Without the steps, you cannot identify the next action. Without a next action, the project stalls. The done-state sentence is the foundation of the whole chain. If you sit down to plan a project and cannot write that sentence in one attempt, the project is not yet defined — you are still in the thinking phase, not the planning phase.
One practical test: if a colleague picked this project up tomorrow, would they know exactly what done looks like from the project name alone? If the answer is no, the name is an area of responsibility masquerading as a project. Rename it with the outcome, and the planning gets easier immediately.
Auditing your task list for hidden projects
The most useful first step in GTD project planning is not creating a new list — it is reviewing the list you already have and reclassifying everything correctly. Most people carry 20 to 40 items they call tasks that are actually multi-step projects. Finding them is the clarifying move.
The test is simple: can this be done in a single physical action? If yes, it is a task. If no, it is a project, and it belongs on the GTD projects list with its own done-state sentence and at least one next action. This reclassification pass often reveals that the items causing the most anxiety are the ones that have been miscategorised — they feel like tasks, so they sit on the task list indefinitely, but no single action ever completes them.
Business owners who run this audit for the first time typically discover 30 to 60 active projects. That number is not a sign of overcommitment. It is a sign that many commitments were living inside their head without a plan — what GTD calls open loops. Naming them as projects closes the loops and takes the mental load off your working memory.
Planning complex projects with the natural planning model
For straightforward projects, a done-state sentence and one next action is enough to get moving. For larger or more complex projects — a new service launch, a significant client engagement, a business system rebuild — the GTD natural planning model is the right tool.
The model runs in five steps: define the purpose and principles, envision the outcome, brainstorm all the components, organise them into a sequence, and then identify the next action. Most people skip straight to organising, which is why they produce plans that feel logical on paper but leave out half the dependencies. The purpose step — why does this project exist, and what limits what we do — changes what gets brainstormed. It is worth the five minutes before you start.
The outcome-envisioning step deserves specific attention. Making the done state vivid — not just written down but mentally imagined — changes the quality of the brainstorm that follows. When you can picture the finished state clearly, the ideas that belong in this project sort themselves from the ones that belong elsewhere. This is not a productivity technique. It is how your brain naturally generates relevant ideas, and the natural planning model builds around it deliberately.
The next-action rule
Every project on your list needs a next action — a single, physical, visible action that is available to do right now. Not a phase, not a milestone, not a sub-project. The next action must be the smallest concrete move that would advance the project today.
“Plan the client onboarding” is not a next action. “Draft the three-question intake form” is a next action. The difference is not about scope — it is about executability. When you open your task list and see something you can physically do without further decision-making, you work. When you see something that requires you to figure out what to do before doing it, you hesitate. That hesitation compounds across a full project list until the list feels like a burden rather than a guide.
During the weekly review, every project that lacks a next action gets one. This is the maintenance step that keeps the project list alive rather than stagnant. A project list without next actions is a wish list. A project list where every item has a concrete next action is an executable plan.
GTD project planning in the NP System
In the Nerd Productivity System, GTD project planning sits in the Plan phase. The Plan phase is where you move from processing your captured inputs to deciding what you are committed to and in what sequence. Your projects list is the full inventory; your weekly Rocks are the two or three projects getting real protected time this week; your next actions are what lands in your daily execution blocks.
The reason GTD and the NP System complement each other is that both treat planning as the bridge between strategy and daily work. When your project list is current, every project has a done state, and every project has a next action, the daily question of what to work on becomes straightforward. You are not deciding from scratch each morning. You are working from a plan that the weekly review keeps honest.
If you want to see how the NP System ties Capture, Process, Plan, and Do into a single framework, the free NP System course walks through each phase in sequence. You can also take the productivity quiz to find out which phase is causing the most friction in your current system before you start rebuilding.
