
What I like best about Asana is how effectively it brings structure and visibility to cross-functional work. As someone working closely with Sales Ops, Marketing Ops, and Tech Ops, Asana helps me break down complex, ongoing initiatives into clear projects, tasks, owners, and timelines.
The flexibility of Asana is a big plus — I can use it both for long-term operational projects and day-to-day BAU requests. Features like custom fields, rules, and forms make it easy to standardize intake, prioritize work, and ensure nothing falls through the cracks. It has significantly reduced follow-ups and ad-hoc communication by giving all stakeholders a single source of truth.
Overall, Asana has improved accountability, transparency, and execution across teams, especially in fast-moving operational environments Review collected by and hosted on G2.com.
While Asana is very strong for internal project and task management, it can feel limited when used for request or ticket-style workflows. Features like native SLA tracking, automatic acknowledgements, and ticket IDs are not built in, which means teams need to rely on workarounds using rules, custom fields, or integrations.
Additionally, managing requests coming in via email alongside form submissions can sometimes feel fragmented, especially for operational teams handling high volumes. More robust reporting around ageing tasks and SLA breaches would also be helpful for operational oversight.
That said, these are manageable gaps for many teams, and Asana continues to work well as a flexible and collaborative platform when combined with clear processes. Review collected by and hosted on G2.com.