Project tasks beyond the next action
Apologies in advance for what feels like a stupid question, but:
Say I'm processing/organising a task, and realise that once I've done that, there'll be an action straight afterwards (say, 'review notes', followed by 'email summary to my boss'). I'll set up a next action (or put it in the calendar if has to be done at that time) for 'review notes', but I can't figure out what to do with the second of those actions:
- it's not a next action
- I can't put it in the calendar - I might not even have to, in terms of it not having a deadline
- it's not a 'someday/maybe' action
- waiting for doesn't feel right at all - especially if I'm setting out a project with many actions, it would just become cluttered with tasks I can't do anything about right away
- it's kind of a natural consequence of completing the first action, but surely GTD finds a way of recording it as a specific task up front?
I can't recall this being covered in where I'm up to in the book. And apologies again if this keeps coming up.
Thanks in advance!
project support and other ways...
there are several ways to treat this "next" next action and all actions coming after that, that you might want to record all ready because you thought of them and you don't want to lose the idea (or because there is a commitment):
- you might define "e-mail summary to boss" as a project and "review notes" would be the first action for that project
- you might define your next action as "review notes (for e-mailing boss)"
- you might define a waiting for: "WF: review notes (to mail boss)
- you might start reviewing the notes and in that same flow send the mail to your boss, and not need to record that next action at all ;-)
- you might store thos next next actions in project support material (and store it as "rough planning for the project")
Just try something (maybe one of these or something completely different): give it a chance, see if it works for you. If it does: do it again. If it doesn't: try something different until you find some approach that works for you...
MNA - Multi Next Action notation.
For a linear sequence of two or three actions in the same context you can use the following Next Action notation:
Originally Posted by jduk
Review notes >> Prepare Summary >> Email summary to boss
Another vote for the Weekly Review
I think a lot of people feel the need for "safety nets" in their system, and that's absolutely fine - I do it all the time. But I also reiterate the importance of the Weekly Review, which according to David is really geared towards the 10,000 foot, Project level. You can't "forget that there's more to come" if you are reviewing every project each week for completion or further action needed. I don't think the usefulness of the Weekly Review as THE key to banishing most niggling thoughts can be overstated!
Originally Posted by jduk