Software features often are a lie… let me elaborate on that.
This post is a bit off the topic of Drafts. But I am sure that some of the community members are interested in this topic - please tell me if I am right or wrong.
I was reading through Zettelkasten Usage: Analog or Digital - #10 by guleh and thought that this might interesting for some peoples to think about with me and other GTD-fans.
I have to say that Drafts is one of this apps (or even applications) that really stands out and that is NOT fitting into the category I describe here.
It has been over twenty year since I read the GTD-book by David Allen. Sadly David himself was using and utilizing Lotus Notes during his first decades of work life and therefore lived completely in his own world without generating a official GTD software.
Up to my knowledege he still is hesitant to state on those claims to GTD made from many software and keeps repeating in his book about the core feature “List Managers”.
But hence name dropping is cool - as I am guilty myself of many times - and GTD is hip, nearly every task manager claims to be GTD. I mean in a sense they are because GTD is the short form for “getting things done” and a task manager helps you getting things done - right?
But GTD in David Allen’s definition is more. A toolset of good and simply ideas combined to a powerful system. The 2 minute rule for example is a very interesting concept that I try to teach my children in any context - I even make a 5 min rule out of it.
what is the 2-minute-rule
If something is done in 2 minutes or less.
Do it right away - to manage it inside your system will take more time.
I find my systems to be more complex why I stocked up to 5 minutes
So does every GTD-stating task-manager not implementing the two minute rule lie?
GTD as the GTD-system is a very great definition of how to organize tasks and projects and not get lost in the daily and weekly walk with them.
David states this as his “trusted system”. And the quest for a trusted system is often a very hard and long one. Interestingly I found
Things on iOS to be a very good (in a sense of OK) system - but this only since i totally wracked their implementation of objects - more about that later.
As a software-engineer working in a team and a love to definition and philosophy I found that:
Software is sum of the frozen thoughts of a/the developer(s)
Therefore it is not the way of implementing it but a way. And if your way of thinking matches up with the way of thinking of the developer you can use the software. If not you might be able to bend your thoughts into the software or (sometimes) bend the software to your way of thinking.
Lets do an example:
- GTD defines tasks that you need to do
- GTD sorts that tasks inside of contexts to do them in batches and to filter them if the context does not apply
- GTD defines a task as a step in a project - something not get to a goal or outcome by more than one step
Not to the implementation:
- Things defines tasks and sorts them in projects - nice and good
- Things defines tags to be maybe used as contexts
- Things does not give a simple or top-level way to access those contexts
- But it gives you many layers to set start and due dates - nothing a task in GTD is mentioned to have
If you stop and think a moment about GTD and your daily needs this sorting of Things is kind of strange.
To put things inside a project is a logical step.
But not to put them in context that will help you daily access it later is quite against GTD that I only can shake my head about it.
So even Things - one software that I trust to be my GTD-system - has pitfalls as deep and wide as that basic GTD-concept.
So what did I do to continue using Things?
- I sort my tasks in Things in contexts (formerly known as Things projects - but now never used as such from me inside my contexts areas)
- I also create projects (from projects) and put reference information, ideas and goals into them and review them regularly
- but my tasks in the contexts are not connected to the projects in my project and someday maybe lists
Is this a problem?
Not for me. I found the sorting in contexts to be much more helpful to really get things done.
But please decide for yourself!
The strange thing about this is, that I did that task-in-project-sorting for years and not getting the hurdle it created for me.
The connection between a task and a project is still there - not in the software but in my brain.
I do not need the connection in the software. I need the software to help me remember the tasks in the context and not the task depending on the project.
A complete different trail is the difference between tasks (actionable things) and ideas.
But this will not be part of this topic.
So my (kind of harsh) statement is that software (or the developers) are lying about there GTD-ness of software. Or even replace the feature of GTD with other aspects. (e.g. Zettelkasten…)
I would love to read your opinion on this…
Did you find the holy grail of GTD-software?
Did you have similar moment of - what am I doing?