What do you like best about Asana?
Clear task ownership: every task can have one owner, so responsibility is obvious.
Good visibility: projects, sections, timelines, and boards make work easy to track.
Strong collaboration: comments, attachments, mentions, and status updates stay in one place.
Flexible views: list, board, timeline, and calendar support different working styles.
Subtasks and dependencies: useful for breaking work down and showing what blocks what.
Good for cross-team coordination: marketing, ops, product, and IT can work in the same system.
Automation: recurring tasks, rules, and notifications reduce manual follow-up.
Portfolio and reporting features: helpful for managers tracking multiple projects.
Integrations: works with Slack, Teams, Google Drive, Outlook, and many other tools.
Clean interface: easier adoption compared with heavier project management tools. Review collected by and hosted on G2.com.
What do you dislike about Asana?
Can become messy fast if teams do not follow standards.
Reporting is decent, but not always deep enough for advanced analytics.
Complex projects can feel harder to model than in Jira or MS Project.
Dependency and timeline features are useful, but not always enough for heavy project management.
Too many notifications can create noise.
Subtasks and task relationships can become confusing in large projects.
Limited native support for very technical workflows like code/release management.
Automation is useful, but more advanced logic may need paid plans or external tools.
Permissions and governance can feel limited in some scenarios.
Users may treat it like a chat tool and avoid keeping fields structured.
Search is helpful, but finding the exact thing is not always perfect in large workspaces.
Pricing can become significant as the team grows. Review collected by and hosted on G2.com.