I have used Asana as a part of a few student and non-profit organizations, and that I just received the daily tasks digest in my inbox as I'm scripting this. I do know I represent my fellow team members when this is often one email that quickly goes within the trash or gets ignored.
We've found that Asana is a smaller amount than optimal for projects which involve an outsized amount of open-ended work, like organizing and event planning unless the team is fully committed to Asana for reporting and task management. It's just too much work for people to return back to the system all the time.
It's also probably not ideal for keeping track of huge numbers of the latest projects. there's a statistic somewhere that says creative workers (artists, researchers, etc.) need to keep 30-60 potential projects on the radar in the least time. The flat architecture of Asana makes it so potential projects need to be collapsed into one line; it doesn't substitute for a notebook. It is often hard to stay "scraps" of data in Asana, especially compared to non-public task management systems like Things and Omni Focus, in spite of its support for notes.
The subtask system requires you to be focused on one task at a time - again, a consequence of Asana's roots in software development.
The comment feed is great, but you actually need to be committed to Asana to use it.
When that's all said, Asana is an awesome task tracker for a bigger start-up or corporation where there are clearly defined projects. The Workspace Overview does a pleasant job of mixing relevant context alongside personal tasks for a classic Product Manager/Project Manager. The UI is additionally really neat. But like any tool, half knowing is knowing when to not use it.
Comments