Long post warning:
TLDR;
The minimal viable product needs to start small with a simple ToDo app, because most users don’t need a full blown GTD app right from the start. … But there has to be “no friction” in the underlaying data-structure, if it needs to grow.
hmmm, I think that estimation is not right. Neither in complexity nor in the amount of time needed to make it a “product” that users would want to pay for.
IMO the UX has to be the “killer feature” …
At David Allen gives away his design for the Ultimate GTD App (GTD Summit 2019) - YouTube David Allen pointed out, that there where 2 serious attempts to implement the “perfect GTD” app … Both “failed”. …
The past attempts probably failed, because “cramming” everything into 1 “hardcoded” app did blow up the complexity to infinity. … (I’m exaggerating here
IMO the key point to success is the underlaying “data structure” that connects all the different elements together. As shown in this thread it seems everyone is using at least 3 different apps to get stuff done, because no single app will do the job.
Also user needs are different. eg:
If you are new to Getting Stuff Done workflows you’ll probably start with a simple ToDo app, so Projectify is a professional looking starter … but
After some time that’s not good enough anymore … So you may want more, but it should be possible to carry the “existing” data with you, because a lot of value was already created.
May be there should be a Contacts addOn so you can speed up contacting people.
But …
if you collect data to prepare a PhD theses and want to define some “due dates” a Callendar addOn in combination with a BibTex addOn may be more important
… and so on. …
IMO the GTD concept is flexible enough to handle both usecases,
IMO TW tiddlers are flexible enough to handle both usecases
but none of the existing TW plugins are able to handle that out of the box, because most of the community pluigns are not compatible enough. Neither in UI, nor in the underlaying data structure.
As I did read in this thread the existing TW implementations are also “not good enough”, mainly because the have been written by devs, that did develop them for their own preferred usecases and not to build the “perfect GTD elements”.
@ludwa6 linked a workflow image at: Any new GTD plug ins available other than GSD5, Cardo and Projectify - #43 by ludwa6 which looks “simple” on the first view.
Top left it contains 1 elements from “Collect” to “Do” and it shows point 2 & 3 in more detail. The funny thing here is, that every single element from 1 to 5 is a complete app for itself.
eg: Collect. … tasks for “a project” which is the orange bubble in the details workflow
- Some users may want to use an “outliner” to collect input for the “inbox”
- I personally would like to use a mind-map (In the video David Allen also mentioned a MM, which can be a complete app on itself)
eg: Process - Organize details
- Shows a workflow using some terms form GTD … but
- I can tell you an implementation of the Eisenhower principle can do that too.
It will be possible to create both workflows in TiddlyWiki … but
I think the underlaying data-structure has to be identified first. The “killer UX” I did mention above has to stand on a solid base concept that has the “big picture” in mind. … where
The minimal viable product needs to start small with a simple ToDo app as 1 component, because most users don’t need a full blown GTD app right from the start. … But there has to be “no friction” if you need to grow.
Just some thoughts.
PS: I’ll probably move this post and comments into its own thread…