Forum

  • If you are new to these Forums, please take a moment to register using the fields above.
Announcement Announcement Module
Collapse
No announcement yet.
How to define a next task that might be a big task Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to define a next task that might be a big task

    Again, just looking for best practicies.
    Let's say you have an issue log for a project or something, with 20 issues on it. Your job is to review the log, and act on each one, with each one maybe becoming multiple actions.
    Would I throw in a next action of:
    "Review open issues and determine next action for each." That seems to me like a concrete, physical task.
    or put in an action item for each one?

  • #2
    It seems to me that you first have a single next action (if you can get it done in one sitting): Review the list. That list is like an inbox. As you go through it, each of the issues may become it's own project because there is more than one tasks associated with each issue. For each new project, you then have a single "next action" (plus any other "project" details you might need to document in a separate location).

    C.

    Comment


    • #3
      I tried that and it worked. Thanks!

      Comment

      Working...
      X