Comments on: Super-Charge Remember The Milk With Smart Lists and Tags http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/?utm_source=rss&utm_medium=rss&utm_campaign=super-charge-remember-the-milk-with-smart-lists-and-tags Increasing Your Quality of Life with Social Media and Web 2.0 Thu, 12 Jan 2012 17:17:00 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: web design London http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-10786 web design London Tue, 01 Nov 2011 19:13:00 +0000 http://sheenonline.biz/?p=46#comment-10786 Very nice setup. I actually changed mine (static lists with smart lists for context to yours which is more versatile. One question: what do you do with (project-) tasks which are not next actions.  Very nice setup. I actually changed mine (static lists with smart lists for context to yours which is more versatile. One question: what do you do with (project-) tasks which are not next actions. 

]]> By: Peter Myers http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-10195 Peter Myers Mon, 11 Oct 2010 11:18:00 +0000 http://sheenonline.biz/?p=46#comment-10195 Hello. I have started using the RTM format recently and I love it. I am always looking to find the best ways of doing things, but I can't see the benefit of using Tags over adding tasks to lists. For instance, I will set up a project and when writing a new task just use "#projectName" to push it to that tab. Can you explain why tags are more efficient than this? thanks P Hello.
I have started using the RTM format recently and I love it. I am always looking to find the best ways of doing things, but I can’t see the benefit of using Tags over adding tasks to lists.

For instance, I will set up a project and when writing a new task just use “#projectName” to push it to that tab.

Can you explain why tags are more efficient than this?

thanks

P

]]> By: Rahsheen http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2758 Rahsheen Sun, 03 Jan 2010 21:03:12 +0000 http://sheenonline.biz/?p=46#comment-2758 The dot isn't absolutely necessary for the smart list names<br>themselves. I just did it that way for consistency, I guess. The dot isn't absolutely necessary for the smart list names
themselves. I just did it that way for consistency, I guess.

]]> By: RonnyO http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2757 RonnyO Sun, 03 Jan 2010 20:13:29 +0000 http://sheenonline.biz/?p=46#comment-2757 This is awesome. But why do I need the "." prefix? Seems like you never use normal tags, without prefixes. The other ones keeps contexts and statuses nicely apart from the project list, but then projects are sorted alphabetically anyway, so why do I need that dot?<br>Thanks. This is awesome. But why do I need the “.” prefix? Seems like you never use normal tags, without prefixes. The other ones keeps contexts and statuses nicely apart from the project list, but then projects are sorted alphabetically anyway, so why do I need that dot?
Thanks.

]]> By: Rahsheen http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2661 Rahsheen Fri, 18 Dec 2009 20:23:40 +0000 http://sheenonline.biz/?p=46#comment-2661 Actually, every task should have a context. That's how I keep them<br>from getting lost. I actually place contexts and projects on the same<br>level as far as keeping the system water tight. For instance, in the<br>example you post, all of these tasks would be tagged with<br>".drinkcoffee" as their project, which would keep them out of the ugly<br>filter. The same goes for any task that actually has an @context.<br><br>As far as misspelling stuff, I take heavy advantage of RTM's<br>auto-complete. Even if I know what tags I want, I click them off from<br>the auto-complete drop down list. When I'm on the go adding tasks via<br>email and such, I don't usually bother trying to tag them at that<br>time, I just wait until I get back to a browser (I don't have the net<br>on my phone) so that I can tag them properly. Creating the tasks in<br>the actual smart list where they belong is another fail-safe. :) Actually, every task should have a context. That's how I keep them
from getting lost. I actually place contexts and projects on the same
level as far as keeping the system water tight. For instance, in the
example you post, all of these tasks would be tagged with
“.drinkcoffee” as their project, which would keep them out of the ugly
filter. The same goes for any task that actually has an @context.

