If Google Tasks puts all its chips on integration, Asana takes the opposite approach and scatters its strengths all over a wide swath of features that make it a clear stand-out if you’re working with a bunch of goons you’ve got to boss around.
For my purposes, and in general as a solo task manager, spending a lot of time assigning things to ‘me’ and tracking ‘my load’ and such means a whole lot of wasted effort. Like buy a big truck when you live in the middle of the city, or a Rolex when you just need something to tell you the time – it’ll get the job done, it just may not be the right tool.
But boy oh boy if you like pretty interfaces with lots of color, unicorn sparkle animations, and options to include head-shot circles of every team member so you can stare at their stock-photo smiles every time you’re once again delaying the due date because of their incompetence, Asana is for you.
All this, of course, presupposes that your team-based environment isn’t on some other enterprise project management software like MS Project or even a moldy set of Excel spreadsheets running macros like that weird guy you once knew that now runs seemingly every marathon and posts endless pictures of each of them.
Anyway, point being, Asana is going to fit those groups that don’t have an integrated solution but depend on team-based timing to get things done. As a writer, even those outside folks I work with aren’t going to bother getting Asana just so I can send them tasks that they could do by email. And if they’re not going to buy into the system for me (one client), then it’s not worth it for me to deal with all the extra fields for what amounts to a splashy to-do list.
You’ve fought a good fight, Asana, but this just isn’t your war to win.