Asana Reviews

I use Asana for advanced use cases, including managing software development and other projects.

With one particular project, we manage the development activities with around twenty people on the project team and about five hundred tasks, for which Asana helps to manage our sprint planning.

The most valuable features of the solution are the different views, including the list view, table view, dashboard, and the ability to add fields or customize by adding some specific fields for a project.

The calendar view in Asana has shortcomings and can be improved. The other element is the ability to natively be able to add additional connectors to better manage the planned time versus the actual time for each task.

The timesheet aspect is an additional feature I like to see in Asana since we now use another application called Toggl for managing our time cards. It would be better if we could do what we do in Toggl directly in Asana since it would be easy to plan activities.

I have been using Asana for a year and a half. I use the solution's latest version.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a seven out of ten.

The initial setup was straightforward.

The solution is deployed on the cloud.

I have not specifically seen any ROI using the product. We use it as a part of different tools, so it is like looking at the ROI for an email, which is a part of the tools we need.

To those planning to use Asana, I would say there are many similar applications. It can be hard to choose from applications like monday.com, Asana, ClickUp, and others since they are all good for collaborative project management for smaller projects, which have not quite reached the level in terms of capabilities to manage very large projects. I have managed projects ranging from 25 million USD to 50 million USD, and I feel Asana cannot operate at that level.

Overall, I rate the solution an eight out of ten.

There are two main things I use it for. The first one is lead management and opportunity processing, internally in my organization, project management, and task creation. The second thing I use most is support inside the community of Asana. I'm an ambassador of the Asana community. I also use Asana for this type of support.

Before Asana, we didn't have a tool to control our leads or our opportunities. It was just by memory. If we were talking with a client, we were just thinking about calling that lead or that client in a day. With Asana, I have my leads more organized. I know when to call. I can go back and see what I said on the last call, or what I emailed the last time we contacted them. It's an easier way to keep up with my prospects and my opportunities.

The best feature is how easily you can create rules. You can do it just via point and click. I like how easy it is to use the rules within Asana.

The initial setup was simple. 

Asana has a site available where you can check the status and see if it's working or in the middle of downtime still (when downtime happens).

Technical support has been excellent. 

One of the main things I've been wishing for is an ID, a short ID, just like Jira. That is another tool that I used before. It has an ID for every task in Asana. So it's a short way to know what task are you writing your things on, and it's easier to control your activities. 

In Asana, there's no way to add a custom date field. That's another thing. 

Both of those functionalities I'm wishing for, or I'm hoping for in the short term.

Occasionally, Asana does go down.

I've been using the solution for less than a year - 11 months or ten months, probably.

Since we've had Asana, we have been down twice for two to three hours each time. Asana provides a website to know the status of Asana in general. It's an easy way to check if Asana is down or not. We know that every tool has these types of failures. We wish we don't have any more failures, however, we may continue to have them. That said, Asana is excellent in how they provide the status of Asana in general.

The ability to scale depends on the implementation within your organization. However, the scalability is there to do it on your own. You can have a thousand employees using Asana. I don't see any problems scaling up using Asana.

Right now, we have about 50 people on the solution. We use it quite extensively.

When we need support, we have a VIP support channel as we are an Asana partner. We have Asana support directly with the Asana support team. We are extremely satisfied with the help we get. 

Positive

Besides Asana, we work with Salesforce, Twilio, and Slack. I've used Jira in the past as well. 

We did not previously use a project management solution at this company.

I was involved in the initial implementation. It was straightforward. The difficult part of this type of implementation is how you structure your teams and projects within Asana, however, how you use Asana to do this is intuitive. We didn't have any problem with how to accommodate or establish those things. I'd rate the simplicity of the implementation at a four out of five.

The deployment didn't take more than two weeks. 

The maintenance is easy. It's very smooth. We do not require a maintenance team, however, we do have team leaders that will do occasional maintenance. 

We handled the implementation in-house.

I don't have exact ROI numbers, however, we've seen time investment hours and we know that each hour counts as money. We've seen some return on investment, in time, in productivity. Those two KPIs have seen marked improvements.

We are Asana partners.

I use the most recent version and I use it every day.

I'd rate the solution nine out of ten. It's a great way to organize your daily work within your organization. It doesn't matter your team or the department you're working in. It's very flexible. 

I have used Asana while working at an e-commerce agency while working on creative projects and creating content like ads for Amazon or Walmart Connect. We used Asana to keep individuals within the agency updated on projects, even if they do not work within the creative team. 

