Processing AI

Mindfulcraig

Registered
I first read "Getting Things Done" (GTD) when it was released in 2001, and before that, I had consumed the cassette tape set on Managing Actions and Projects, which was the precursor to GTD. One idea that resonated with me was the concept of "open loops" and how identifying and objectifying everything on our minds can relieve mental overload.

I have explored many ways that AI could assist with GTD, but the main ideas typically revolve around automating the weekly or daily review or using AI for mind-dumping, etc. As a regular and mostly enthusiastic user of AI tools, I’ve started to notice that the low friction associated with initiating new projects, exploring interests, and brainstorming ideas can lead to an exponential number of "open loops" scattered across various AI platforms.

While some of this may be due to my ADHD brain, I believe it affects non-ADHD individuals as well. Many of the outputs from my AI interactions are likely disposable, but I’m realizing that if I don’t process them with some rigour, they will continue to occupy mental bandwidth.

I'm curious about the approaches others have adopted to capture and process AI outputs so they can clear their minds of these open loops.
 
I am using AI for my programming work, and I find it very good for suggesting things and analysing large amounts of text (usually the codebase I am working on). I find it incredibly useful for this sort of work. It generally gets me to where I would have gotten to myself much more quickly. Often it finds some nuance that I might have overlooked.

I ask it to generate code for me and sometimes to write the odd report. It is certainly fast at these, but I would not say it is particularly good. The exception is things where I havle little knowledge or skill. For example using a code library that I am not familiar with is much quicker, easier, and better with AI.

When I ask AI for code recommendations, what it comes up with is usually questionable and often bad. This is for low stake things like writing some code in a project. I won't trust it with these decisions and the idea of trusting it with life decisions terrifies me.

In summary, for computer code work (and I expect for other knowledge work): AI is excellent at analysing and inspiring; it is fast but mediocre at doing; and it is dangerous for making important decisions.
 
To be honest, it's always been the case that you can put too many things into your system if you're not careful. I'm sure we've all experienced going to an inspiring away day, conference or brainstorming session, and coming back with 100 new ideas, only to sit there 3 weeks later looking at our Project list and thinking "Maybe this wasn't such a good idea after all". Using AI to automate/semi-automate input makes it easier to over generate work, but its still the same problem.

I'd say there's 2 things really, and they're as old as the system itself - run everything through your inbox, and keep up with your weekly reviews.

Part of inbox processing is about the mature assessment of whether its really important enough to do. And the weekly review includes a second run of the same idea, you pragmatically assess whether it’s really worth this project sitting on your list, and how long you leave it there with no progress before you simply retire the idea and move on.

There is some nuance about how we might pre-vet AI output before it gets into our Inbox, using a second run of AI. The same way we create filters for email to avoid Inbox overload. But fundamentally we still have to grapple with the decisions of whether or not something belongs in our system.
 
My approach has been to use AI “within” GTD and not “for” GTD. Use it to summarize and clarify items that are in my system. Use it as an assistant, rather than a manager. All those queued articles languishing in my system, have AI write me a one page summary of each, boom, points on the board. Rather than adding a layer(s) of complexity to the problem, use it to simplify and debulk things a bit.
 
I can relate to what you're describing. The low friction of AI makes it dangerously easy to generate new ideas, new projects, and new "what ifs" – and before you know it, your system is overflowing with open loops that never quite settle.

But here's the thing: I don't think this is fundamentally an AI problem. It's the same old human tendency – the compulsion to get everything done – just turbocharged by a tool that never runs out of suggestions. Whether the inputs come from a brainstorming session, a conference, or a ChatGPT conversation, the core issue is the same: we capture because we feel we should do something with every idea, and that creates mental friction.

In my own experience (and I've posted about this before – link below), the Zeigarnik effect is very real. Even when I write things down, they don't truly leave my mind. Once I see an unfinished item in my inbox or on a list, I get that nagging "why haven't I done this yet?" feeling. And when I'm sleep‑deprived, my judgment and willpower drop – I become less able to triage, less willing to delete, and the list just grows heavier, like proof of your own inadequacy.

AI outputs are especially tricky because they often sound reasonable. That makes it even harder to discard them.

My current coping strategy is simple: more single‑threading, strict 2‑minute rule for immediate tasks, and physical isolation – for example, I keep app‑related notes in a separate file and simply don't open it when I'm not actively working on that project. It reduces the constant background noise. And above all, I've learned that rest and focus come before any productivity system.

This is exactly the kind of loop I discussed in an earlier thread – it's not about the tool, it's about our relationship with unfinished business. Here's that post if you're curious:
christophe.portier

Thread 'GTD and impact on mental health... negative?'

I've been practicing the GTD method for several years now, and my professional life greatly benefits from it: efficient, reliable for my colleagues, able to prioritize in often chaotic contexts, I now only function through this wonderful methodology.

On the other hand, I've been sleeping poorly for several months.
And I'm starting to wonder about this angle of the GTD method that might be causing these insomnias: all day long, my brain is on the lookout for any thought to capture and record, as soon as I have a free moment my inbox to (perpetually) process or my well-organized lists make...
 
You must log in or register to reply here.
Top