This is a fantastic question, and it highlights the exact gap between reading GTD theory and making the "mind like water" workflow happen in the real world. Echoing what others have said about tools just being enablers and the core being the processing logic, I'd like to share my perspective on how support material is actually used during execution.
Following the traditional GTD processing logic, when "stuff" hits your inbox, you first determine if it's actionable. If it's not, it goes straight to Reference. But if it
is actionable, you have to ask the critical question:
"What's the next action?" This is where the real work happens.
When you decide that file X is support material for Project Z, you've essentially only completed the "Organize" phase. In practice, you can't directly "execute" an entire raw document. Support material doesn't magically spoon-feed you the tasks;
you have to process and break it down.
For example, let's say the document outlines the goals, execution processes, and acceptance criteria for a specific outcome. You need to spend time digesting it and extracting a series of concrete Next Actions. When it's time to execute, you refer to your extracted action list, not the whole raw document. Whether you summarize it yourself or use AI to extract the to-do list, this "processing" step is mandatory and cannot be skipped.
Regarding storage and retrieval, my habit is straightforward:
don't hesitate to create dedicated folders.Since most work is digital now, I create a dedicated digital folder for each project. If it's a physical document, I simply get a physical folder for it.For my notes, I personally use a physical notebook, borrowing the "Collection" concept from Bullet Journaling. I dedicate a few pages to a project, writing down
only the distilled core goals, key standards, and milestones. If you prefer digital note-taking apps like Obsidian, the logic is exactly the same: create a dedicated note or page for that project to hold these extracted essentials.
So, when the rubber meets the road, my real-world workflow looks like this:
- I see Next Action Y in my task manager.
- I open the project "Collection" in my notebook (or Obsidian) to quickly review the core standards and requirements.
- If I need deeper details while executing, I use that as a bridge to look up the raw support material in the dedicated project folder (digital or physical).
This "processing" step is the necessary bridge between organizing and executing. Hope this real-world scenario helps clarify things for you!
