[eurobubba]

Originally Posted by Brian

In most of the tagging requests that we've seen over the years, there's often little to no thematic relationship between the ones being requested. You'll see person-related ones, time-related ones, and place- or energy-related ones all attached to the same action and used simultaneously. For every N tags assigned to an action, folks want to see that action simultaneously on N lists, and those lists may 'mean' very different things.

[...]

Once you figure out which theme works best for you, though, you can build a context tree to support it - and in our experience, once you know what the best theme is, the other stuff is just cluttering up your workflow and distracting you. I think that last part is what's so hard for folks used to tagging systems to understand.

The simplicity of a single-theme approach is actually a feature; it's not a shortcoming that needs to be addressed or worked around.

One thing I think you're missing here is that there are many reasons to want to view a filtered list of tasks other than being ready to work on them. Off the top of my head, I might need to review tasks from different contexts and projects for the same client or with input from the same vendor/subcontractor, or billable versus non-billable.