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.

Are concurrent multi-steps projects?

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Are concurrent multi-steps projects?

    Hey guys,

    Do you think it's necessary to list a project if all of it's steps can be done independently of each other. Isn't an item in a project list just so you don't forget about putting an action item down? But if all possible next actions are already on the action lists, is it still necessary?

    Thanks.

    Jason

  • #2
    Right, no need for a reminder on the project list if there is nothing else to remember (in addition to what is already on the NA lists).

    The only purpose of the entry on the project list is to remind you to generate next actions after current ones are completed.

    Comment


    • #3
      Originally posted by jayx773 View Post
      Hey guys,

      Do you think it's necessary to list a project if all of it's steps can be done independently of each other. Isn't an item in a project list just so you don't forget about putting an action item down? But if all possible next actions are already on the action lists, is it still necessary?

      Thanks.

      Jason
      My only question: how you can be sure that ALL the next actions are on your lists? It only takes a couple of seconds to put a project on your project list - and this would help you to monitor to the project until it is complete - you lose nothing by putting it on the list and gain a safety-net.

      "All possible next actions" - do you mean all actions that it is possible to do now or every action required to complete the project? Again, I would recommend listing the project, in case you haven't thought of all the next actions.

      Comment


      • #4
        Madalu makes a good point. I recently had a project to survey six people on a particular topic. So I put all six calls on my list as NAs and I'm done, right?

        Wrong. First you have phone tag, spawning an endless series of calls to return, missed calls, and so forth. Then you have, "I'm sorry, you should talk to X instead," starting the whole series over again with X. Not to mention, "some of that may be proprietary, could you send me the survey so I can clear it?" And endlessly on and on. Plus writing up the results once I actually do get the questions answered. As it turns out, this "simple" project involved far more aggravation and NAs than many much more complex (and highly compensated...) efforts.

        Put it on the project list. Why not? It only takes a few seconds, and then you're covered in case those NAs turn out to not be all there is.

        If you're reluctant to create projects, you might look and see whether your tools are imposing too much overhead. Creating a project shouldn't be much harder than creating an NA, really.

        Katherine

        Comment


        • #5
          I've made myself two project lists. "Regular" projects are those complex projects which require planning, support materials, etc. "Mini" projects are those which are very, very simple - no need for additional information - but for which I need some sort of reminder because they have more than one action.

          Comment

          Working...
          X