Episode Overview

Episode Title: GTD Implementation and Integration
Host: John Forrester (GTD®)
Date: March 11, 2026
Main Theme:
This office hours-style episode offers a practical, interactive discussion on the nuances of implementing and integrating Getting Things Done® (GTD) principles for both new and seasoned practitioners. Listeners share personal scenarios and questions about recurring projects, next actions, checklists, project planning, reviews, and group processes, making it a rich resource for actionable tips and relatable insights.

Key Discussion Points & Insights

1. Recurring Projects: Checklist vs. Individual Projects

• Peter asks how to best handle frequently recurring events in a GTD system—should each event be tracked as a separate project or managed with a recurring checklist or area of focus?
  • Mark suggests developing a reusable checklist to avoid rethinking each time (03:34).

  "If you were going through a repeated process, developing a checklist for what you would do for each of those events, then you'd only have to deal with what was different." — Mark (03:34)

  • John Forrester elaborates that checklists are helpful for routine elements while leaving space for tracking exceptions or unique aspects (04:17).
  • Sebastian introduces the idea of using a tickler file or calendar triggers to avoid overloading the project list, adding projects to the system only when a new event is imminent (12:30).

Notable Insight:

A blend of checklists for routine tasks and project tracking for unique elements reduces complexity and “list fatigue.”

2. Projects On Hold vs. Active Projects

• John Forrester explains the value of maintaining a "Projects On Hold" list for commitments due within a year but not currently actionable, distinguishing them from Someday/Maybe items (09:07).
• Importance of timing: Considering when actions become relevant is key to keeping the project list mentally uncluttered.

3. The Natural Planning Model (NPM) — When & How to Use

• Sebastian inquires about practical usage of NPM—should it only be done at the project’s start, or more frequently? (14:15)

  • John responds that NPM can be valuable at any project phase—beginning, middle, or end (postmortem)—and its formality can scale with project size and complexity (15:21).
  • Group NPM sessions, whether in person or online, are described as helpful for collaborative clarity (31:59).

  "Anytime you want to run the Natural Planning Model on a project, it's fine... If I were building the Golden Gate Bridge, I would be doing the natural planning model and revisiting it regularly." — John Forrester (15:21)

4. Next Actions: Defining and Tracking

• Claudia asks about handling next actions with due dates for projects with a known completion deadline (16:53).

  • John suggests several strategies: calendar booking for true deadlines, using flags sparingly, and focusing on review frequency instead of over-reliance on reminders (17:55; 20:23).
  • Sebastian and others highlight that diligent reviewing—daily or weekly—is better than heavy flagging or excessive time-blocking, which can cause more stress if overused (21:52).
  • Peter emphasizes specifying the "truly next physical step," which may not always be as generic as “edit manuscript”—sometimes the actual first action is preparatory, like requesting file access (29:13).

  "If you pick a verb that is really specific about what you'll be, what someone would see you doing when you're doing that action, it's more likely to attract you to it." — John Forrester (24:21)

5. Personalizing Project and Action Planning

• Chris shares his strategy for client software projects: maintaining target schedules in project support materials (instead of the main calendar), enabling course corrections during reviews (25:16; 26:38).
• Device contexts matter: Some use context/time blocks; others, frequent reviews in busy or rapidly-changing schedules.

6. Deciding What to Work on Next

• Masha pertains to prioritizing among numerous next actions; John shares that David Allen recommends doing what you “feel like doing”—trust that eventually, what you feel is what you should do (28:17).

  "Do what you feel like doing. Do what you'd like to do. Because eventually what you'd like to do will be what you should do." — David Allen (quoted by John Forrester, 28:17)

Notable Quotes & Memorable Moments

• John Forrester on over-flagging:

  "When I start thinking, 'Oh, it's going to be tempting to flag something,' it's a sign that I'm really busy not doing a review often enough and need to reconsider my commitments altogether." (20:23)

• Sebastian on review frequency:

  "It's all about reviewing. It's all about doing daily, weekly, bi weekly reviews... If I would review accordingly and if I would adjust the frequency of my reviews to my workload...then there wouldn't be a problem." (21:52)

• Peter on granular next actions:

  "I think it's always very important to... visually imagine yourself doing [the next step]... Sometimes that could still look a little bit different from that generic description of what the task might look like." (29:13)

Timestamps for Important Segments

• 01:58 — Question about managing recurring projects/events (Peter)
• 03:34 — Checklist suggestion for recurring events (Mark)
• 07:07 — Differentiating active/hold projects in busy schedules
• 12:30 — Using tickler files/calendar for repeat events (Sebastian)
• 14:15 — Discussion on when to use the Natural Planning Model (NPM)
• 16:53 — Next actions with due dates and tracking work-in-progress (Claudia)
• 20:23 — Risks of over-flagging and benefits of reviewing
• 21:52 — Sebastian on review cadence as solution for scheduling stresses
• 24:21 — Making next actions granular and actionable (John Forrester)
• 25:16 — Scheduling and course corrections using project support (Chris)
• 28:17 — Doing what you feel like doing (quoting David Allen)
• 29:13 — The subtlety of defining “next action” (Peter)
• 31:59 — Running the Natural Planning Model as a group (John Forrester)

Summary Takeaways

• Recurring projects are best managed with checklists as the backbone, and only distinct or blocking actions tracked as projects, to minimize system overload.
• Reviews—not elaborate reminders or aggressive flagging—are essential for stress-free productivity.
• Natural Planning Model is flexible: Use it as often as clarity and project complexity dictate, including after a project as a learning tool.
• Next actions should be as specific as possible; the right verb nudges you to action.
• Personal adaptation—each practitioner is encouraged to adjust tools and habits (calendar, flags, checklists) to fit work rhythm and preferences.
• And sometimes, trust your intuition on what to do next, as motivation aligns with necessity.

This episode is a practical masterclass in real-world GTD adaptation, filled with participant wisdom and candid stories from GTD veterans and enthusiastic newcomers alike.