Asana Reviews

Asana is used to manage all tasks, including purchase requests, facilities requests, legal matters, and accounting. Everything is funneled through Asana so that all tasks can be tracked.

A recent example involved working on a security purchase request for 2026, which required coordination with purchasing, accounting, and legal. Collaboration occurred with all three groups on a $500,000 purchase request, and it was funneled through Asana so all groups could see their status. This allowed for efficient communication about progress and resolution of questions.

Asana is used for everything and serves as the main hub for any tasks, including projects with engineering, making it essential for all groups to communicate and see each other's progress.

The best features Asana offers, once you become familiar with the system, include clarity in view and tracking of questions. For instance, if information is requested from legal and they respond, a record is maintained to track all comments and keep everyone updated.

Having that clear view and record of communication helps the team day to day by allowing management and staff to see current statuses and responsibilities. It clarifies whose responsibility it is and identifies any hold-ups with legal or engineering tasks, which keeps the organization organized.

Asana has positively impacted the organization by providing clarity for everyone, allowing visibility into who is working on what, from the VP of Operations down to maintenance, ensuring necessary parts are available. It functions as a clearinghouse for all information.

Collaboration has greatly improved with Asana. There is no longer a need to chase down accounting or engineering for project updates because information can be checked through comments. File attachment and messaging capabilities between different groups within Asana are helpful. Email notifications are received for updates relevant to tasks, combining Asana alerts with email for easy visibility.

The interface and notifications in Asana are appreciated because it integrates with email. Updates can be received even when not logged in, which keeps you informed.

Initially, it takes some time to understand the various details, but after extensive use, it feels second nature. Overall, satisfaction with Asana is high.

A rating of eight is given because a downside exists in that everyone has access and notifications are often received for projects that are not involved in, leading to quite a few emails daily, sometimes around sixty to eighty.

Asana has been used for four years.

Asana is stable.

Asana's scalability is impressive, as the organization has grown from one facility in California to another in Washington State, increasing the workforce from one hundred to about four hundred fifty to five hundred people without any scalability issues throughout a four hundred million dollar construction project.

No complaints have been heard about customer support for Asana. Work occurs closely with the IT group, and they have not reported any issues regarding support from Asana.

Positive

A return on investment has been seen with Asana primarily in time savings due to its instantaneous communication, acting as a single point for project discussions. There is no need to juggle multiple conversations across different platforms, and the search engine works effectively, allowing for pulling up historical data efficiently, which ensures all pertinent information is available.

Advice to others looking into using Asana is that it will only work as well as your commitment to it. If you expect it to operate in the background without investing time, it will not surpass other project management tools. However, with one hundred percent commitment, satisfaction with Asana is very high. A rating of eight out of ten is given for this product.

As the main project manager for my team, I own all communications and marketing projects in Asana. We have an annual impact report that showcases our organization's impact for the prior year. It covers our revenue, our expenses, any major achievements, and tells stories about families that we've helped. We set that up to be delivered in two different mediums: a digital report and a printed report. I set every task up in Asana, assign out all of the tasks, and host a kickoff meeting where all of our notes, reference docs, and to-do lists are captured in Asana. I also manage our vendor relationship with an external web development agency. I keep track of their contract, their invoices, their meeting notes, and our check-ins are all captured in Asana. Everything through launch to reporting to our after-action and closing is captured in Asana through various tasks and due dates.

Having everything in one place makes it very helpful. Our entire organization is using Asana, so we are able to collaborate cross-departmentally using Asana. There are no access issues and it keeps everything in one place so that we are not chasing people down via email or Microsoft Teams or in just different workflows. We put all of our work and communication into Asana and it runs really smoothly.

We recently started using Asana for annual fiscal year planning.

Having everything in one place makes it very helpful. Our entire organization is using Asana, so we are able to collaborate cross-departmentally using Asana. There are no access issues and it keeps everything in one place so that we are not chasing people down via email or Microsoft Teams or in just different workflows. We put all of our work and communication into Asana and it runs really smoothly.

In my opinion, the AI Asana Assistant is very helpful. When on Mondays I send out a report that captures all of the active project work to our stakeholders, using that AI assistant to quickly grab bullet points, status updates, and other information from various projects is very helpful and saves me so much time.