When I worked at Claire's stores as a digital project manager for their internal digital creative team, we used Asana for different departments to log requests for creative projects. We also used it to manage the projects within the digital team. 

Asana allows you to create your own project with sub sections with subtasks that can be assigned. The feature I really love is that you can tag people to notify them that there has been progress on a project as well as add attachments. It is a central depository for everything. It is also really useful that you can add people outside your organization to projects you are working on. 

The use of Asana can be restricted if it is not set it up the right way. In some instances, there were subtasks where more than one person needed to review it, but I could only assign it to one person. I would have to create a subtask under a subtask and then assign it to other people. This could be improved. 

I have been using this solution for a year and a half. 

I used Basecamp and JIRA prior to Asana coming out. JIRA is used more for software developers or backend development projects.

The initial setup was complex because the onboarding is not done correctly. This is due to the fact that we are short staffed and did not have time to be trained. Once we had spent more time using the solution, it was easier to use and understand.  

This solution is reasonably priced. 

I would highly recommend Asana as I think it's a great tool. It is really easy to use once you are trained on it. It really helped me effectively manage projects and improve productivity and efficiency. It has a lot of options from an integration perspective with other platforms.

I would rate this solution an eight out of ten. 

I work on a marketing team in a position that was created to implement a CRM Communication Program for existing customers. Because this was a new position and I was new to the company, I was tasked with collaborating with several people across multiple teams. In my experience, it's very difficult to get work done effectively without some kind of project or task management tool. After trying out various online solutions, I learned that one of our divisions was already using Asana so I figured I would give it a try.

Asana has helped me (as an individual contributor) organize my daily work and given me a way to plan for longer term objectives. I initially started using Asana just to manage day-to-day tasks, but as I became more comfortable with the software, I also began to use it as a way to capture campaign ideas so I could eventually convert them to projects and track them. I also started to use the Portfolios feature as a way to report high level statuses of all my work to my manager. Having a portfolio for him serves as an executive dashboard.

In addition to the Portfolios feature benefits, I find the ability to create custom project templates very useful. Creating projects can be time consuming, especially if they are complex (e.g., many tasks, multiple dependencies, multiple sections, etc.). Even copying a project to reuse it (which is common in a lot of other solutions) can create more work by duplicating unnecessary information. Instead, Asana allows a user to use any project as a template that can be selected when creating a new project. So, I have created base projects for various types of projects with only the tasks that would be completed and then use those as templates.

While having custom templates is a big benefit, I see a lot of opportunities for improvement in Asana's execution of the concept. A user should be able to identify an assignee for specific tasks or task types while applying the template, or at a minimum, allow for a default assignee. As it is, the template gets created with the just task dates driven by the project start and end dates inputted by the user. In my current situation, I'm assigning myself to many tasks, so I have to do that manually every time. Even if I eventually start adding other people to assign tasks, there won't be more than a handful to do. However, those few people will have multiple tasks. It would be nice to be able to select those individuals during the setup rather than having to do so manually once the project has been created.

Nine months.

I have not experienced any issues with stability.

It is very scalable.

I have not had any interaction with a support team as of yet.

I previously used Jira at a different company to manage a different kind of team.

We're not using any custom features that would require setup from the vendor.

Use of vendor services was not required.

I have not calculated an ROI tied to using this software.

Asana has two different types of structures: company vs workspace. Company is really best if all the users you plan to assign work to are all internal (have the same corporate domain in their user ID email address). Once one person signs up (even for a free account) with a corporate email address, Asana will automatically relate that person to that company, if it already exists. If you plan to use it for external collaboration as well as internal, then creating a workspace is a better approach.

Before deciding on Asana, I tried Trello, monday.com, and ClickUp.

It would be nice in the future to add the ability to customize the colors of the interface and add company branding.

We primarily use the solution for project management and communication on projects.

We're still in the process of learning it, so I can't say that it's improved the organization tremendously yet, but our whole team understands its value and we just need to implement it. The onboarding process has been a little bit slow, just getting everybody to use it and moving away from our old habits.

The ability to build subtasks and break things down off of our major tasks has been very valuable.

The world is moving to a lot of video-type communication and having a quick way to do video inside the platform or communicate via video from one person to another could be very handy. In a couple of other platforms, I have looked for a way to communicate with the team with a short 30-second video that I can just click on, record, send, and be done with it.

