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.
Trying to setup GTD - Internet Business - Always Online
MoeBerry | Jan 8 2007
Hello new friends! I am nearly done with the GTD book, and I am trying to get a few conceptual questions answered. 1 - Are ongoing everyday tasks such as: These are divided by vendor in some ways, but the orders come into one website. So I am not sure if these actions are really contexts, or projects? If they are projects that are just permanently daily tasks, and not something that are ever going to be "completed"... 2 - Since I am always with my laptop, and phone, I am not sure the best way to setup my contexts? Should I divide things up by time during the day? ... like "morning work", "afternoon work"? The thing is I can pretty much do any task at anytime. Its nice, but frustrating as well. I am planning to use outlook as my trusted system, with the GTD add-on. 90% of my items are digitally stored, or at least have the key reference digitally. Your advice is welcome! 4 Comments
POSTED IN:
Checking for new orders, sending...Submitted by Herah on January 10, 2007 - 12:39pm.
MoeBerry;7593 wrote:
If you are already doing these things by habit, you don't have to represent them at all. If you need to be reminded, or need to track whether they're done, they can be repeating tasks in the @Work context (since you say you're using Outlook). You cross them off each day, and they automatically reappear the next day. MoeBerry;7593 wrote:
Should I divide things up by time during the day? ... like "morning work", "afternoon work"? Only if they naturally fall out that way. I have separate @TrainAM and @TrainPM contexts because the set of possible action items is different -- I can't process the day's notes on the morning train, or plan the day's schedule on the evening train. Think in terms of "workspaces". If you have to log in to some external system or bring up a specific application, and you don't stay logged in all day, that can be a context (I have @Quicken for personal bookkeeping). If you have to get into a certain mindset -- the way David talks about batching his phone calls -- that can be a context. Sometimes I wind up nesting contexts -- for example, if there are bills to pay, I'll put an "@Quicken" task in my @Home context, to remind me to visit that context today. » POSTED IN:
|
|
EXPLORE 43Folders | THE GOOD STUFF |