diff options
| -rw-r--r-- | index.mdwn | 4 | ||||
| -rw-r--r-- | projects-next-actions.mdwn | 12 |
2 files changed, 12 insertions, 4 deletions
@@ -63,9 +63,6 @@ Outline - "current files" for stuff relevant for current projects and next actions * [[Inputs and inboxes|inboxes]] * [[Projects and next actions|projects-next-actions]] - - next action: physical action, well-defined, preferably less than 15 min - - project: anything that takes more than one step, but less than a year - - discuss possible contexts and categories for next actions * [[Keeping track of files|files]] - pending and support (current files) - archiving systems and tools @@ -134,6 +131,7 @@ being added to the text of the book. worked on at least one thing you care about. * phone calls, sms, notes, as inbox +* inboxes: show pseudocode from liw's canonical presentation References ---------- 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 |