Michael Ramone
Registered
Still, all these years later, don't understand what "actionable" means.
It's either exactly the word for the meaning David Allen intended when he wrote the book—"can be acted on"—or exceptionally poorly chosen. How is the question "Is it actionable?" at all related to questions like "Is action required on it?" I just cannot wrap my head around what the idea is supposed to be. I stare at this stupid question for hours to no avail. It's opaque to me. The entirety of the GTD methodology apart from this is crystal clear to me—at least insofar as such is possible in lieu of clarity about "actionable."
If the question is, "Is some action required on this?", then we encounter a slew of unrelated issues. Many items you get in your inbox could, with fairly little consequence, be equally suited for any "decision"—trashed, filed as reference, incubated for "possible later action", acted on somehow in 2 minutes or less, delegated in some form, or acted on later in some longer-than-2-minute form. You COULD do any of them with most of the inputs you get. So what is the real determining criterion? What does "actionable" mean?
What is the idea? I don't understand "action required". I don't understand "Is it actionable?" Is the idea that I'm simply supposed to choose one course and go with it? Is it totally an act of will in the moment?
Let's say I get an e-mail with a bunch of information in it. I know what it is already. That part of the processing is easy and straightforward. Now it occurs to me that I COULD spend some more time reading it more closely. I now have a "next action" that I COULD take—but is this THE "next action" that's "required"? I COULD do it. Is that all that is involved?
Then it occurs to me while looking at the e-mail that I COULD also go check some other data source on the Web that's in some way related to my receipt of this e-mail. Is this an action that is "required" on this input? Is this an action that I "have"?
Then it occurs to me while I'm aberrating in the above that I CAN think of some response that I COULD send back to the sender. Is this now an action for me to take?
Here's the problem: If I ask "Is it actionable?", I answer "Yes, I can..." It is indeed actionable. It can be acted on. If I ask, "Is there some action required on it?", I always say, "No, of course not. I can avoid this e-mail as much as I want. Nothing is necessary about this e-mail."
The answer to "Is it actionable?" is always "Yes." The answer to "Does it require action?" is always "No." What's the real decision? The other options we see paraded around are so squishy
"Do I want to act on it?"
"Am I committed to act on it?"
"Do I intend to act on it soon?"
All these are largely meaningless. You may feel one way one second and another the next
One final note: Many people seem to think that "Is it actionable?" is intended to be used as a test to determine whether some item on a list is sufficiently clear according to GTD standards. They'll say things like "The item 'Go to Europe' is not actionable; it's not broken down enough. 'Surf Web for airline tickets' is actionable. That's a step you can take." This use of the word has nothing to do with what I'm talking about here. I don't know where exactly this idea comes from. I don't think it's used anywhere in the official expositions of the methodology. It seems to be a remnant of some other context or source.
The essence of the decision in the middle of the workflow chart should be damn clear; the entire thing depends on it.
It's either exactly the word for the meaning David Allen intended when he wrote the book—"can be acted on"—or exceptionally poorly chosen. How is the question "Is it actionable?" at all related to questions like "Is action required on it?" I just cannot wrap my head around what the idea is supposed to be. I stare at this stupid question for hours to no avail. It's opaque to me. The entirety of the GTD methodology apart from this is crystal clear to me—at least insofar as such is possible in lieu of clarity about "actionable."
If the question is, "Is some action required on this?", then we encounter a slew of unrelated issues. Many items you get in your inbox could, with fairly little consequence, be equally suited for any "decision"—trashed, filed as reference, incubated for "possible later action", acted on somehow in 2 minutes or less, delegated in some form, or acted on later in some longer-than-2-minute form. You COULD do any of them with most of the inputs you get. So what is the real determining criterion? What does "actionable" mean?
What is the idea? I don't understand "action required". I don't understand "Is it actionable?" Is the idea that I'm simply supposed to choose one course and go with it? Is it totally an act of will in the moment?
Let's say I get an e-mail with a bunch of information in it. I know what it is already. That part of the processing is easy and straightforward. Now it occurs to me that I COULD spend some more time reading it more closely. I now have a "next action" that I COULD take—but is this THE "next action" that's "required"? I COULD do it. Is that all that is involved?
Then it occurs to me while looking at the e-mail that I COULD also go check some other data source on the Web that's in some way related to my receipt of this e-mail. Is this an action that is "required" on this input? Is this an action that I "have"?
Then it occurs to me while I'm aberrating in the above that I CAN think of some response that I COULD send back to the sender. Is this now an action for me to take?
Here's the problem: If I ask "Is it actionable?", I answer "Yes, I can..." It is indeed actionable. It can be acted on. If I ask, "Is there some action required on it?", I always say, "No, of course not. I can avoid this e-mail as much as I want. Nothing is necessary about this e-mail."
The answer to "Is it actionable?" is always "Yes." The answer to "Does it require action?" is always "No." What's the real decision? The other options we see paraded around are so squishy
"Do I want to act on it?"
"Am I committed to act on it?"
"Do I intend to act on it soon?"
All these are largely meaningless. You may feel one way one second and another the next
One final note: Many people seem to think that "Is it actionable?" is intended to be used as a test to determine whether some item on a list is sufficiently clear according to GTD standards. They'll say things like "The item 'Go to Europe' is not actionable; it's not broken down enough. 'Surf Web for airline tickets' is actionable. That's a step you can take." This use of the word has nothing to do with what I'm talking about here. I don't know where exactly this idea comes from. I don't think it's used anywhere in the official expositions of the methodology. It seems to be a remnant of some other context or source.
The essence of the decision in the middle of the workflow chart should be damn clear; the entire thing depends on it.