Asana vs Procore Project Management comparison

"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."

"The solution scales well."

"The way it handles the task is good. The whole team needs to organize all our tasks using Asana. It helps to clarify and allows us to prioritize tasks effectively."

"It is very good for managing the timeline. I'm a quality manager, and I have different testing projects running with different work breakdown structures. Asana makes it very easy to implement and monitor the plans. It is easy to move the tasks and complete them, break them down, and assign them to people."

"Asana's most valuable aspect is its ability to consolidate all tasks and projects onto a single board, allowing for seamless navigation through timelines from start to finish. Additionally, it enables the inclusion of key stakeholders and provides a private communication channel for discreet discussions. The organizational component of Asana is particularly beneficial, including its coding features."

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

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

"I really enjoy the portfolios in Asana. One of the ways Asana stands out to me is with portfolios. You can have all your different projects, and you can have those assigned to different teams. If you want to customize a grouping of projects, you can use portfolios. For instance, one of the things that we do is we can assign a portfolio to a specific strategic objective we have, and we can put all those projects that are related to that strategic objective in that portfolio. We then know exactly what people are working on to help us achieve our goals. So, I really like portfolios."

"Other companies have been using it for years, and it is a very stable platform."

"The financial side of Procore Project Management is better."

"The coordination between the field and the office without the need to print or physically transport drawings is very valuable."

"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."

"There could be some improvements in terms of how projects or day-to-day work is organized. One of the challenges when it comes to rolling out to an enterprise is the way the projects are organized. It has a kind of setup where you have different projects and tasks, but it is not as organized as Smartsheet when it comes to organizing projects or different teams. It can get really cluttered really fast. JIRA has another suite to submit the support tickets. It would be good if Asana could branch out to incorporate some kind of workflow. It is great for collaboration and recording work, but there isn't any workflow. It would be useful if they can map out a workflow of who approves what. This is kind of a big ask, and it is not geared towards that."

"It would be great if Asana could create a library for each project within the interface."

"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."

"The solution could have a bigger pop-up when someone assigns a task or have a notification similar to Facebook, where you see a number indicating the notifications you receive."

"More features can be added."

"Auto-shift is an essential feature for planning, but it's currently not there. It should have this feature so that when you move a task that depends on another task, the dates should be auto-shifted. For example, you have two tasks dependent on each other. When the parent task is moved or delayed, the child task should also be delayed, and the date should be shifted. When we have a very long timeline, it's very complex to go task by task and shift the dates on the task. Auto-shift is a fantastic and basic feature of project management, and having such a feature in Asana would make our lives much easier. If Asana added this feature, it would complete the suit and close the project management cycle because currently, there is a gap."

"The calendar view in Asana has shortcomings and can be improved."

"It would be nice if the tool can reduce its operational cost. It would make it more competitive."

"It takes time to use it. It is not entirely intuitive, so there are areas for improvement."

"It is not entirely intuitive, so there are areas for improvement."

"The price of the solution is reasonable."

"We paid a monthly licensing fee for the product."

"This solution is reasonably priced."

"It has a free version."

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

"We're on the business tier, which is $25 a month if you're on an annual contract. It's $31 if you're on a month-to-month contract. In my experience, there are no hidden costs with Asana. I know Smartsheet has these add-ons that you can buy, which is an additional cost, but Asana doesn't have any add-ons that I know of. When you're trying to scale the product and want to add users, you have to do it in buckets of five. This is also something to consider."

"There is a free version of Asana, but we use the paid version to receive all the features we want. The overall price is reasonable."

"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."

"The tool is cheap and I would rate it a ten out of ten."