Most project tools fail at the same place: the moment work passes between two people. Asana's whole design is an argument about that moment — one assignee, one due date, one place the next step lives. Six weeks with a cross-functional team told us whether the discipline survives contact with real work.
Structure that holds
Sections, subtasks, dependencies and milestones behave predictably, and the timeline view is the clearest implementation of Gantt in this category. When a dependency slips, downstream dates shift and the owners get told. That sounds basic. In practice it is the feature that removed our weekly 'where is this' meeting.
The My Tasks view is the other quiet win: everyone gets one honest list, sorted by date, drawn from every project they touch.
Reporting leadership will actually read
Dashboards and portfolios turn scattered projects into a status page without anyone building a spreadsheet on Friday afternoon.
- Portfolio health rollups took our status reporting from an hour a week to zero
- Goals link strategy to the projects underneath, if your organisation works that way
- Workload view exposed that two people were carrying 60% of the open tasks
Where it is weaker
Automation rules are simpler than ClickUp's and hit their ceiling sooner. Custom fields and forms are good but not endlessly configurable. And the price steps up sharply — Advanced at $26 per user is a real budget line for a twenty-person team.
Who it suits
Marketing, operations, agencies and any organisation where several teams depend on each other. Engineering teams will still prefer Jira or Linear. Very small teams will find ClickUp or Trello cheaper and lighter.
Verdict
Asana is the choice when the problem is accountability rather than features. Six weeks in, our test team had fewer dropped handoffs and one complaint: the bill.