From Obsidian Overwhelm to Clarity: My Journey Clearing the Inbox & Linking Projects to Next Actions (with a little help!)

A

achieve

Registered
Hi fellow GTDers,

Some of you might remember my previous post, "Experiencing Friction with GTD After One Month – Seeking Workflow Optimization Advice." I received so many beneficial suggestions in that thread, and I'm incredibly grateful for the community's input. I wanted to share an update on a recent breakthrough I had implementing GTD more rigorously, specifically using Obsidian with a few key markdown files: gtd-inbox.md, gtd-next-actions.md, my monthly notes for Projects, and a future-maybe.md. I was feeling a bit swamped by everything, but a structured approach made a huge difference. I also had some AI assistance (from Gemini 2.5 Pro) guiding me step-by-step, which was surprisingly effective.

Here’s a bit about the process and what I learned:

1. Tackling the Inbox (gtd-inbox.md):

This was the crucial first step. I was guided to look at only the first item in my inbox and ask the two classic questions:
* "What is it?" (Clarifying the actual 'stuff')
* "Is it actionable?"

This simple, focused approach for each item was key.
* If it was actionable and could be done in under 2 minutes, I did it right then and there. For example, a quick task like "drafting a short memo" got done.
* If it was actionable but took longer, it became a Next Action and went onto my gtd-next-actions.md list. For instance, "Archive audio recordings" (which involved listening, naming, and filing) went here.
* If it was a bigger undertaking requiring multiple steps (like "Get a multi-stage approval document fully signed and archived"), it was identified as a Project and added to my Project list (in my monthly notes). The very next physical action for that project then went onto my gtd-next-actions.md.
* If it was something I was waiting on someone else for (e.g., "Friend to buy batteries"), after clarifying my action (which was to follow up), it went to my "Waiting For" list.

Processing the inbox this way, item by item, eventually led to the satisfying feeling of an empty inbox! I even did a "mind sweep" to capture any other lingering thoughts and processed those too.

2. Connecting Projects to Concrete Next Actions:

This was a major 'aha!' moment. I was then guided to review my Project list. For every single project, I had to define a clear, physical Next Action that would move it forward.
* For example, a project like "Select and order new doors" (where I was stuck between two suppliers) had the Next Action: "Design a detailed spec sheet/RFQ to send to both door suppliers for comparable quotes." This NA was then added to my gtd-next-actions.md under the relevant context (e.g., @Computer).
* Another project, "Address a critical issue flagged by senior management," which I admittedly had been avoiding, was broken down into three concrete Next Actions that I added to my list under @Company.

This process of ensuring every project has a live Next Action felt like giving each project a clear "on-ramp." If a project doesn't have a defined Next Action, it's just a wish or a source of stress.

3. Understanding the Dynamic Duo: Projects & Next Actions:

The biggest takeaway was understanding the living, breathing relationship between the Project list and the Next Actions list. It’s not a one-time setup. As I complete a Next Action for a project, I must immediately (or during my Weekly Review) define the new Next Action for that project. It's like there's an invisible thread connecting them, ensuring continuous momentum. If this thread breaks (i.e., a project has no NA), the project stalls.

It was a focused effort, and I spent a good amount of time on this, but the clarity and sense of control I have now is immense. Even though my gtd-next-actions.md list is long (with contexts like @Workstation, @SpecificLeader, @Home), I know what needs doing and where/when I can do it.

Has anyone else had a similar experience when systematically linking all their projects to tangible next actions? I'd love to hear your thoughts and any tips you have for maintaining this clarity, especially during busy weeks. Please feel free to share your own experiences!

Thanks for reading!

 
achieve said:
Has anyone else had a similar experience when systematically linking all their projects to tangible next actions? I'd love to hear your thoughts and any tips you have for maintaining this clarity, especially during busy weeks. Please feel free to share your own experiences!
Click to expand...
Absolutely. When I stopped doing project notes (with every next action I could think of) and just listing the outcomes I wanted on a project list, and the very next action on a context list, my system became less convoluted. I was able to stop tagging and moving actions. And I stopped having next actions on a list that I couldn't possibly do. Because they were not my very next action. I'm not sure what you mean by linking though. If by this you mean tagging or linking notes together or having a "tree" hierarchy or some sort of complex folder system , I don't do that at all.
 
fooddude said:
Absolutely. When I stopped doing project notes (with every next action I could think of) and just listing the outcomes I wanted on a project list, and the very next action on a context list, my system became less convoluted. I was able to stop tagging and moving actions. And I stopped having next actions on a list that I couldn't possibly do. Because they were not my very next action. I'm not sure what you mean by linking though. If by this you mean tagging or linking notes together or having a "tree" hierarchy or some sort of complex folder system , I don't do that at all.
Click to expand...
Hi! What I mean by "linking" isn't about creating complex connections like elaborate tagging systems or hierarchical folders. Instead, it’s a simple, dynamic process: by looking at the project list, I use my brain to manually generate the single next action for each project, one by one—and I only write down that exact step, just like you mentioned before.

The "implicit link" comes from immediately updating each project’s next action as soon as the previous step is done. It’s not about pre-building complicated relationships between tasks; it’s about keeping the project list alive through active, real-time reflection—no fancy systems, just a clear, updated next step for whatever’s in front of me.

This way, the "connection" is organic and straightforward, driven by my thinking process rather than rigid structures. Does that better capture what I mean?：）
 
achieve said:
Has anyone else had a similar experience when systematically linking all their projects to tangible next actions?
Click to expand...

There's a treasure trove of thoughts on the subject from many people on the forums. I won't rehash a lot of it but for example, you will find many perspectives in a thread such as https://forum.gettingthingsdone.com...projects-experiment-which-team-are-you.18567/

I find linking next actions to projects key to successfully getting a project done. For many of the same reasons you described and experienced. It's a very useful mechanism to prevent or notice projects that are not making constant forward momentum.
 
Matt_M said:
I find linking next actions to projects key to successfully getting a project done.
Click to expand...
when I create a project tag in my list manager, it allows me to easily complete the project part of the weekly review and when I review next actions, tagging can happen when it belongs to a project and I realize I missed tagging it.

it's more an efficiency of working with projects and a think about it once (this belongs to this project so I tag it), kind of thing.
Completeness is not the point. Registering thoughts for future reference is the benefit.

Clayton

You only need to have a thought once and then you capture it, unless you like having that thought. - David Allen's inexact AI quote fountain.
 
Matt_M said:
There's a treasure trove of thoughts on the subject from many people on the forums. I won't rehash a lot of it but for example, you will find many perspectives in a thread such as https://forum.gettingthingsdone.com...projects-experiment-which-team-are-you.18567/

I find linking next actions to projects key to successfully getting a project done. For many of the same reasons you described and experienced. It's a very useful mechanism to prevent or notice projects that are not making constant forward momentum.
Click to expand...

Thank you for your reply! It seems the link requires specific permissions to access, as the page shows "You do not have permission to view this page or perform this action." Could you share the full title of the thread or any relevant keywords that might help locate public discussions on the topic? Appreciate your help!
 
You must log in or register to reply here.
Top