-
Notifications
You must be signed in to change notification settings - Fork 2
/
gtd.html
329 lines (314 loc) · 12.7 KB
/
gtd.html
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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 TRANSITIONAL//EN">
<html>
<head>
<title>Getting Things DONE summary</title>
<link rel="stylesheet" type="text/css" href="common.css"/>
</head>
<body>
<h1>Getting Things DONE summary</h1>
<p>
This webpage summarizes the book
"<a href="http://www.amazon.com/Getting-Things-Done-Stress-Free-Productivity/dp/0142000280/ref=pd_bbs_sr_1/002-3725102-8149600?ie=UTF8&s=books&qid=1190210992&sr=1-1">Getting Things DONE</a>" by David Allen.
He runs a consulting company called "The David Allen Company"
whose website is <a href="http://www.davidco.com/">here</a>.
</p>
<h2>Key Objectives</h2>
<p>
<ul>
<li>Document all the tasks you need to accomplish
in a system other than your memory.
Include tasks to be worked now and in the future.
Include both work and personal tasks.</li>
<li>Consult your lists often so you'll make
wise decisions about the next task on which to work.</li>
</ul>
</p>
<h2>Main Benefits</h2>
<p>
<ul>
<li>Stress is reduced because you won't have to worry
that you forgot about some important task.</li>
<li>You will make better choices about where to focus
your attention at the current time, taking into account
your <a href="#context">context</a>.</li>
</ul>
</p>
<h2>Five Stages of Managing Workflow</h2>
<p>
<ol>
<li>collect inputs</li>
<li>process inputs</li>
<li>organize results</li>
<li>review options for next actions</li>
<li>do a next action</li>
</ol>
</p>
<h3>Collecting Inputs</h3>
<p>
Inputs include:
<ul>
<li>notes written on scrap paper, napkins, etc.</li>
<li>notebooks</li>
<li>email</li>
<li>calendars containing written notes</li>
<li>flyers about upcoming events</li>
<li>magazines</li>
<li>books</li>
<li>just about anything you've accumulated
on your desk, in a closet, in piles on the floor,
or stashed in your car</li>
</ul>
</p>
<h3>Processing Inputs</h3>
<p>
Here are the steps to follow when processing each of the collected inputs.
<ol>
<li>Determine whether some action needs to be taken?</li>
<li>If it does require action then
<ol type="a">
<li>Determine the <b>next action</b> that is required.<br/>
This must be a real activity.
For example, instead of "car tires",<br/>
an action could be "call to schedule tire change" or
"investigate tire prices online".</li>
<li>Select one of the following options.
<ol>
<li><b>Do it</b>
if it can be completed in two minutes or less.</li>
<li><b>Delegate it</b>
if you are not the right person to do it<br/>
and it can be delegated to someone else.<br/>
Consider adding it to your "Waiting For" list
to track its completion.</li>
<li><b>Defer it</b>
by documenting it as something to be done later.<br/>
If it requires multiple actions, create a <b>project</b>
for tracking the actions and document them.<br/>
A project is just a task that requires
more than one action to complete.<br/>
Document the required action(s) in one of these repositories:
<ol type="a">
<li><b>calendar</b>
(for non-paper-based, date/time-specific reminders)</li>
<li><b><a href="#43Folders">43 Folders</a></b>
(for paper-based, date-specific reminders)</li>
<li><b>"Next Actions" list</b>
(for non-date/time-specific reminders)</li>
</ol>
</ol>
</li>
</ol>
</li>
<li>If it doesn't require action then<br/>
select one of the following options.
<ol type="a">
<li>Throw it in the <b>trash</b>.</li>
<li>Incubate it by adding it to your <b>someday/maybe list</b>.</li>
<li>Store it in your <b>reference filing system</b>.</li>
</ol>
</li>
</ol>
</p>
<p>
The reference filing system is typically a single,
alphabetized collection of folders that hold any material
you may want to refer to later.
This includes support materials for specific projects.
If a single topic or project requires a large number of folders,
they might be stored in a separate, alphabetized collection of folders.
</p>
<h3>Organize Results</h3>
<p>
Information related to projects and tasks (actions)
can be stored in the following locations.
<ol>
<li><b>project list</b></li>
<li><b>"next actions" list</b> categorized by project and
<a href="#context">context</a></li>
<li><b>calendar</b>
for date or time specific actions that must be performed
and information about specific days</li>
<li><a href="#43Folders"></b>43 folders</b></a>
for paper-based reminders of date-specific actions</li>
<li><b>reference files</b></li>
<li><b>"waiting for" list</b> list to track actions
you are waiting for others to complete</li>
<li>"<b>someday/maybe</b>" list<br/>
Examples of things that might be included in this list include:
<ul>
<li>projects you'd like to begin</li>
<li>vacation destinations you'd like to visit</li>
<li>books you'd like to read</li>
<li>DVDs you'd like to rent</li>
<li>CDs you'd like to buy</li>
</ul>
</li>
<li><b>email folders</b><br/>
Create an email folder named "@ACTION" and use it to
hold emails that describe action you must complete.<br/>
Create an email folder named "@WAITING FOR" and use it to
hold emails that describe actions for which you are waiting for
others to complete.</li>
<li><b>read/review stack</b></li>
</ol>
</p>
<p>
The lists mentioned above can be on paper or in an electronic form.
An advantage of paper lists is that you view them and add to them
without being at your computer. An advantages of electronic lists
are that they are easily searched. Another is that the items in them
can be indexed in multiple ways, for example, by project and by context.
</p>
<p>
A <b><a name="context">context</a></b> describes a basic requirement
that must be met in order to do an action. It can be
<ul>
<li>a location (such as home or office) where you need to be</li>
<li>a specific tool (such as a phone or computer)
that must be available</li>
<li>a person (such as your boss) that must be present</li>
</ul>
</p>
<h3><a name="43Folders">43 Folders</a></h3>
<p>
This is a name for a technique of using ordinary folders
to store paper-based reminders of things to be done
on a specific date or during a specific month.
It requires using 43 folders,
one of each of the 31 days in the longest month
and one for each of the 12 months.
The folders are labeled with day numbers and month names.
They are stored in a particular order.
For example, on the morning of April 16th,
the folders would be in the following order:
16, 17, 18, ..., 31, May, 1, 2, 3, ..., 15,
June, July, August, September, October, November, December,
January, February, March, April.
</p>
<p>
Every morning you look in the front folder to see if it contains
reminders about things you need to do today.
After processing the contents of the folder
it is moved to its proper position after all the numbered folders
behind the folder for the next month.
If it is the first day of the month then the folder for the new month
is examined. Its contents can be processed immediately or
moved to one of the numbered day folders behind it.
After processing the contents of the month folder
it is moved to back of the set of 43 folders.
</p>
<p>
When you have a paper-based reminder for something to be done in the
next 28 to 31 days, it is placed in one of the numbered day folders.
When it doesn't need to be addressed for longer than that,
it is placed in one of the month folders.
</p>
<p>
Examples of situations where this is useful include:
<ul>
<li>birthday cards to be mailed on a certain day</li>
<li>bills to be paid on a certain day</li>
<li>maps to places you need to go on a certain day</li>
<li>sales or coupons that are good on a certain day</li>
</ul>
</p>
<h2>Practices to Adopt</h2>
<h3>Habits</h3>
<p>
<ul>
<li>Always have paper and a writing instrument with you.
Ideas can come at any time. Process these notes as new inputs
ASAP so they aren't lost and are considered when planning
next actions.</li>
<li>Always bring something from your "To Read/Review" stack
to meetings. Meetings nearly always start late and the time
spent waiting can be used to catch up on reading.</li>
</ul>
</p>
<h3>Daily Practices</h3>
<p>
Determine if anything described in the following locations
needs to be addressed today.
<ul>
<li>43 Folders</li>
<li>your calendar</li>
<li>your @ACTION email folder</li>
<li>flagged items in your next actions list</li>
</ul>
</p>
<h3>Periodic Practices</h3>
<p>
<ul>
<li>At least once per week,
review all incomplete items in your lists and
flag the onces that need to be addressed soon.</li>
<li>At least once per year review the content of
all the folders in your reference filing system and
throw out items that are no longer relevant.</li>
<li>Once a week or less, review your "Projects",
"Waiting For" and "Someday/Maybe" lists
to see if anything in them needs to be addressed soon.
This review can generate new items in the "Next Actions" list.</li>
<li>At least once per week, gather new inputs
and add them to your system.</li>
</ul>
</p>
<h2>Deciding What To Do Now</h2>
<p>There are three techniques for deciding what task to perform
at any given time.</p>
<h3>Four-Criteria Model for Choosing Actions in the Moment</h3>
<ol>
<li>Only consider actions that can be performed in your current context
(defined by your location and the set of resources available).</li>
<li>Only consider actions that can be completed in the amount of time
you have available. Actions should be defined as small as possible
and not require multiple steps.</li>
<li>Only consider actions that can be addressed given your current
energy level.</li>
<li>Decide between the remaining actions based on their priority
or payoff.</li>
</ol>
<h3>Threefold Model for Evaluating Daily Work</h3>
<p>
The next thing you do can be one of these.
<ol>
<li>Do an action from your "Next Actions" list.</li>
<li>Do work as it shows up if it is more important than
anything on your "Next Actions" list.</li>
<li>Define additional work (adding to your lists) based on new
inputs in your in-basket, email, voic-mail and meeting notes.</li>
</ol>
</p>
<h3>Six-Level Model for Reviewing Your Own Work</h3>
<p>
There are six perspectives from which to view tasks is order to
assign priorities to them. Consider how completing a given task
will help to achieve the following.
<ol>
<li>life goals</li>
<li>3-5 year goals</li>
<li>1-2 year goals</li>
<li>areas of responsibility</li>
<li>current projects</li>
<li>current actions</li>
</ol>
</p>
<h2>Recommended Software</h2>
<h3>Task Lists</h3>
<ul>
<li><a href="http://www.omnigroup.com/applications/omnifocus/">OmniFocus</a>
for Mac OS X</li>
<li><a href="http://www.igtd.pl/iGTD/">iGTD</a> for Mac OS X</li>
</ul>
<h3>Calendar</h3>
<ul>
<li><a href="http://www.apple.com/macosx/features/ical/">iCal</a>
for Mac OS X</li>
</ul>
<h3>Email</h3>
<ul>
<li><a href="http://www.apple.com/macosx/features/mail/">Mail</a>
for Mac OS X</li>
</ul>
</body>
</html>