|
|
|
Archive - Mar 2006
- Date
-
- All
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
Tue, 2006/03/28 - 06:17 — matt
One idea that comes up regularly for GTD practitioners is the idea of keeping a "daily to-do list," i.e., a list of tasks (Next Actions in GTD-speak) that should be done that day. Keeping one of these is a traditional time management staple [1], and one that Allen turns on its head. The reasoning is:
- The pace of modern life changes so fast that such daily plans are often invalidated by the first unforeseen event (e.g., an email from a client at 8:15 AM that requires your immediate attention).
- Having tasks on the daily to-do list that don't absolutely have to be done that day numbs you to other items that really do have to get done, leading to things slipping through the cracks and decreased trust in your system.
Wed, 2006/03/22 - 22:15 — matt
As part of my self-training to be a personal productivity presenter and coach, I'm reading [1] every related book I can get my hands on. (My goal? Be a world-class expert [2] in the field.) One thing I regularly come across are relatively simple ideas for workflow management, esp. "TRAF" (Toss, Refer, Act, File) and the "Four Ds" (Delete, Do, Delegate, Defer). How do these compare with the more complex GTD workflow diagram? Read on!
The players
In this section I'll describe the three approaches to managing inputs that we'll be comparing - TRAF, the "Four Ds", and GTD's workflow diagram.
Thu, 2006/03/16 - 04:07 — matt
At the start of the year, I decided to try an experiment (see A geek "gets" networking: The strange magic of connecting with others): I was going to grow my personal network by three people per week for a year, a goal that seemed both audacious and possible, given a bit of stretching (which Alvin says is The Most Important Thing to Do).
In the last ten weeks I've connected with about 50 new people, which actually exceeds my goal of three per week (30 at this point). Even this early in the experiment, I've had a number of lessons and questions come up, which follow. However, the short story is 1) it's fun, 2) it's work, 3) it's personally challenging and rewarding, and 4) I don't know where it's going!
Effort
Mon, 2006/03/06 - 21:34 — matt
I write down everything I want to remember. That way, instead of spending a lot of time trying to remember what it is I wrote down, I spend the time looking for the paper I wrote it down on. -- Beryl Pfizer
I've dreamed up an information-managing tool that should exist, and it's driving me nuts working without it. Here are a few initial notes; comments are very welcome.
In training myself to be a productivity consultant, my information tracking and capturing needs have gone through the roof. For example, I need to manage things like:
- networking information (who, when, how I connected to them),
- blog ideas,
- useful productivity tips for myself and clients,
- marketing and web site ideas,
- notes from books I read [2],
- notes/ideas for projects,
|
Search
Recent blog posts
- Productivity lessons from mountain biking. Or, what sports can teach us about doing
- IdeaLab 0826: Systemic self-repair, over-blogging, faith, and "doing it" productivity style
- A conversation with Ron Hale Evans, author of "Mind Performance Hacks"
- Why Blogruptcy is a great idea but doesn't work, and why SPAM is easy to fix and information overload isn't
- IdeaLab 0729: A little GTD heresy, willpower, jealousy, and straight talk
- Honors, Mac tips, plus (apparently) a iCal-GTD-Quicksilver mini-tutorial
- An interview with Scott Ginsberg, author of "Hello, My Name is Scott"
- The Path of Maximum Productivity: Seven tensions, and how to resolve them
- IdeaLab 0624: Ice Cream, attitude, danger, and dishwashers
- The productivity I/O sweet spot, or Why balance is a bad thing
| |