summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2012-11-23 16:59:22 +0000
committerLars Wirzenius <liw@liw.fi>2012-11-23 16:59:22 +0000
commita5aa91c07b7455bd9ccbfcbca8304d60cb5aa390 (patch)
tree6c440e65b3ae7110ed7b50272b13ab730a9b98ae
parent9f200c7276af51aba4e9cc08d481fc5436cf3cea (diff)
downloadgtdfh.liw.fi-a5aa91c07b7455bd9ccbfcbca8304d60cb5aa390.tar.gz
Write down the goal of a project
-rw-r--r--projects-next-actions.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/projects-next-actions.mdwn b/projects-next-actions.mdwn
index 875608f..3cdcaea 100644
--- a/projects-next-actions.mdwn
+++ b/projects-next-actions.mdwn
@@ -47,6 +47,11 @@ time, though the time will be much longer. Next actions should typically
be doable within half a day (but shorter is better), whereas projects
might last up to a year.
+It's a good idea to write down the goal of a project in a sentence or
+a paragraph. This concentrates your thinking to be directed at achieving
+that goal and makes it easier to avoid spending time on things that are
+related to the goal, but don't help you achieve it.
+
Keeping track of projects and next actions: the art of lists
------------------------------------------------------------