From bb6e60a0984287ecb754ebd5275eeee26b8abb79 Mon Sep 17 00:00:00 2001
From: Flancian <0@flancia.org>
Date: Sat, 28 Nov 2020 18:00:26 +0100
Subject: [PATCH] Auto: misc.

---
 getting-things-done.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/getting-things-done.md b/getting-things-done.md
index f680b73b1..3dc7d5dc4 100644
--- a/getting-things-done.md
+++ b/getting-things-done.md
@@ -6,7 +6,8 @@
 - https://hamberg.no/gtd for an intro.
 - The gist of it:
   - Break down tasks. Be specific.
-  - When go through your backlog, like email, you try to either take any needed action immediately (but only if it's short; perhaps set a threshold in seconds, rather than minutes) or classify for later doing.
+  - When go through your backlog, like any inbox (including a "main" one, your base field of operations for executing the GTD algorithms), you try to either take any needed action immediately (but only if it's short; perhaps set a threshold in seconds, rather than minutes) or classify for later doing.
+  - My take: as I can, I try to expand items, breaking them down into simpler actions and tagging them (classifying them) with a greater degree of specificity. This makes the tasks more tractable over time.
   - You classify according to [[time]] and [[context]] for the task of doing. Some example tags:
     - [[next action]], [[next week]], [[some day]], [[office]], [[home]], [[project]].
   - [[next action]] is where the magic happens. At some point something needs to be your [[next action]] to get done :)