I feel that the accuracy and usefulness of the AI assistant's summaries and suggestions are very accurate based on the information that is in the project. It is very accurate and made my reporting easier. However, that is dependent upon my team using Asana effectively and keeping their own work up to date.

Asana has positively impacted my organization by enabling us to work more effectively across departments. This effectiveness shows up in all of the above. We are able to communicate in one platform, which streamlines everything. It gives visibility to everyone, so you are not worried about forgetting to loop someone in. Everyone has access to all of the projects that they need and can see deadlines, can see status updates, and can review and approve things quickly.

My only feedback or criticism of Asana would be the customer service. It is not amazing. I have reached out to our rep and to our salesperson about needing some help with onboarding new features and implementing certain things. It is a little frustrating because you either have to pay hourly to get Asana support, or you only get fifteen-minute phone calls at a time. Scheduling actual training sessions with Asana employees costs money outside of your enterprise membership. To me that is kind of shady because you are paying for a service. There was no Asana onboarding. They put it all on me and my boss to go through all of the Asana trainings ourselves and then figure it out. When it would have been really helpful for their customer service team to provide some hands-on training to our team and to help us actually set up our projects in the beginning.

I have been using Asana for one year.

Asana is stable.

Asana's scalability is great. It works when I am working with a small team of ten or less people, but it also works when I am organizing an event for twenty-four hundred people.

The customer support for Asana is not great.

We previously used Reich and our reason for switching was we were looking for software that we could use cross-departmentally to collaborate across the organization, and Asana just fit our needs a little bit better than Reich did.

I would highly recommend Asana. I would recommend that others go through the Asana training videos, and if they are really interested or possibly a lead on their team to go through the Asana Ambassador training. I give Asana an overall rating of nine out of ten.

My main use case for Asana is identifying the progress of tasks assigned to the team. I utilize Asana for team collaboration, team ticket generation for each task, and to collaborate through comments, which serves as the tracking mechanism for product development and project management.

For one of my current projects, whenever a new task comes into view, we have a specific team divided into front-end, back-end, DevOps, AI, and project manager roles. All team members are assigned to the specific task. Whatever task they pick up, we move it to in-progress status and then mark it as completed once the task has been finished. For example, if I want to create a background task for an AI process that will implement categorical scenarios to understand how user behaviors respond to specific video comments, we need to generate a whole pipeline-based scenario. This includes what the background of Asana's ticket should be, who needs to be assigned to this task, who will be doing this task, who is the assignee, who will be reporting this task, what will be the deadline, and what approach they have implemented once completed. All of these things are maintained in Asana, which tracks user continuity and how they are approaching specific project tickets and tasks.

In my opinion, the best features Asana offers include all product management scenarios, such as how tickets can be generated and what assignees and assigners need to be adapted. It can be integrated with external CRM tools and external collaboration tools like Slack and MS Teams. Asana also offers MCP and its toolkit, which we can utilize perfectly.

I find myself using ticket management the most among those features.

Asana has impacted my organization positively by being very useful for product management and task management. We manage internally how tasks can be assigned to specific teams and how they can be launched on specific dates. Deadline-based use cases can be completed, enhanced, and tracked perfectly through collaboration of different teams.

I would say that we are working on time for each task and can manage who can pick what kind of task by checking the specific workflow. This gives insight into what needs to be done in future ticket pipelines. Based on how many tickets are created, we can justify priorities and complete them as soon as possible. We can maintain deadlines as well. Productivity metrics such as the time of completion for any specific ticket or feature that we are building can be implemented perfectly. All of these things are maintained in a professional manner in Asana.

Asana can be improved by adding a voice-based assistant for ticket generation. Currently, everything needs to be written manually, so we could add voice integration. Additionally, calling mechanisms are not available to collaborate between the team for any specific task. If anything needs to be collaborated within the team, we need to tag them instead of having a calling mechanism to check on pending tasks. A notification system could send updates to other team members as well.

I have been using Asana for around three years.

Asana is stable.

Asana's scalability is perfect. Multiple teams and multiple team members can collaborate with each other.

I would say customer support is very good. Both email and calling support are working perfectly. The chatbot of Asana also provides perfect responses. The pre-generated FAQs offer clarity on what steps need to be included, which is sufficient.

