Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.
Actions from emails
mcnicks | Apr 3 2006
I have been working on improving the organization of my emails and I have set up some folders for actionable stuff: @Action,for stuff that needs done; @Review, for stuff that may contain actionable stuff but needs more detailed reviewing to determine them and @Waiting, for emails that indicate that I am waiting for others to respond (mostly these are emails I have sent to other people, asking them to do stuff for me). This seems to be working well, but I think that it is not as 'GTD' as it could be. The emails in my @Action folder can lack clarity and often contain more than one action, which means that there may not be an single, obvious next action to take for each email. So I wonder whether, as part of my email processing, I should be taking time to extract actions from emails into my next action context lists? Sounds sensible, but I am not sure how to relate the actions that are produced back to the emails (particularly because I am swinging towards using lofi, paper and pen lists). What do you all do in this case? Should I consider my @Action, @Review and @Waiting folders as mini reference folders that I review at regular intervals? I am worried that I will end up with a system that I do not implicitely trust ("has that email been _totally_ dealt with?" / "is this action all I have to do wrt that email?" ...etc). Cheers, 3 Comments
POSTED IN:
What particular system are you...Submitted by emuelle1 on April 3, 2006 - 8:47am.
What particular system are you using? As an Outlook user, if I get an email with actionable items, I drag the email to the tasks folder and change the name accordingly. That way the content of the email remains in the task and the email can be deleted. If it's a project, I assign it to the Project category and generate NAs as appropriate. I do keep a "Read/Review" folder at both home and work, so items that I want to look at more in depth that are not time sensitive can go in and wait for me to decide that I feel like reading it. In fact, I just deleted a bunch of corporate newsletters that I realized I'm NEVER going to read. I read one and decided that the other six probably have the same level of substance and meaning to my life and career. I treat waiting for emails as tasks. I generate a task and put it in the @Waiting For category so that it can be tracked. If it is a project, I put it in Projects and generate an NA to put in @Waiting For. » POSTED IN:
|
|
EXPLORE 43Folders | THE GOOD STUFF |