The Truth About GTD Software Tools

I just found a David Allen email newsletter I received on this topic back on 7/3/19. Subject line: David Allen on the Best Software for GTD. Here’s the link to that newsletter piece, in which he posts his actual handwritten notes on his ideas, and even invites potential developers to contact his CTO directly via email:
 
I’ve applied Lean Six Sigma principles to my GTD setup and reached something quite close to what I’d call a personal airtight system.
I'm really curious about what materials you used to learn Lean Six Sigma principles, as I'm not very familiar with it yet. Could you recommend any books or videos?

Maybe like these?
《The Machine That Changed the World》 – James P. Womack, Daniel T. Jones, et al.
《Toyota Production System》 – 大野耐一(Taiichi Ohno)

Thank you!
 
Last edited:
I'm really curious about what materials you used to learn Lean Six Sigma principles, as I'm not very familiar with it yet. Could you recommend any books or videos?

Maybe like these?
《The Machine That Changed the World》 – James P. Womack, Daniel T. Jones, et al.
《Toyota Production System》 – 大野耐一(Taiichi Ohno)

Thank you!
I actually went through a full Lean Six Sigma Black Belt curriculum at GE Healthcare—it ran over the course of a year and concluded with a rigorous exam. That experience really shaped how I approach process improvement. Toyota House of quality was part of the curriculum.

From where I sit, Lean is quite intuitive—it’s largely common-sense principles around eliminating waste and optimizing flow. Six Sigma, by contrast, leans heavily into probabilities and statistics, which can feel quite dense at first.

If you’re just embarking on this journey, a great place to begin is a quick read of the Wikipedia entries on Lean and Six Sigma—they’re concise, free, and provide a solid conceptual foundation.

I also used an Excel-based toolkit called Systems2win, which provided a suite of Lean Six Sigma templates to support DMAIC projects—from SIPOC charts and Pareto diagrams to FMEA, control charts, and more. It’s especially useful for visualizing and managing process improvement workflows right inside Excel. You can explore it here: Systems2win Lean Six Sigma tools - https://www.systems2win.com/solutions/SixSigma.htm
 
I actually went through a full Lean Six Sigma Black Belt curriculum at GE Healthcare—it ran over the course of a year and concluded with a rigorous exam. That experience really shaped how I approach process improvement. Toyota House of quality was part of the curriculum.

From where I sit, Lean is quite intuitive—it’s largely common-sense principles around eliminating waste and optimizing flow. Six Sigma, by contrast, leans heavily into probabilities and statistics, which can feel quite dense at first.

If you’re just embarking on this journey, a great place to begin is a quick read of the Wikipedia entries on Lean and Six Sigma—they’re concise, free, and provide a solid conceptual foundation.

I also used an Excel-based toolkit called Systems2win, which provided a suite of Lean Six Sigma templates to support DMAIC projects—from SIPOC charts and Pareto diagrams to FMEA, control charts, and more. It’s especially useful for visualizing and managing process improvement workflows right inside Excel. You can explore it here: Systems2win Lean Six Sigma tools - https://www.systems2win.com/solutions/SixSigma.htm
Wow, I'm really impressed and genuinely admire your learning journey!
I'll definitely start by reading the Wikipedia entries you mentioned.
As for tools like Systems2win and some of the terms you brought up, I’m not fully familiar with them yet—they’re new to me, and I’ll need to take some time to learn and understand them better.
Thank you so much for sharing!
 
Wow, I'm really impressed and genuinely admire your learning journey!
I'll definitely start by reading the Wikipedia entries you mentioned.
As for tools like Systems2win and some of the terms you brought up, I’m not fully familiar with them yet—they’re new to me, and I’ll need to take some time to learn and understand them better.
Thank you so much for sharing!
Thanks a lot for your kind words!
Yes, you’ll bump into a few acronyms at the start — but they’re really just shorthand for structured thinking. For example:
  • DMAIC (Define, Measure, Analyze, Improve, Control) — the classic cycle you’d go through when working on an existing flow.
  • SIPOC (Supplier, Input, Process, Output, Customer) — a great way to step back and see the high-level interactions between entities.
  • FMEA (Failure Mode and Effects Analysis) — a structured toolkit to tackle problems and risks; often complemented by techniques like the fishbone (Ishikawa) diagram.
