A
Anonymous
Guest
How do you deal with one-day projects? I get a lot of requests that are mini-projects and need to be completed the same day they are requested. Like 'could you print out report XYZ, review these changes, reprint and fax to so-and-so'. Or oftentimes I get to work in the morning to find a note attached to my door saying 'help, my printer needs more ink' which requires that I retrieve an ink cartridge from storage, call the person and ask when I can come install it in their office (so I don't interfere with a meeting) and then actually installing it and realinging, etc. These are projects in themselves, but they are simple and usually completed a few hours or less after they are 'collected'.
In the previous example, I usually just put 'Fix Printer 1234' on my next actions list for the day and try to do it all in one step. If I can't because the person is in a meeting and I have to schedule another appointment to finish the job, then 'fix printer 1234' is not a true next action. Perhaps I'm overanalysing this, but I am guessing that I should change the text and/or context of the action each time I get to a stopping point. Maybe changing the action to 'set appointment with so-and-so for printer repair'. I want to keep it simple, but I don't want to see 'fix printer 1234' when the true next action is 'call so-and-so/re: printer'. It seems like overkill to define a successful outcome and create a project out of a small task that in itself will take less than a half hour at best unless I am forced to wait for the other party to be available to complete the project. There are other small 'projects' like this that creep up through my day. I am trying to get a handle on them as they pop up. If they are urgent (and many of them are) they immediately go on my agenda for the day. I just have trouble picking them up again when the true next action isn't clearly stated. I end up having to rethink where I was with that 'project' before moving on it. Maybe I should just do it and not overthink it and only change the context if it doesn't get completed that day. Any thoughts?
In the previous example, I usually just put 'Fix Printer 1234' on my next actions list for the day and try to do it all in one step. If I can't because the person is in a meeting and I have to schedule another appointment to finish the job, then 'fix printer 1234' is not a true next action. Perhaps I'm overanalysing this, but I am guessing that I should change the text and/or context of the action each time I get to a stopping point. Maybe changing the action to 'set appointment with so-and-so for printer repair'. I want to keep it simple, but I don't want to see 'fix printer 1234' when the true next action is 'call so-and-so/re: printer'. It seems like overkill to define a successful outcome and create a project out of a small task that in itself will take less than a half hour at best unless I am forced to wait for the other party to be available to complete the project. There are other small 'projects' like this that creep up through my day. I am trying to get a handle on them as they pop up. If they are urgent (and many of them are) they immediately go on my agenda for the day. I just have trouble picking them up again when the true next action isn't clearly stated. I end up having to rethink where I was with that 'project' before moving on it. Maybe I should just do it and not overthink it and only change the context if it doesn't get completed that day. Any thoughts?