On Fri, Jan 2, 2009 at 5:12 AM, Ido Magal <[email protected]> wrote: > Totally understood and agreed. > > My question is, how does a tickler differ sufficiently from a delayed > action to warrant its own concept? > Is it often that ticklers don't result in an action or project that needs > Doing?
The example that David Allen uses is getting a schedule for concerts he might want to attend, that are 8 months (or whatever) into the future. He doesn't know if he'll even be in town then, so he can't make a project "book ticket for show" or anything like that. So he puts the concert schedule into a tickler file (he's describing a physical set of folders to use as a tickler file), and it disappears off his planning radar for 6 months or whenever the tickler is due. When it comes up again, it's just another thing in his inbox -- maybe he's gonna be overseas when the show is on, so he can just chuck the thing out, no actions necessary. So that's the example; the tickler is just another kind of in-tray item. In the real world of mGTD users though, I suspect people do use ticklers for delaying actions as you suggest :) You can probably tag an action to make it a tickler too.. I do like the idea of a project and action having a couple of buttons: [ hide this for 2 weeks ] [ hide this for 6 weeks ] ..kinda turning them into ticklers. ;Daniel -- Daniel Baird /to be or not to be/ => /(2b|[^2]b)/ => /(2|[^2])b/ => /.b/ ...optimise your regexes, people! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GTD TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