I don't think it needs additional features as much as having a way to onboard the team and having a better way to get everybody accustomed to using it. That's what we need to figure out. I don't know if that's anything that Asana can do as much as it is just figuring out how to build an implementation plan for the product on our end.

I have been using Asana for about six months.

It is very stable.

I think it's extremely scalable. I'm questioning how I can use archives, how I can resurrect old projects, and how to add on to old projects. Before we can ever get to that level, we have to implement the projects we have. So the long-term roadmap in my mind is: What does it look like if I want to resurrect an old project, add onto it, keep or duplicate it?

Right now, there are only four of us in the company, so we're only implementing the product across the four of us and that's just super, super simple.

It was very simple. By the end of the first day, I had a pretty good grasp on it. I think the rest of the team saw implementing the projects as a little too much work, and I think that was part of what limited our process. Moving from pen and paper, or moving from a whiteboard, into a digital platform involves a shift of mindset and a shift of processes. We didn't do a good transition from old-school processes to new-school digital processes.

For what it brings to the table, I think Asana is fairly affordable. There are some features, such as portfolios, that I would like to see included at the level we're at. I think to pay extra for some of the portfolio features is unrealistic at this point, especially for a small startup company like ours. I would like to see that feature in our pricing plan right now, but other than that, it's definitely pretty good.

I looked at monday.com and at Trello. I looked at several different systems and landed on Asana for project management as we really thought it would bring the best value to our team.

I would advise others looking into Asana to investigate the other platforms, but more than anything to know what they want when they go out and look for a platform. I didn't have well-documented what I really, really wanted, and that required me to chase a lot of rabbit trails and actually test some products, which wasted a lot of my time. If I had down on paper what I really wanted, Asana would have risen to the surface really quickly, but I was not well-prepared for what I was looking for.

As a whole, I would rate Asana as a 8.5 to 9 out of 10.

Asana is highly beneficial for extended projects that require a strategic approach. It allows us to dissect these projects into numerous tasks and effectively prioritize them based on their deadlines. Moreover, Asana facilitates seamless collaboration across various departments, emphasizing the significance of time management and strategic thinking. Additionally, it aids in allocating resources within my team, ensuring efficient execution of the pertinent project.

Asana, despite its compact size, proves to be incredibly valuable. When initiating a project, it offers the ability to generate a personalized form for clients. In this particular context, my clients include the customer success team and solution architects. This feature allows me to provide them with a convenient means to submit their requests, resembling a ticketing system geared towards internal operations. Moreover, it enables efficient allocation within my team. For instance, if a question pertains to customer success, I can assign it to the CSOps manager and the team. Similarly, if it relates to a specific channel, it can be allocated accordingly.

Additionally, Asana allows for allocation across different projects, providing excellent visibility for customers who submit tickets. They can view timelines and prioritize projects, promoting transparency. The system revolves around offering visibility, prioritization of tasks, and effective delegation within the team. Despite its simplicity, it encompasses the creation of project forms with various rules. These rules determine assignments based on request type and submitter, as well as priority levels set by team leaders. Overall, Asana's functionality in this regard is highly advantageous.

The documentation could be enhanced by incorporating more visually informative videos that demonstrate how to accomplish specific tasks. While Asana's community support is valuable for answering questions, finding precise answers often requires sifting through multiple posts. Having concise and explanatory videos would greatly improve the user experience. When searching on platforms like Google, there are many individuals sharing their approaches to using Asana. However, the information provided is often not directly applicable to one's specific needs. Therefore, it would be advantageous to have comprehensive video tutorials that address common user queries. This would provide a more efficient and intuitive way of accessing information, especially when it comes to learning how to navigate and utilize Asana's features effectively.

Asana offers a variety of view formats that provide different levels of visibility. These include board view, list view, timeline view, and dependency view. For a single project, you can explore multiple views depending on your objectives. If you're working on a long-term project, you may prefer the timeline view to track your progress and have a macro-level overview of where you stand. On the other hand, for more granular tasks, the board view can be helpful in monitoring the progress and visualizing how things are advancing. The choice of view is not merely a feature selection but rather a decision based on the visibility it offers for your specific needs.

I have been using Asana within the last 12 months.

The solution is stable.

I rate the stability of Asana an eight out of ten.

We have a few hundred people using this solution in my organization.

I rate the scalability of Asana a seven out of ten.

I did not contact the vendor's support.

