summaryrefslogtreecommitdiff
path: root/projects-next-actions.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'projects-next-actions.mdwn')
-rw-r--r--projects-next-actions.mdwn12
1 files changed, 11 insertions, 1 deletions
diff --git a/projects-next-actions.mdwn b/projects-next-actions.mdwn
index f18d125..c3300ff 100644
--- a/projects-next-actions.mdwn
+++ b/projects-next-actions.mdwn
@@ -14,7 +14,17 @@ two very important reasons:
* it's unclear when it's finished
When you actually start doing things, it's much easier if you know what
-you need to do, and when you're finished.
+you need to do, and when you're finished. A **good next action** would
+fulfill the following criteria:
+
+* a _physical_ action ("write", not "think about")
+ * thinking is part of planning! and that should happend during review phase
+ * planning can be broken down into next actions, however
+* it's clear what I need to (a widget to crank)
+* duration at most 15 minutes, preferably
+* I'm committed to doing it
+* does not depend on anything, can be done immediately
+* it's clear when it's done
Obviously, some things you want to get done are going to take a lot of
time. That's OK: they just should not be next actions. Next actions need