[brandonbloom]

The word "project" has meaning, as does the word "task". Not everything you want to track is a task and not every grouping of tasks is a project.

People argued over whether or not a particular sub-project should be a project or a section. People argued over when to use sections vs when to use tags. People were uncomfortable creating "tasks" for things that don't have a singular notion of "done". People argued over when to use subtasks vs top level tasks. It was just silly.

Ignoring my complaints about Asana's UI/UX, simply choosing more abstract words, such as "boards" and "cards" alleviates a great deal of cognitive dissonance when creating organizational systems for new teams and domains to be organized.

Joel wrote a great article about how this sort of thinking leads to a very different product design, and Trello's approach specifically: http://www.joelonsoftware.com/items/2012/01/06.html