I have used Jira prior to choosing Asana. Both tools have specific strengths. Asana is very simple to learn and understand. All workflows, Kanban boards, collaboration, tickets, and logs are maintained perfectly in both. Jira has Confluence integrated, which allows for documentation and article-based cases, giving it some advantage. However, it is very difficult to understand and maintain the content. In that regard, Asana is good, but it does not have the flexibility to write notes-based documentation.

I have used only these two solutions before choosing Asana.

I have definitely seen a return on investment with Asana. The efficiency of building the whole project has increased through team management using Asana. Multiple clients work directly with this collaboration tool, so definitely there has been a return on investment.

My main use case for Asana is exchanging tickets with customers. To exchange tickets with customers, we define the field from both sides and exchange the information or issues reported by the customer, which are then linked to Jira, allowing our development team to work on that internal ticket. Asana is deployed in my organization as an on-premises and web application.

I find Asana friendly, and the user interface is really quick. All the options available from Asana tools are easy to use by the rest of the teams, so I would recommend Asana for other customers too.

In my opinion, the best features Asana offers include ticket creation and ticket grouping. Ticket creation and grouping help my team and me in our day-to-day work because we can group the tickets based on the feature or issue categories, allowing us, as a team or as engineers, to work on multiple tickets together rather than on a ticket-by-ticket basis.

Asana has positively impacted our organization as we are able to organize all the tickets or issues in one project space, allowing me to generate status reports and present them to management, which functions as a dashboard for the high-level management team. Having all the issues in one project space and generating status reports gives management status updates, helping me prioritize features or groups that are lagging or need work, which has resulted in high productivity based on prioritization.

I believe Asana can be improved by adding more features similar to Jira, such as a detailed dashboard or detailed release planning windows, which would be helpful for elaborating on project management activities.

I have been using Asana for five years.

In my experience, Asana is stable.

Asana's scalability is impressive; it can scale to any number of engineers and teams.

Customer support is quick; whenever we report an issue, the response is prompt.

Before Asana, we previously used PTC Integrity and Jira, but we switched to Asana based on customer requirements, allowing us to have shareable projects that customers also recommended we use.

I have seen a return on investment with Asana as it has improved productivity, saved time, and reduced indirect costs.

We took Asana on a per-person basis, specifically for 50 people, and I do not remember the exact price, but it was an Enterprise feature.

We did not evaluate other options before choosing Asana, as we were using other tools, and the recommendation from our customer led us to directly start using Asana.

I would rate customer support an eight on a scale of one to ten. I would advise others looking into using Asana to go ahead and use it. One general feedback about Asana is that compared to Jira, it has fewer features and is not as organized. If Asana provides a user interface and more features necessary for project management, it could attract more customers in the market. I choose a seven because I use multiple project management tools such as Jira, Asana, and PTC Integrity, and when I compare the features, I think it is seven—not less or more. I gave this review an overall rating of seven.

We use Asana to track the activity in our department and to get a dashboard with all the information so we can present a report to the high management at the company. That is the main use. It is about technology, what we use Asana for.

What I appreciate about Asana is the easy way to get the data we need for the reports because we are moving all our tickets. We are making a copy from our main ticket system to Asana because our main ticket system is not giving us what we are looking for, so we need to process everything in Asana. We get the dashboard and analytical reports, so we can have a summary of what has been done in which department we are working with or helping. We can see how many requests for each department we are having. The easy way to get all the analytics at the end of the month or year is the most important feature, and that's why we are still with Asana.

The benefits I see with Asana are the main tools because of the integration this tool has. For example, we are making tickets but receiving requests through email, and we have the integration with Outlook and Google. We have the add-ins, so we are making the ticket on our main system while replying to the mail, and simultaneously taking this mail to complete our ticket for our Asana project.

The time we are investing through departments with Asana is valuable because we are receiving requests or updates for projects without investing time in meetings or writing emails. Because of the integration we have, we just create a project and everyone with specific tasks moves on their tasks, and we receive the updates. We created a bot that gives us updates automatically. Asana provides automation because we receive these updates the moment they happen without anyone needing to tell us they completed tasks or moved on to others.

Asana's cloud deployment has been beneficial for our remote or hybrid team operations. If someone is onsite and someone is working from home, everyone can work on the same project through automation. The person from home doesn't need to be on an infinite call with management or coworkers. They can work in real time, and once someone completes a prerequisite task from home, the people onsite will know it and get the green flag to continue their assigned tasks. It has benefits for anyone, including personal uses.

