also, can you sketch out your workflow? @hungrybreadelevato…
also, can you sketch out your workflow? @hungrybreadelevator !todo
Replies
Significantly I added queue. I try to keep my todos and inprogs low.
As I work with knovigator I will scatter todos as bookmarks to come back to. These todos also provide starting points for jumping back into a knovigator thread and continuing my work.
In the workflow thread I will click on the [task tag] thread and open a search where I will collect (by quoting) a few todos from my other quests. I will then try to knock them out. If I can't finish them in one go I will mark them as INPROG instead of [task tag]. I will then remove them from the [task tag] thread and add them (by quoting) into the INPROG thread.
The QUEUE is for keeping track of other Todos if I'm worried I will lose them, but I don't want to get bogged down with a long list so I putt his at the bottom. Similarly WAITING is for things that need to be done but I cannot take action on them yet.
This is all for GTD-esque, but what is neat about knovigator is that I have not put time constraints on this workflow. No deadlines etc. Knovigator is not my planning tool, it is my thinking tool. Thus the speed of time outside of my quests does not matter as much as the speed of my own thoughts as they develop. I don't need for this workflow to be very advanced. I just need a sense of security with the idea that I'm not losing anything. It's all there when I need it.
I think the archive feature and the number indicator for branches will radically change this workflow that I have described above. I probably will quote less because I can use blue number as an indicator of what needs to be done and then archive done things.
!expand
I also love the archive feature because it removes from site but does not delete. This increases the play of knovigator without me having to worry about losing anything.
feature request: what if the blue thread number changed when notes in the thread where archived? I guess I can just delete them, but that would help with a GTD approach to the thread without also deleting data.