[Tim Wood]

The way the app is shaping up, you should be able to get away with 'Calls' in most cases. We have another axis on which to focus your action list so that you can avoid the whole A>B vs B>A problem. I don't think we are talking about that bit publically yet :)

Hopefully most people will have a fairly small set of contexts that express requirements for actionability rather some area of responsibility.

Still, there are cases where tagging or multiple contexts, etc. would be useful (say, if you sometimes have meetings with action items for Bob and sometimes with Jane, but you also might have some items require both of them to be present to be actionable).

There are a couple main problems with tagging; UI and taxonomy fiddling. We can obviously deal with some of the UI problems, but if we add tagging, how many people are going to spend hours developing and modifying complex tagging systems, endlessly agonizing over the taxonomy to apply to each and every task?

It's certainly possible to use tagging responsibly, but it seems far easier for it to become a productivity black hole.