It would be beneficial to have a native option for Asana to create tickets so we could move away from our main ticketing tool. If that could be integrated into Asana, that would be advantageous for other kinds of businesses.

I have been using Asana for a year and a half, but we started to pay the subscription just three or four months ago because our team grew up, and we needed to move to a subscription.

The initial setup for Asana was pretty easy to use from the beginning. Then we started to make it more complex because we needed to use some features, rules, and automatic actions. Now if someone is watching our projects for the very first time, they might say that Asana is complicated, but it's not complicated at all.

I would rate Asana's customer service or technical support as nine on a scale of one to ten.

We tried Asana but then attempted to move to a different tool. However, because of some features Asana has, we needed to move back and we are happy with Asana.

The initial setup for Asana was pretty easy to use from the beginning. Then we started to make it more complex because we needed to use some features, rules, and automatic actions. Now if someone is watching our projects for the very first time, they might say that Asana is complicated, but it's not complicated at all.

I have seen ROI with Asana because we are moving faster with our projects due to all the details mentioned before.

I considered Notion, but I don't really remember the names of the other tools. The features that Notion didn't have that Asana did have, which we absolutely needed, were the reporting and dashboards. Notion has a kind of dashboard, but it's not the same. At the moment we were trying Notion, it was necessary to keep updating the info manually. With Asana, it's automatic because it's taking the info from all the projects and updating in real time. That is the most important feature that made us move back to Asana.

We have a subscription for Asana. I have hands-on experience with this tool. We integrate Asana with Outlook and Teams. Regarding the license, I think it's just the first tier. It was limited because we got the dashboard for reports. About a month and a half or two months ago, it was renewed. The license we are working with is the same, but now we have new features, so it's easier for us to get the reports. I'm pretty happy with the license we have acquired. My name is Carlos, and it would be alright to use my real name with the review. I rate Asana a 10 out of 10.

Asana serves as the main platform for tasking project management activities, team collaboration, workflow and process management, planning and visibility, and cross-functional coordination. It becomes a single source of truth for any project execution, collaboration, and tracking.

Asana impacts the organization in several ways. It has improved my execution clarity across different teams by showing what needs to be done, who owns it, and what the due date is. My PMO strength has increased because my governance and visibility have increased. I can now see real-time dashboards, portfolio views of leadership, and instant visibility into project health, with easier tracking of risk, delays, and progress. Decision-making becomes faster and more data-driven. The shift from email spreadsheets and manual flows has reduced operational inefficiencies.

The best feature is end-to-end project management that encourages real-time collaboration across multiple projects. I can utilize list, board, and timeline views while prioritizing my work and syncing with my calendar. Asana has a very good interactive Gantt chart timeline that helps different stakeholders such as PMO, QA, and business teams view the same project in their preferred way. I can customize reports to my needs. Asana helps me clearly assign task ownership and push accountability to the respective individuals, which eliminates confusion. This is especially critical for cross-functional programs that require significant coordination and control. Asana has very good workflow automation that manages status updates, task routing, and notifications easily within its ecosystem.

Collaboration features include commenting where I can mention a person's name with the "at rate" symbol, which automatically creates a task for that person and enables real-time communication. There is no need to drop an email chain or lose any context or oversight on any task I might have missed. Real-time reporting and goal and strategic alignment between the project and project manager also help with coordination. The customization capabilities are extensive, allowing me to customize fields for tracking, validation status, priority, and risk. Templates can be repeatedly used, and forms standardize work intake. Asana is particularly well-suited for the life sciences and healthcare industry, as I have worked extensively in this specific field.

Resource and workload management features allow me to see team capacity and workload distribution and rebalance tasks actively. This prevents burnout and improves delivery predictability. Asana's recent AI capabilities automatically summarize status and provide workflow suggestions. The AI also gives project insights regarding what is going on, so I do not have to prepare a separate project review deck. I can simply take inputs from Asana, ask questions, and receive a very good overview of the projects I am working on. Asana creates good execution based on tasks, encourages collaboration, helps with reporting, and strategically enables me to do everything in one system rather than depending on multiple systems.

I have been using Asana for eight years now.

