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.
the 2 minute action that grows Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • the 2 minute action that grows

    What are some ways of handling these situations that work for people? I keep thinking that I am over-looking or not getting some basic principle.

    I am processing and begin to execute what I think will be a two-minute action. But, I discover that:

    1. It is going to take more than the time I have at hand, even if it is a one-off action.

    or

    2. It is part of an active project but I had not considered this aspect. I need to make a note of this and incorporate it into project planning. Or, , it changes the next action on my list (a good reason to try to associate actions with projects). For example, I went to replace a battery in a receiver and found I needed to order a new housing that holds and the battery in place. To find the part number I have to take the old housing apart, for which I need to identify the size tool I need and then get it. But, my next action after replacing the battery and getting this gizmo to work was to order a special cleaner for it (independent) but I am not going to clean it if I can't get the new battery housing anyway.

    or

    3. It is a someday maybe, but I don't know yet if it will stand alone or be part of a project. I need to remember to incorporate it when I plan the project and when I decide if the project is active or not.

    or

    4. It is so important that it will make me want to make the project active as soon as I can.

    5. It is actually part of a routine but no one has been doing it routinely, either because no one was thinking about it or no one wanted to.

  • #2
    Originally posted by Jamie Elis View Post
    I am processing and begin to execute what I think will be a two-minute action. But, I discover that:

    1. It is going to take more than the time I have at hand, even if it is a one-off action.
    Add action to appropriate context list.

    2. It is part of an active project but I had not considered this aspect. I need to make a note of this and incorporate it into project planning. Or, , it changes the next action on my list (a good reason to try to associate actions with projects). For example, I went to replace a battery in a receiver and found I needed to order a new housing that holds and the battery in place. To find the part number I have to take the old housing apart, for which I need to identify the size tool I need and then get it. But, my next action after replacing the battery and getting this gizmo to work was to order a special cleaner for it (independent) but I am not going to clean it if I can't get the new battery housing anyway.
    Make appropriate note in project materials for later action and/or adjust project plan on the spot and/or adjust next action list on the spot.

    3. It is a someday maybe, but I don't know yet if it will stand alone or be part of a project. I need to remember to incorporate it when I plan the project and when I decide if the project is active or not.
    File it with other materials related to the someday/maybe project for later review.

    4. It is so important that it will make me want to make the project active as soon as I can.
    Drop everything and get to work on the project if possible. Look at calendar and schedule a slot if not.

    5. It is actually part of a routine but no one has been doing it routinely, either because no one was thinking about it or no one wanted to.
    Treat as any other action, though you might want to review your system for reminders of routine actions to see if changes are needed.

    Katherine

    Comment

    Working...
    X