And ultimately, the north star of all this is DFSS (Design for Six Sigma). That’s when companies design products or services from scratch with quality in mind, ensuring that from input to output, the process is so robust that the number of defects is driven down to the famous “six sigma” level — about 3.4 defects per million opportunities.

Now, just imagine if we were running our GTD workflows at Six Sigma levels. That would mean that for one million opportunities for error in our ecosystem (every capture, clarify, organize, review, execute step), we’d tolerate no more than 3.4 defects. Be my guest!

With this in mind, that’s exactly why I’ve been developing supporting tools around my GTD setup — to systematically reduce friction and eradicate defects. One concrete example is the delegation flow I’ve been building, which I’ve copied below to give you a sense of how this plays out in practice.

1755796977620.png
 

Attachments

I actually went through a full Lean Six Sigma Black Belt curriculum at GE Healthcare—it ran over the course of a year and concluded with a rigorous exam. That experience really shaped how I approach process improvement. Toyota House of quality was part of the curriculum.

From where I sit, Lean is quite intuitive—it’s largely common-sense principles around eliminating waste and optimizing flow. Six Sigma, by contrast, leans heavily into probabilities and statistics, which can feel quite dense at first.

If you’re just embarking on this journey, a great place to begin is a quick read of the Wikipedia entries on Lean and Six Sigma—they’re concise, free, and provide a solid conceptual foundation.

I also used an Excel-based toolkit called Systems2win, which provided a suite of Lean Six Sigma templates to support DMAIC projects—from SIPOC charts and Pareto diagrams to FMEA, control charts, and more. It’s especially useful for visualizing and managing process improvement workflows right inside Excel. You can explore it here: Systems2win Lean Six Sigma tools - https://www.systems2win.com/solutions/SixSigma.htm
After reading your post, I took the time to seriously explore the philosophy of Lean Six Sigma—especially the DMAIC framework. I then spent over half an hour discussing this topic with Gemini 2.5 Pro.

I’ve made a preliminary discovery: DMAIC, in simple terms, starts with clearly defining a problem or need, then uses data for objective analysis to identify the root cause, implement improvements, and establish control to sustain the results. What I found is that this is an excellent approach for seriously tackling any issue. By combining data analysis with problem-solving, it connects seemingly unrelated data points, transforming previously underutilized lagging indicators into meaningful insights.

For example, I’ve decided to use DMAIC to start with my sleep—I want to understand what truly affects it. This feels like exactly the kind of situation where the concept of "leading indicators" you mentioned can really shine. I’ve had years of sleep data from my smartwatch, but until now, that data just sat unused, not delivering real value. With DMAIC, however, I started looking at it differently. I began correlating my sleep data with other factors like my body temperature and room temperature before bed, and the time I stop using screens each night. This could allow me to discover insights such as: “Every 30 minutes earlier I stop using my phone before bed, my deep sleep increases by about 10 minutes.” Just thinking about it gets me excited!

Last night, I pulled out a notebook and created a simple paper table. Each row records one day’s pre-sleep conditions: whether I stopped screen use before 10 p.m., my body temperature, room temperature, total sleep duration, and the next evening, I’ll rate my energy level that day on a scale from 1 to 5 (with 5 being the best).
Right now, this table format hasn’t been fully integrated into my GTD yet. But I’ll keep experimenting over the coming days to figure out the best way to weave it into my existing system.

Do you think I’ve at least grasped the basics of DMAIC? :) Thanks so much for explaining the key concepts of Six Sigma and giving me great advice on how to learn them.
 
Last edited:
SIPOC (Supplier, Input, Process, Output, Customer) — a great way to step back and see the high-level interactions between entities.
Maybe I can use SIPOC this way:
  • Suppliers: My smartwatch and I (tracking behaviors)
  • Inputs: Body temp, room temp, screen time before bed
  • Process: Collect data → Analyze patterns → Adjust habits
  • Output: Better sleep quality and higher daily energy levels
  • Customer: Myself the next day :D
I find DMAIC, SIPOC, and FMEA (along with its SOD and RPN) quite elegant and insightful. Their combination is worth exploring slowly and thoughtfully.
 
After reading your post, I took the time to seriously explore the philosophy of Lean Six Sigma—especially the DMAIC framework. I then spent over half an hour discussing this topic with Gemini 2.5 Pro.