I did not use other solutions similar to Asana.

I did not evaluate other solutions before Asana. It was always deployed in my company when I started working.

I would recommend Asana to others.

I rate Asana an eight out of ten.

We use Asana for project management and task management.

Asana has a wonderful user experience that is very easy to interact with and has tons of integrations with other products and tools.

Asana should provide the ability to have read-only users. Sometimes, I need to collaborate with people external to my organization, and I would love to invite them to my Asana board and assign tasks to them. Sometimes, these are short collaborations. I work in marketing, and sometimes I work with agencies.

I would love to do project management on my side, which would be way easier. It's difficult to have short-term collaborations with external users because the operations team owns the final licenses, and I work for marketing.

I have been using Asana for five years.

Asana is a highly stable solution.

I rate Asana ten out of ten for stability.

Around 250 to 300 users are using the solution in our organization.

I rate Asana ten out of ten for scalability.

I have previously used different tools like monday.com and Productive.

I am using the latest version of Asana. I was not involved with the solution's setup, but I was involved in onboarding the users, which was very easy.

I have contacted Asana's technical support with questions on how to do advanced things. Asana provides you with extensive documentation and documentation on the API so you can develop your custom integrations.

The more people use Asana, the easier it is to collaborate, and you will reduce a lot of messaging, email back and forth, and all those not-very-smart things that take a lot of time. Anyone who is considering using Asana should maximize their potential. Asana has many features like approvals, workflows, and automation, and it's best to spend some time learning them.

We were forced to take two hours of our time to learn how to use Asana, and it's a life savior. You can see people using Asana like any other tool, and then you have advanced users who utilize all the potential and boost productivity. You can really tell the people who are proficient with Asana in terms of productivity.

Overall, I rate Asana ten out of ten.

We are using Asana to send tasks or tickets to different departments internally, inside the company.

It has helped our departments maintain visibility. If you're tagged in there, everybody can see it. It's different than emailing and being CC'd. If you have 30 emails before you became CC'd and then you have to go and read through each one of them, scroll down to the end to understand what's going on, it can get messy. Here, everything looks much better and it's much easier to understand what's going on.

The visibility is great. The fact that everybody can see all of the tasks, and all of the comments, is super helpful. If you are tagged inside this task, so it's very easy to see. The interface looks really nice and it's really simple to get around and view everything, especially the items directly related to your work. Task management and distribution are awesome. 

If you are not tagged in the task specifically, even though the task is in your department, you're not going to get notified that there is a new task for your department. You need to constantly have the assignment program open, so you can check in and basically do the tasks that are new, to assign them accordingly. 

From my department, if I send a task to a different department unless they open it and tag me personally, I'm not going to see this task anymore. That's a little bit tricky for us. We need that to be changed.

We don't get enough notifications. Everyone has to keep opening up Asana to check and see the tasks. If something isn't tagged, it won't show up in anyone's notifications.

I've been using the solution for three months. 

The solution has been quite stable. There aren't bugs or glitches and it doesn't crash or freeze. It is reliable. 

We haven't had an issue with scaling per se. However, we would like the visibility to expand beyond our department. There aren't enough notifications and everybody needs to open it up all the time to check tasks. 

We have about 100 users on the solution currently. It's used by all departments, including IT, back office, customer support, operations, partner department, management, and compliance.

We switched to Asana from Freshdesk. We also used to use Zendesk for ticketing. In my previous companies, we might have used Skype or Microsoft Teams or just plain email to communicate items to each other. 

We used to do emails basically and were CC'ing everyone. Then we went to Freshdesk as a ticketing system. Everybody wants to have Asana for the reporting system. It's much better to use Asana as everybody can see it. The managers and heads of departments can actually see what you're doing, and what each of their team members is doing all of the time.

We used Freshdesk as an email ticketing system, with clients mostly. It was not internal usage. Asana is better for creating tasks and having visibility without having to email people to inform them of tickets. 

I wasn't a part of the implementation process.

Our IT team handled the implementation. 

I'd recommend the solution to others. It's very useful and the interface is easy to use. As with any program, you need to get used to it, however, and maybe I'm just not used to it yet. Maybe they use notification alarms that I am missing or maybe they can be set. That's the biggest issue for us right now. In any case, the way it's set up, it's really nice. You can mark items as complete and you can mark is in progress. It's simple.

I would rate the product eight out of ten. If the alerts and notifications were better, I would rate it higher.