As far as misspelling stuff, I take heavy advantage of RTM's
auto-complete. Even if I know what tags I want, I click them off from
the auto-complete drop down list. When I'm on the go adding tasks via
email and such, I don't usually bother trying to tag them at that
time, I just wait until I get back to a browser (I don't have the net
on my phone) so that I can tag them properly. Creating the tasks in
the actual smart list where they belong is another fail-safe. :)

]]> By: Markus http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2660 Markus Fri, 18 Dec 2009 16:49:00 +0000 http://sheenonline.biz/?p=46#comment-2660 OK we seem to have a different understanding about task status<br><br>In .drinkcoffee<br>-make coffee<br>-take milk from fridge<br>-pour coffee<br>-establish your own coffeeshop<br><br>for me "take milk" is not -someday and it's not -next. I'd call "establish coffeeshop" -someday because it will be really done someday. "Take milk" is also not -waiting because this would produce too many tasks on my waiting list (actually would be 250!)<br><br>So quintessence seems to be: <br>-to get the system waterproof every task must have a status. Otherwise tasks could be missed. Therefore I need something like -later. I better not check tagContains:- to be sure status is valid. Better (but less "dynamic"): tag:-next OR tag:-waiting.... <br>-Further every task that is next needs a context. And it needs to have a valid context which is not sure using the above smartlist, right? I already have a check that searches -next tasks not being on a contextlist <br>-the last chance to loose tasks is wrong spelling of project tags. I actually don't have an idea how to catch these. So I have to be carefull with the .project tags (e.g. only assign these by entering the tasks directly into contextlists (does move to smartlist change tags? This would be marvellous! I'll test it) OK we seem to have a different understanding about task status

In .drinkcoffee
-make coffee
-take milk from fridge
-pour coffee
-establish your own coffeeshop

for me “take milk” is not -someday and it's not -next. I'd call “establish coffeeshop” -someday because it will be really done someday. “Take milk” is also not -waiting because this would produce too many tasks on my waiting list (actually would be 250!)

So quintessence seems to be:
-to get the system waterproof every task must have a status. Otherwise tasks could be missed. Therefore I need something like -later. I better not check tagContains:- to be sure status is valid. Better (but less “dynamic”): tag:-next OR tag:-waiting….
-Further every task that is next needs a context. And it needs to have a valid context which is not sure using the above smartlist, right? I already have a check that searches -next tasks not being on a contextlist
-the last chance to loose tasks is wrong spelling of project tags. I actually don't have an idea how to catch these. So I have to be carefull with the .project tags (e.g. only assign these by entering the tasks directly into contextlists (does move to smartlist change tags? This would be marvellous! I'll test it)

]]> By: Rahsheen http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2645 Rahsheen Fri, 18 Dec 2009 13:23:40 +0000 http://sheenonline.biz/?p=46#comment-2645 Actually, every task should have a context. That's how I keep them<br>from getting lost. I actually place contexts and projects on the same<br>level as far as keeping the system water tight. For instance, in the<br>example you post, all of these tasks would be tagged with<br>".drinkcoffee" as their project, which would keep them out of the ugly<br>filter. The same goes for any task that actually has an @context.<br><br>As far as misspelling stuff, I take heavy advantage of RTM's<br>auto-complete. Even if I know what tags I want, I click them off from<br>the auto-complete drop down list. When I'm on the go adding tasks via<br>email and such, I don't usually bother trying to tag them at that<br>time, I just wait until I get back to a browser (I don't have the net<br>on my phone) so that I can tag them properly. Creating the tasks in<br>the actual smart list where they belong is another fail-safe. :) Actually, every task should have a context. That's how I keep them
from getting lost. I actually place contexts and projects on the same
level as far as keeping the system water tight. For instance, in the
example you post, all of these tasks would be tagged with
“.drinkcoffee” as their project, which would keep them out of the ugly
filter. The same goes for any task that actually has an @context.

