We performed a comparison between Asana and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Project Portfolio Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The tool has a lot of integrations."
"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."
"It is stable and easy to set up."
"The solution's user interface is very good."
"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."
"The most valuable feature of Asana is the tracking of comments and documents in one place."
"It’s a great way to communicate plans and progress across the business and is flexible about how much detail I include and how I present it."
"It has helped our departments maintain visibility."
"Enterprise One provides a variety of types of resource assignments for assigning work to people. It's very easy and straightforward to configure these assignments. Planview allows us to see the entire workforce. We can see where our skill sets of people are, what they're working on, and allows us to make informed business decisions based on priority."
"The overall interface is very easy to use. It puts together strategy and execution across all your investments."
"We use time reporting. We convert time reporting into financial costs and do contractor and capacity planning for our resources. We track our work. So, that's the module we use extensively. As a matter of fact, we have upwards of 300 open projects at this given moment. It is pretty close to 300 open activities that are working."
"The solution view into resource capacity and availability helps us to manage work."
"We can easily see which functions are overcapacity. Before, we did not have visibility into that."
"The resource management and assignment features are valuable. The timesheet management is also valuable because that is a requirement for us. So, the ability to see timesheet forecasting and timesheet actual submission from resources has been very useful and valuable to us."
"Its view into resource capacity and availability helps us to manage work. In reporting, we use this facility to help with resource capacity and availability. It also helps to see how much we are using. We derive that information from the work and resource management screen. That is very helpful."
"A lot of of the value is around the project metrics so far but as I get more plugged into the strategic management, it's strategic planning and programs and then tying that into outcomes. I work with executive leadership and that's really what they're looking for, to say, "Okay, what outcomes do we want to achieve and how are we going to get there, plan that out, sequence that out, and then get the work to do that? And then track the work back to where we're headed with our outcomes.""
"The product must reduce the information on the interface."
"This solution has a learning curve, where it is initially difficult to use."
"The calendar view in Asana has shortcomings and can be improved."
"I rate the support from Asana a four out of five."
"It's difficult to have short-term collaborations with external users because the operations team owns the final licenses, and I work for marketing."
"It's hard to integrate Asana into other parts of the company workflow, so integration is an area for improvement."
"The messaging feature could be better."
"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."
"I would like to be able to integrate with Oracle to supplement what we're currently doing with reporting."
"I would like to be able to copy and paste from Excel into work and assignments along with roles and hours, as opposed to having to type it out one by one."
"Recently, we have gotten on a newer version. We're currently on version 15. Some of the things that we've been running into roadblocks on, it looks like the solutions will be coming out in versions 17 or 18. So, we have to upgrade before somethings can get completed."
"I would like a bit more flexibility, as far as the configuration, and have additional capabilities to configure, making it more flexible for our use."
"Configuring the UI in the content management system is too elaborate and too time-consuming."
"I think that the user interface needs some getting used to. It's not immediately intuitive. That's potentially room for improvement. I think also that an organization needs to have good support from some senior management to get something like Planview established."
"It is not an end-user-friendly product, and that's really the biggest thing. The hardest or the biggest hurdle I've ever had to face was adoption. I did the installation of the HP product in 2011. The company used it from 2011 to 2015, and the adoption was very high. When I was given the Planview product, adoption was very low. It wasn't as extensively used. We actually had people who wanted to go back to HP PPM because the interface of Planview was so broken, and it still is to some degree. So, it is not user-friendly. It doesn't flow the way a project manager thinks. What we did with HP PPM was a lot more manual programming. It wasn't as nice in terms of the interface, and it wasn't as pretty, but you could design it and build it so that everything flows with the way you worked, but Planview doesn't quite do that. There are a lot of screens. You have to jump back and forth. There are so many different places you have to go to just to do some basic tasks. That's the biggest thing that has really hindered adoption."
"Our challenge will be this tool is complex. It is not necessarily easy to start and learn from the beginning. How do you get people who are not professionals to adopt it, use it, and not be mean about it?"
Asana is ranked 3rd in Project Management Software with 43 reviews while Planview Portfolios is ranked 8th in Project Portfolio Management with 63 reviews. Asana is rated 8.4, while Planview Portfolios is rated 8.0. The top reviewer of Asana writes "Stands out with portfolios, easy setup, and real-time information, but needs big improvement when it comes to workflows, automation, and dashboards". On the other hand, the top reviewer of Planview Portfolios writes "Helps prioritize projects, share the big picture with management, and has a great planning capacity". Asana is most compared with Microsoft Azure DevOps, Microsoft Project, Wrike, monday.com and Jira, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, Planview ProjectPlace and SAP Portfolio and Project Management. See our Asana vs. Planview Portfolios report.
See our list of best Project Portfolio Management vendors and best Project Management Software vendors.
We monitor all Project Portfolio Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
