I have a situation that commonly pops up at work, and I am not sure the best way to handle it.
When I have something pop into my inbox, I decide whether it is actionable or not.
But sometimes it's not so obvious, and it may be because I am not entire clear on what 'actionable' really means.
My understanding is if you process an item that you can do something about, then it's actionable. If you come across an item that you need to do next tuesday, it's actionable. But what about something that you need to do, but can't until a near future condition is met?
Here is an example:
I receive a form via email with new user information. To me, this means set up the new user with an account and then email that user their login information. The setting up the account part is easy, as it is immediately actionable. However, what do I do about sending the email? Is that considered actionable even though I can't send email for a few days (3-5) until someone else sets up their email account?
Is the 'send person login info' action actionable? What I've been doing is putting 'email acct set up for x person' on my @waiting for list. and just checking every day or so to see if it is set up.
I can definitely make it work so it gets done. I am just really curious as to how it flows on the flow chart.
What's the difference between an item that you can't do now but you have to do next tuesday, and an item that you have to do but can't until another condition is met. I somehow feel that this is a different situation that receiving a travel brochure in the mail and deciding i may do something about later, in which case it goes on my someday/maybe list.
So I guess it boils down to: is it 'actionable' if I have to do something about it but can't right now?