I try to use a similar method with all of my business communication, though systems like this work exponentially better when everyone in an organization is using them–meaning, everyone does it, and everyone understands it.

However, I think something is missing: a lot of the work I do requires what amounts to miniature RFIs. So one other category of email is “Request for Information.” Examples include:

“Who are the associates you would recommend to prepare and give the presentation to the board next month?”

“Which days are you available for the conversation with that potential partner?”

“When do you estimate the project will be finished?”

There should be an equally rigorous set of recommendations (and expectations) for response to questions like these. I think the onus is on the sender to set the parameters:

“I need to hear back by Friday.”

And then the onus is on the receiver to either respond with an answer by the set date or to reply immediately that the date won’t work:

“I won’t have the full project map from the contractors until Monday. Can you wait for a reply until then?’

This complicates things (it’s not a simple Yes/No, with an implied Yes) but it’s also reflective of a lot of everyday work.

What do you think?

This reminds me of the IBIS framework established by Jeff Conklin to address “wicked problems,” in which all chunks of a dialog are characterized into one of a few types: Questions, Ideas, Arguments (in support or opposition to the Ideas), etc.

Compendium is a tool for mapping these dialogs using IBIS. The result is mind-map-like illustrations of the flow of conversation. Fascinating stuff, if you ask me.
http://compendium.open.ac.uk/institute/about.htm

Best, Noah