Asana Reviews

Our marketing and communications team uses Asana as a project management and communication program. We input all of our marketing projects and their related tasks and assign each task to a staff member with a due date. This allows us to track our work's progress in Asana.

Asana has significantly reduced the number of emails we exchange because we can access the project directly. It organizes all the tasks related to each project, assigns them to staff with due dates, and tracks progress. This creates a historical record of our projects tied to specific dates, allowing us to review what we did last year and ensure that projects are updated. Asana has systemized our work by ensuring that every project has the same tasks, including peer review and proofreading. This has reduced mistakes and improved the quality of our work.

The solution's most valuable feature is its ability to keep us organized and on task.

Improvement-wise, I would like more options for changing notification settings. Currently, there are only a few available options, but it would be helpful to have more control over the notifications received. For example, if you are on a project, you can receive every notification related to it, even if the task isn't yours.

It would be interesting if Asana could integrate with email platforms like Outlook and on, Gmail, and Google Calendar. This way, when a project has a due date, it could automatically appear on people's calendars.

I have been using Asana for a year and a half. Also, I believe that I am using the solution's latest version. Specifically speaking, it is a cloud-based version.

Stability-wise, I rate the solution a ten out of ten since it has never gone down while we were working on it.

Scalability-wise, I rate the solution a ten out of ten. So, depending on your subscription, I think you can add a significant number of users.

I don't have any experience with technical support.

I think the initial setup was pretty straightforward. We had help from our IT department, but I don't believe the process was complicated.

I have experienced a return on investment using the solution.

Price-wise, I think it's an affordable option for mid to large-sized companies.

It would be beneficial for users to take some time to consider the different types of projects they have across various categories and to create those categories before inputting the projects. This way, the system will be more organized and easier to search. If projects are simply added as individual items without any categorization, managing them can become overwhelming. Overall, I rate the solution a ten out of ten.

We are a software company and we have many different software projects with 10 to 15 developers working on each project. We use to Asana to manage each project, for team collaboration and to assign tasks to the team. Basically, we use Asana for project management and collaboration.

We have not used Asana on our private server. We have only been using the cloud solution. We need an on premise solution for government agencies. This would be an improvement if this was possible.

We have been using this solution for six years. 

This is a stable solution. So far we have faced not any problem with the system slowing down or lagging. 

We have 150 full-time employees in our organization and for our use case, Asana is sufficient. We don't know if we can handle over 500 or 1000 users at the same time. We have not tried yet.

The initial setup is straightforward. It was just a few clicks to get started and to integrate Asana into our existing business system. It took 15 days to fully implement our projects using Asana.

We have a monthly subscription.

I would rate this solution a nine out of ten. 

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.

In my company, we use Asana for project management tracking.

Asana helps us in our company to split tasks and assign them to different people. Asana allows each one to individually update the task completed, which can be tracked and visible to all the teams in the company.

The most valuable feature of the solution is its project management tracking systems.

There is always a constant need to update the product to be able to give it more features in terms of tasks like adding commands or nodes. The product's page is not user-friendly. In general, the product's page should be more friendly to use. Asana does have all the things the user requires, making it a good product.

I have been using Asana for a year. I am a customer of the solution.

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

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

We had multiple teams working from different countries in the company, with Finland being the place where the main office was located. There were only 30 users of the solution in the company.

The solution's technical support was okay. I rate the technical support a seven out of ten.

The technical support would respond through a chat system and get back to you at a later stage, so instant support wasn't available.

Neutral

I rate the initial setup a seven, on a scale of one to ten, where ten is the best.

The solution is deployed on the public cloud.

To be frank, I don't know the time taken for the deployment because when I joined the company, Asana was already a subscribed tool. I was not the person who had subscribed and deployed Asana in the company, making me just a user.

I was not involved in the pricing part of the product since it was done by development teams and my manager in the past.

I would like to tell those planning to use the solution that the product is a good fit for medium and big companies. I suggest small companies go for the lighter version of the solution sensitive, more simple. Asana's version, meant for medium and big companies, has more features and functions.

I rate the overall solution an eight out of ten.

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 used this solution for project management and to keep track of the projects we are working on.

This solution is easier and faster to use compared to Jira. It's not very structured and you can add sub-tasks and issues easily. You can add other projects within the same screen.

If you have been using a tool like Jira for many years, it make time some time to get used to the minimalist layout in Asana. Once you get used to it, you may find it easier and faster to use than Jira. 

I have been using this solution for four months.

This is a stable solution. 

We have not witnessed any limitations on scalability. 

We previously used Jira.

The initial setup is straightforward.

If you are looking for a minimalist tool that is flexible and offers a to-do list and project management, I would recommend Asana.

If they want something more structured and integrated with an extended SDLC tool set, I would recommend Jira instead.

I would rate this solution a seven 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.

Our marketing team has four people who use it exclusively for marketing projects.

There is one super-user/administrator who is a marketing coordinator and is in charge of setting up projects and assigning tasks. The rest of us operate within the framework she has established.

The ability to share projects and tasks among team members appears to be the most valuable feature.

For large teams, scalability should be improved.

I used it on a client engagement three years ago, and have recently adopted it for our internal project. I've been using it again for two months.

We haven't seen any issues with the stability of Asana. It has been working, and everything is fine.

I am not sure about the scalability of Asana. 

If I were to scale it, I believe it is more of a team solution for a small team or an individual.

I don't see it as something that you would want to apply to a large team within an enterprise.

It appears to be best suited for a small or, medium-sized team.

Some organizations use it more widely, but I am not sure how that would work.

This solution is used by our marketing team.

I have not contacted technical support. I haven't had to deal with them.

This solution is great. I have tried a few other work management, and project management solutions and this one is the best for my requirements.

The initial setup was completely straightforward, and simple. 

We had no trouble understanding the functionality or configuring it to meet our needs. It has been a very positive experience.

The deployment is extremely easy. We are releasing it to people as they come on board, and they are adapting to it very well.

The administrator is in charge of deploying and maintaining the solution, as well as keeping it up to date.

I wasn't involved in the acquisition. I am not aware of any pricing details.

The key to successfully utilizing this project management tool is to be very clear about how it is set up, to have someone in charge of creating projects to avoid duplication and to have some ground rules around the configuration. Otherwise, it could inevitably turn into a bunch of individual task lists. There are many individual to-do list apps available, as such you don't need an app like this for that.

It all comes down to being very clear. This is a project collaboration app for teams, and for a team to collaborate on a project, there must be general agreement on what the project is, what the stages are, what the deliverables are, and so on.

I'm still exploring how to use it properly. I'm not the best person to inquire about new features, but it's very impressive, and I'm discovering a lot of great features and capabilities as I use it.

I would rate Asana a nine out of ten.