As far as misspelling stuff, I take heavy advantage of RTM's
auto-complete. Even if I know what tags I want, I click them off from
the auto-complete drop down list. When I'm on the go adding tasks via
email and such, I don't usually bother trying to tag them at that
time, I just wait until I get back to a browser (I don't have the net
on my phone) so that I can tag them properly. Creating the tasks in
the actual smart list where they belong is another fail-safe. :)

]]> By: Markus http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2644 Markus Fri, 18 Dec 2009 09:49:00 +0000 http://sheenonline.biz/?p=46#comment-2644 OK we seem to have a different understanding about task status<br><br>In .drinkcoffee<br>-make coffee<br>-take milk from fridge<br>-pour coffee<br>-establish your own coffeeshop<br><br>for me "take milk" is not -someday and it's not -next. I'd call "establish coffeeshop" -someday because it will be really done someday. "Take milk" is also not -waiting because this would produce too many tasks on my waiting list (actually would be 250!)<br><br>So quintessence seems to be: <br>-to get the system waterproof every task must have a status. Otherwise tasks could be missed. Therefore I need something like -later. I better not check tagContains:- to be sure status is valid. Better (but less "dynamic"): tag:-next OR tag:-waiting.... <br>-Further every task that is next needs a context. And it needs to have a valid context which is not sure using the above smartlist, right? I already have a check that searches -next tasks not being on a contextlist <br>-the last chance to loose tasks is wrong spelling of project tags. I actually don't have an idea how to catch these. So I have to be carefull with the .project tags (e.g. only assign these by entering the tasks directly into contextlists (does move to smartlist change tags? This would be marvellous! I'll test it) OK we seem to have a different understanding about task status

In .drinkcoffee
-make coffee
-take milk from fridge
-pour coffee
-establish your own coffeeshop

for me “take milk” is not -someday and it's not -next. I'd call “establish coffeeshop” -someday because it will be really done someday. “Take milk” is also not -waiting because this would produce too many tasks on my waiting list (actually would be 250!)

So quintessence seems to be:
-to get the system waterproof every task must have a status. Otherwise tasks could be missed. Therefore I need something like -later. I better not check tagContains:- to be sure status is valid. Better (but less “dynamic”): tag:-next OR tag:-waiting….
-Further every task that is next needs a context. And it needs to have a valid context which is not sure using the above smartlist, right? I already have a check that searches -next tasks not being on a contextlist
-the last chance to loose tasks is wrong spelling of project tags. I actually don't have an idea how to catch these. So I have to be carefull with the .project tags (e.g. only assign these by entering the tasks directly into contextlists (does move to smartlist change tags? This would be marvellous! I'll test it)

]]> By: Rahsheen http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2643 Rahsheen Thu, 17 Dec 2009 10:38:01 +0000 http://sheenonline.biz/?p=46#comment-2643 Oh! Ok. I see what you mean. The ultimate goal is that nothing is<br>caught by the "ugly list." Part of an effective GTD system is that you<br>know when you can do something and you know where you have to be to<br>accomplish it. For instance, I know I need to be @online to update my<br>blog, @grocery to pick up the milk, or @work to fire my boss. If I'm<br>not -waiting on someone or -someday in order to complete a task, it<br>must be a -next action. The "ugly list" is really just to catch your<br>mistakes :) Oh! Ok. I see what you mean. The ultimate goal is that nothing is
caught by the “ugly list.” Part of an effective GTD system is that you
know when you can do something and you know where you have to be to
accomplish it. For instance, I know I need to be @online to update my
blog, @grocery to pick up the milk, or @work to fire my boss. If I'm
not -waiting on someone or -someday in order to complete a task, it
must be a -next action. The “ugly list” is really just to catch your
mistakes :)

]]> By: Markus http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2642 Markus Thu, 17 Dec 2009 09:54:25 +0000 http://sheenonline.biz/?p=46#comment-2642 I think i haven't been clear enough. Of course I have lots of single tasks that don't belong to any project so they are missing a .projectname tag and, as long as they aren't -next and no context is assigned (I assign the context when the task gets a next action because the context might change until that point; this might be the differrence in out workflows) they are caught by that filter.<br><br>Second I worry about tasks that do have a .project tag but have a typo in the project name. As long as you dont' check for tasks not being at the project or single actions lists you will loose them in my eyes because theyre only in the UglyCollection- list. This seems to be one dissadvantage in the use of the smartsearch projectlists I think i haven't been clear enough. Of course I have lots of single tasks that don't belong to any project so they are missing a .projectname tag and, as long as they aren't -next and no context is assigned (I assign the context when the task gets a next action because the context might change until that point; this might be the differrence in out workflows) they are caught by that filter.

