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.
"Waiting for" triggers next actions Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • "Waiting for" triggers next actions

    Does anyone else use a waiting-for trigger list to create next actions that aren't obvious?

    Let me give an example. I just ordered some flower bulbs to plant in my garden this spring. However, they come in a package that is much too large for me to plant, so I put out an open offer for my friends and family to take some. A few took me up on it.

    Now when I get the bulbs in the mail, the obvious next action is "plant the bulbs". However, I also owe a few people bulbs, which I can easily forget.

    So I created a "Waiting for trigger list" and number actions that will need to be taken once a "waiting for" is fulfilled.

    In this case, I created a trigger called "1. distribute bulbs to Joe, Jill, and CJ", and noted "Trigger list 1" next to my Waiting-for "Waiting for bulbs to arrive". Then when I cross it off, I'll reference my trigger list and add that item to my next-actions.

    Does anyone else find themselves using a "Waiting for trigger list"? Is there a better way to do this?

  • #2
    It sounds like you have a situation where one project (distribute bulbs to Joe, Jill, and CJ) can't start until an action is completed in another project (order bulbs). I don't know what you mean by a "trigger list", but what I do is have two projects, one that starts with a "Waiting For bulbs to arrive", the other starts with "Order bulbs" then "Waiting For bulbs to arrive" then "plant bulbs", etc. The first "Waiting For" in the distribute project sits on my @Waiting For list while the ordering commences. Once the bulbs have been ordered, I have two identical Waiting Fors ("Waiting For bulbs to arrive"). Once they arrive, both "Waiting For's" get marked done and both projects proceed. That's how I would handle it.

    Comment


    • #3
      Originally posted by cojo View Post
      Is there a better way to do this?
      I'd just put the waiting for bulbs to arrive on one list. When they do I'd catch that I have to distribute bulbs by looking at the project notes for bulb garden and note that I have to send some to the folks I am sharing with. I'd have a single larger project that covers all bulb activities.

      Comment


      • #4
        Originally posted by Oogiem View Post
        I'd just put the waiting for bulbs to arrive on one list. When they do I'd catch that I have to distribute bulbs by looking at the project notes for bulb garden and note that I have to send some to the folks I am sharing with. I'd have a single larger project that covers all bulb activities.
        I like this...I do have a "project" section that includes notes for individual projects and I consult it frequently.

        Comment


        • #5
          Personally, it looks like you have two projects: Plant bulbs, and Give away bulbs.

          Comment


          • #6
            I've recently introduced something like this into my system. I added a "checklist" section, which is where I dump "don't forget" actions that won't be relevant until some event triggers the checklist.

            So I'd have the Deliver Widget Project checklist and the Dinner Party checklist and in your case I would create the Bulb Arrival Checklist as soon as the first "don't forget" action re the bulbs came up.

            So the action "Waiting for: Bulbs" would probably be phrased "Waiting for: Bulbs - Remember Bulb Arrival checklist!"

            I'm not sure if that's Correct, but it's working for me.

            Gardener

            Comment

            Working...
            X