I’ve made a preliminary discovery: DMAIC, in simple terms, starts with clearly defining a problem or need, then uses data for objective analysis to identify the root cause, implement improvements, and establish control to sustain the results. What I found is that this is an excellent approach for seriously tackling any issue. By combining data analysis with problem-solving, it connects seemingly unrelated data points, transforming previously underutilized lagging indicators into meaningful insights.

For example, I’ve decided to use DMAIC to start with my sleep—I want to understand what truly affects it. This feels like exactly the kind of situation where the concept of "leading indicators" you mentioned can really shine. I’ve had years of sleep data from my smartwatch, but until now, that data just sat unused, not delivering real value. With DMAIC, however, I started looking at it differently. I began correlating my sleep data with other factors like my body temperature and room temperature before bed, and the time I stop using screens each night. This could allow me to discover insights such as: “Every 30 minutes earlier I stop using my phone before bed, my deep sleep increases by about 10 minutes.” Just thinking about it gets me excited!

Last night, I pulled out a notebook and created a simple paper table. Each row records one day’s pre-sleep conditions: whether I stopped screen use before 10 p.m., my body temperature, room temperature, total sleep duration, and the next evening, I’ll rate my energy level that day on a scale from 1 to 5 (with 5 being the best).
Right now, this table format hasn’t been fully integrated into my GTD yet. But I’ll keep experimenting over the coming days to figure out the best way to weave it into my existing system.

Do you think I’ve at least grasped the basics of DMAIC? :) Thanks so much for explaining the key concepts of Six Sigma and giving me great advice on how to learn them.
Cool stuff. Absolutely, with this approach we can be parachuted anywhere there is a process to scrutinize, be at work, at home…
 
Good discussion on (part of) an old video.
I suggest to go back to the basics to see what is possible, what not and why.
(some philosophical intro before the SW stuff)

1. there was (is and will be) a universal organizing process behind EVERY doing. It was so before scribd was invented, and it will be so when robots will (eventually replace humans).

2. The sequential process: 1. getting input - 2. evaluating it, if something needs to be done, then (3. postponing it, 4. selecting it, and then) DOING it.

3. until recently (last 50 years) this process was of low intensity, DOING was the limiting factor/bottleneck of human existence, nobody cared much about the org process, it was done intuitively (mostly during doing - manual- work). it was mostly clear what needs to be done next.

4. But progress made DOING less tedious AND intensified the first step of organising process (and forced people doing at least the second)

5. "Organizing doing" became the bottleneck. the intuitive way of organizing became insufficient.

time management came about. Usually targeting PARTS of the org process (nobody saw the whole process...)

then came David A. and described the WHOLE org. process and added a fifth step (if there is moch stuff deferred, much will become obsolete, and regular review is necessary). Hence GTD is simply the complete set of principles of "organizing life".

Please note that despite of the popular notion, GTD is NOT ABOUT DOING.
It is about Getting to doing (the ENGAGE step is only SELECTING the best option to be done...)
GTD never deals with how to garden, make surgery or plumbing. It deals with the common, organizing part of ALL these.

Now to the SW:
1. Capturing is best aided by tools, the question is only whether ALL sources can be automatically routed to a reasonable set of Inboxes (if you have seen Black Mirror - it might come - as a "life recorder"). Not yet there.

2. Clarifying is done by our brain, with our COMPLETE context in mind. If AI will know myself better that I do - it can do my clarification.
(and for simple things it can try even now, under my supervision. It can suggest an action for the email, but is does not know that I met my boss at the cofee machine and that chenged context). For now, I would not TRUST it the full Clarification.

3. This is the easiest part - calendar and lists can be implemented in plenty of tools since decades - but with the limitations given in point 2

4. review - AI can give suggestions, or open ended questions to facilitate stuff

5. engage (= select) can be partially facilitated by proper questions and supprted with checklists.

6. All higher horizons ("my map of life") can be included in a SW as reference (mindmaps, lists, whatever personal format preference you have, even a simple word doc is OK). AI/SW can aid with questions - but I think the THINKING about these will happen in our brains for a long time

maybe you have seen the so far best attempts on "full GTD systems": IQTELL and ctrlAlpha - unfortunately both discontinued for the same reason.
Money and
Data Privacy - routing ALL possible inputs into its universal inbox (plenty of APIs, access rights to everything, etc...)
there are ongoing attempts too - will fail similarly.

-----
this is the state of stuff now (as I know of). :)
 
Top