Second I worry about tasks that do have a .project tag but have a typo in the project name. As long as you dont' check for tasks not being at the project or single actions lists you will loose them in my eyes because theyre only in the UglyCollection- list. This seems to be one dissadvantage in the use of the smartsearch projectlists

]]> By: Rahsheen http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2641 Rahsheen Wed, 16 Dec 2009 10:39:32 +0000 http://sheenonline.biz/?p=46#comment-2641 Anything that is part of a project shouldn't get caught in that filter<br>because of the ".projectname" tag. Pretty much, as long as you assign<br>an "@context," you should be fine. Anything that is part of a project shouldn't get caught in that filter
because of the “.projectname” tag. Pretty much, as long as you assign
an “@context,” you should be fine.

]]> By: Markus http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2639 Markus Tue, 15 Dec 2009 11:28:02 +0000 http://sheenonline.biz/?p=46#comment-2639 Very nice setup. I actually changed mine (static lists with smart lists for context to yours which is more versatile. One question: what do you do with (project-) tasks which are not next actions. To keep things easy they shouldn't have any satuts so they will get caught by accident by your NOT tagContains:@ or NOT tagContains:. OR isTagged:false search. Don't you have these? Or is everything which isn't -next or -waiting automatically a Someday task?<br><br>Thanks a lot in advance! Very nice setup. I actually changed mine (static lists with smart lists for context to yours which is more versatile. One question: what do you do with (project-) tasks which are not next actions. To keep things easy they shouldn't have any satuts so they will get caught by accident by your NOT tagContains:@ or NOT tagContains:. OR isTagged:false search. Don't you have these? Or is everything which isn't -next or -waiting automatically a Someday task?

Thanks a lot in advance!

]]> By: Rahsheen Porter (rahsheen) 's status on Friday, 28-Aug-09 14:14:22 UTC - Identi.ca http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2547 Rahsheen Porter (rahsheen) 's status on Friday, 28-Aug-09 14:14:22 UTC - Identi.ca Fri, 28 Aug 2009 14:14:30 +0000 http://sheenonline.biz/?p=46#comment-2547 [...] http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/ [...] [...] http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/ [...]

]]> By: HOWTO: Get Things Done with Evernote | MentalPolyphonics http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2467 HOWTO: Get Things Done with Evernote | MentalPolyphonics Wed, 03 Jun 2009 16:02:37 +0000 http://sheenonline.biz/?p=46#comment-2467 [...] You could have a single notebook and use tags for status, but since any given action is only going to have one status, I don’t see the advantage of [...] [...] You could have a single notebook and use tags for status, but since any given action is only going to have one status, I don’t see the advantage of [...]

]]> By: mikehardin63 http://sheenonline.biz/2008/06/super-charge-remember-the-milk-with-smart-lists-and-tags/comment-page-1/#comment-2460 mikehardin63 Thu, 28 May 2009 03:02:16 +0000 http://sheenonline.biz/?p=46#comment-2460 make "and list:Daily" a part of the search criteria for your smart list and you won't have to move them from the inbox. They will go in the daily list automatically. make “and list:Daily” a part of the search criteria for your smart list and you won't have to move them from the inbox. They will go in the daily list automatically.

]]>