Journalist troubles
nzs_finest says:
HI all, wasn't exactly sure whether to post this in 'help or 'tips and tricks' as its not to do with trouble using a feature as such but here goes.
I'm a cadet journalist and have started using rtm in more or less a gtd style but am having trouble with deciding how best to manage my daily work tasks.
As a journalist I have a story list of each of the different matters and events I'm covering for the week.
I started by having a normal list for each story with the overall focus of the piece tagged:story and indiviual 'next actions' as separate tasks tagged with the appropriate designations and locations as prescribed in gtd.
However when I've finished the story I'm left with an empty normal list that I have to delete in my 'weekly review'.
It works in a sort of clumsy round-about way but if anyone is familiar with gtd and underany of the above I'd appreciate any advice.
Cheers
I'm a cadet journalist and have started using rtm in more or less a gtd style but am having trouble with deciding how best to manage my daily work tasks.
As a journalist I have a story list of each of the different matters and events I'm covering for the week.
I started by having a normal list for each story with the overall focus of the piece tagged:story and indiviual 'next actions' as separate tasks tagged with the appropriate designations and locations as prescribed in gtd.
However when I've finished the story I'm left with an empty normal list that I have to delete in my 'weekly review'.
It works in a sort of clumsy round-about way but if anyone is familiar with gtd and underany of the above I'd appreciate any advice.
Cheers
Replace "story" by the more generic GTD term "project" and I'm doing the same thing...
(but I archive empty lists/projects instead of deleting them, to keep all the completed tasks "together")
Using lists for projects is "advised" in the classic piece on GTD with RTM:
http://blog.rememberthemilk.com/2008/05/guest-post-advanced-gtd-with-remember-the-milk/
(but I archive empty lists/projects instead of deleting them, to keep all the completed tasks "together")
Using lists for projects is "advised" in the classic piece on GTD with RTM:
http://blog.rememberthemilk.com/2008/05/guest-post-advanced-gtd-with-remember-the-milk/
andrewski (Remember The Milk) says:
It sounds like you're asking a pretty common question about how to manage your GTD projects (where your projects are generally stories). You'll find a number of topics in the forums about this is general, but for a quick tip that may help:
I'd suggest (mostly for the sake of avoiding having to delete a list each week) that you arrange your normal lists by GTD context (phone, computer, etc.) and to arrange your projects/stories by tag. You can then use the Task Cloud on the right to click through to each project/story. You could also use Smart Lists (e.g. tag:event) if you want to save a story (in combination with any other properties too: for example, this could be useful for looking at all next actions across stories, e.g. tag:na OR dueBefore:Friday).
Also, if you haven't read it already, Doug Ireton's guest post about GTD on our blog is a great, complete primer to setting up GTD in RTM. :)
Hope this helps!
I'd suggest (mostly for the sake of avoiding having to delete a list each week) that you arrange your normal lists by GTD context (phone, computer, etc.) and to arrange your projects/stories by tag. You can then use the Task Cloud on the right to click through to each project/story. You could also use Smart Lists (e.g. tag:event) if you want to save a story (in combination with any other properties too: for example, this could be useful for looking at all next actions across stories, e.g. tag:na OR dueBefore:Friday).
Also, if you haven't read it already, Doug Ireton's guest post about GTD on our blog is a great, complete primer to setting up GTD in RTM. :)
Hope this helps!