Thanks for the link to workflowy. Here’s some thoughts on it.
Problems:
If I use it to keep a todo/projects list, I can’t assign priorities or dates to sort and filter by. (Hashtags aren’t enough for this.)
Can’t have the same item linked to from two different places. It’s a tree, not a graph. I read some people say they’ve exported their brains to workflowy, but your brain is more of a graph than a tree. (Duplication isn’t enough for this, because changes in the duplicate aren’t applied to the original.)
Regardless, it’s definitely better than the mess of text files I’m currently using.
The tagging and searching functionality seems to make it possible to implement the I’m bored and have 20 minutes, tell me what to do function that another commenter talked about. Just tag the relevant subtasks with #nextaction or something, and then search for that tag later.
I also wish it was a graph rather than a tree, best of all via a duplicate* that synced the copies. I deal with dates by making a separate item ‘do X’ and putting it in a list sorted by date. (This would be a better solution if you could have two copies of the item.)
Thanks for the link to workflowy. Here’s some thoughts on it.
Problems:
If I use it to keep a todo/projects list, I can’t assign priorities or dates to sort and filter by. (Hashtags aren’t enough for this.)
Can’t have the same item linked to from two different places. It’s a tree, not a graph. I read some people say they’ve exported their brains to workflowy, but your brain is more of a graph than a tree. (Duplication isn’t enough for this, because changes in the duplicate aren’t applied to the original.)
Regardless, it’s definitely better than the mess of text files I’m currently using.
The tagging and searching functionality seems to make it possible to implement the I’m bored and have 20 minutes, tell me what to do function that another commenter talked about. Just tag the relevant subtasks with #nextaction or something, and then search for that tag later.
I also wish it was a graph rather than a tree, best of all via a duplicate* that synced the copies. I deal with dates by making a separate item ‘do X’ and putting it in a list sorted by date. (This would be a better solution if you could have two copies of the item.)
Hi Yli, Here’s a possible solution for you: A post of mine was featured on Jesse Patel’s WorkFlowy blog a couple of days ago: http://blog.workflowy.com/2014/08/21/using-workflowy-as-a-kanban-calendar/