One of the recent projects I completed was Viva Vault validation for a pharma client, and I used Asana from start to end. I started with project setup where the project created was Viva Vault, and then I drilled down into different sections including initiation, planning, execution, review and approval, go live, and closure. When breaking down the tasks, I had different tasks from a validation point of view including validation plan creation, user requirement specification, functional specification, IQ OQ protocols, test execution, deviation management, and validation summary. Each task also had sub-tasks with proper due dates according to the project timelines. Asana has the capability to attach documents, templates, and comments for discussions or approval. Timelines and dependencies were managed based on deliverables. For example, I had to complete URS, FS, and configuration before testing and release. The dependency for testing was the functional specification, so testing could not start until the functional specification was complete. This helped the PMO track delays and identify the critical path for the entire project.

Regarding collaboration and communication, all discussions happened inside the task with no emails. Stakeholders were tagged for different approvals including QA, business, and IT. Real-time status updates were implemented. Dashboards and reporting showed the percentage of completion of validation activity, open versus closed deviations, and any tasks that were at risk or overdue. I held weekly governance calls as well. For compliance and audit readiness, documents attached to tasks served as a centralized repository with active history maintained showing who did what and the delay between review and approval. This helps produce evidence during audits or inspections.

AI capability made a significant difference because I did not need to go inside each project to see what was happening. I could get an overview and summary of the entire project instead. Task ownership and accountability also made a big difference because ownership often becomes ambiguous when multiple stakeholders are involved. Without clear ownership, follow-ups require constant intervention. Dependencies can cause delays, and it becomes unclear who is responsible for what. Asana streamlines this by ensuring every task has a single owner and a clear deadline. Sub-tasks ensure granularity and accountability with no gaps in execution. Dependencies are obvious because Asana shows who is blocking whom and what the dependency of that particular task is. Real-time visibility shows where the task is actually being held, which gives me actual impact by providing a faster execution cycle, reducing coordination overhead for the PMO, and improving stakeholder trust, especially on client-facing projects. Better audit readiness is captured. The single biggest impact came from clear task ownership because once everyone knew exactly what they owned and when they needed to execute, the work became more predictable and efficient.

My single-person dashboard shows everything assigned to me across multiple projects in one place, prioritized based on due date and urgencies, so I do not have to juggle between projects. A small but powerful feature is the My Tasks view, which acts as my daily control center, prioritizing work from my start of the day to the end based on due date. I can prioritize very quickly and easily, and the tasks align based on project criticality as well. Some projects require really quick attention in terms of escalations or lagging away from the deadline, which I can easily see on the My Tasks board. I rate this product nine out of ten.

My main use case for Asana is management and documentation. We use Asana to figure out how to work together on teams, feature planning, and feature feedback.

Some of the features are proprietary, so I cannot go deep into anything, but when we are working on something, it is typically two persons on it going back and forth on the document figuring out how to work together and what to collaborate on.

The deadlines work really well, the timelines work really well, and the views work well on all devices because we use it on mobile, tablets, and laptops.

In my opinion, the best features Asana offers are collaboration.

I have experience with integrations. We are a Slack team and then we moved over to Teams, so the integration from the bot integrations that we have give you notifications based on timeline deadlines, and those things work really well and we appreciate those.

Asana has positively impacted my organization as we have moved from a team of five persons to currently a team of about nine or twelve persons over the last two to three years, and it really helps.

It is the go-to tool for reviewing items in specific places, and it lifts some of the work when it comes to collaboration, making it easier for us.

Asana helped with that growth as we are at approximately seventy percent efficiency on the team because we have a go-to tool that helps us with managing our documentation and eases us with collaboration.

Asana can be improved, but I would need to dig more into that to give a thorough response.

It would be nice if we could integrate it with Telegram or with something comparable to Open Law or Hermes, but I have not checked the availability.

I still worry about Asana's governance and security because the language around it is ambiguous since everybody keeps changing based on regulations rather than the customer's needs.

Asana's parent company's needs are more important than the customer's needs, and the training data that is used is interesting.

Regarding Asana's AI capabilities, its accuracy and reliability of output are still at best okay; it still needs to be worked on, but it is coming along.

I have been using Asana for four or more years.

Asana is stable.

Asana's scalability is really scalable.

The customer support is good.

To my knowledge, I did not previously use a different solution.

I have not seen a return on investment, so I cannot share relevant metrics such as time saved, money saved, or fewer employees needed.

The pricing, setup cost, and licensing were not my wheelhouse, as I just got access.

I am not certain if I evaluated other options before choosing Asana.

I would advise others looking into using Asana to read the use case and figure out if it fits your needs, but generally give it a try before you say no.

I would rate this product an eight out of ten.

I work in restaurant technology with Asana.

I think it's very user-friendly on their Kanban boards for Asana. It's very easy to use for everyone in the team. They have a good tool for the portfolio aspect because we have projects in different areas. Their new capacity planning is also useful for us to see where we are overloaded and how we can shuffle resources around. The fact that the Kanban is so easy to use and the portfolio functions are particularly valuable.

We have benefited from Asana's visual interface components such as Kanban boards. I did not use their Gantt chart, but they have good features and there is substantial visibility among team members because they can see who's working on what. It's easy to use and very friendly.

Asana takes one of the highest priorities for us for reviews.

Asana gives visibility to upper management with the workload and all the other projects that are going on at this point in the company.

The capacity planning in Asana is working pretty decently, but there are some opportunities there for sorting, such as determining which project has the highest resources, as their sorting doesn't work that effectively. The capacity planning sorting and visual aspects could be improved.

We started using Asana approximately two to three years ago.

I'm in touch with Asana's sales account manager only. I learned it on my own. Their website has many areas of training, so it's very comprehensive. If you have any questions, you can use the search function and receive many good answers.

I would rate eight to nine for my experience with either the sales representative or the online support.

Positive

The initial setup with Asana was not straightforward because you had to think of where you want to go. It's somewhat tedious because you have to add it project by project, but it's part of building a portfolio. While it was more challenging in the beginning, for an end user, it was not that complicated.

There are main differences between Planview and Asana in my opinion, with Planview being much stricter. There are too many controls on it. Planview has more reporting capabilities and is more detailed. However, for what we need right now in our organization, Asana works pretty well.

It would be acceptable if my real name was used with this review.

It can be public for my company name.

On a scale of 1-10, I rate Asana an 8.

My main use case for Asana is ticketing, specifically software ticketing and task ticketing, where I manage tasks and manage task issues.

The best features Asana offers for managing tasks are agility and flexibility.

Asana has positively impacted my organization by providing flexibility, improving time to market, and enhancing collaboration.

I think Asana can be improved, but there is nothing I wish worked better or features I would like to see added.

I have been using Asana for two years.

Asana is stable, and in my experience, I can affirm that it is stable.

I have not experienced any stability problems with Asana.

Asana's scalability for my organization is good; it is good enough.

The customer support for Asana is good.

Negative

I did not previously use a different solution before Asana.

My experience with pricing, setup cost, and licensing for Asana is good for on-premises.

I did not see a return on investment with Asana, and I cannot share any relevant metrics, such as time saved or improved efficiency.

Before choosing Asana, I did not evaluate other options.

I would not recommend Asana to others looking into using it. My company does not have a business relationship with this vendor other than being a customer. I would rate this product an 8.

My main use case for Asana is project tracking.

Whenever we are assigned new projects, we enter the project information in Asana, which lists the different team members on the project team. We can share and exchange information as well as track progress of all deliverables for the project.

The best features Asana offers include project tracking, communication between project teams, workflow automation, reports and dashboards, and cross-functional coordination.

The feature that has made the biggest difference for my team is the cross-functional coordination because it allows communication between the internal team as well as the external teams that are involved in the projects.

Asana has positively impacted my organization through the coordination between all of the different players on different projects, and the tracking and assignments are very streamlined.

Coordination and tracking have become streamlined because everything is instantaneous, which is always beneficial in a project.

Asana can be improved by continuing to stay current and evolve with technology as technology evolves.

I have been using Asana for two years.

Asana is stable.

Asana's scalability is strong because it works with tools like Microsoft Teams, Slack, Google Workspace, Outlook, Jira, Salesforce, and Power BI, which makes it scalable because it functions with all these different platforms and tools.

I have never had to use customer support.

Negative

I do not have visibility regarding return on investment; I am an end user.

My advice to others looking into using Asana is that it is flexible and it has strong collaboration tools, and I would encourage them to take advantage of those tools.

My company does not have a business relationship with this vendor other than being a customer.

I would rate this product an 8.