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."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."
"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 initial setup was straightforward."
"It is pretty comprehensive when it comes to the different views that it gives you. It gives you a Gantt chart view, calendar view, board view, and list view. It is kind of helpful to have different types of views and see how it views your different tasks. I appreciate being able to do that. The biggest thing is that it is extremely user friendly. Asana is pretty intuitive. Someone who is not tech-savvy can kind of catch on quickly. It is better than other tools like Smartsheet. Some of the other tools like Microsoft Project and Excel are great tools, but you have to invest a lot of time to learn them, which is not the case with Asana."
"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."
"The general UI shows progress and data analytics for all projects in progress."
"The ability to build subtasks and break things down off of our major tasks has been very valuable. It is very stable and extremely scalable. The initial setup is very simple."
"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."
"We're still in an early stage. Things will change as we use it more. I did program reports that are important and that will provide us with value."
"With the lifecycles, it helps us step through our processes easier. We'll take a process and create it in Visio, then we'll go and implemented in Planview. Anytime that we have to do a new process, this is what we use. We just step it through the lifecycles and the configure screens are very easy to use. The fields that you need are easy to use."
"The most valuable feature of this solution is reporting."
"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."
"Its ability to create summary reports across multiple projects is one of the best features. They have very good data warehousing. You can put that out. You can tell that data warehousing from Planview Enterprise One is excellent."
"It has helped improve governance, mostly. People want to know where their money's going. Projects sponsors need to know what we're spending money on and what our burn rate is. Planview can give that to you straightaway."
"We use expenditures quite a bit. We put in forecast expenditures and then we actualize them below the line in the little box in the bottom tray. Being able to track the project with relevant milestones is also valuable. Milestones are valuable because it helps us to keep the project on track. The expenditures are valuable because we need to be able to understand expenses that are beyond the regular resources in the projects."
"We've brought our portfolio altogether. We have had multiple ways of reporting out what our portfolio is, whether it's in Excel, Word, or in different places. We brought all of our projects together in one place. That has worked out well for us. We've been able to manage the work on Gantt charts and our resources better. The big thing for us on research and development is around managing people's time, on which projects they are working on, and how much effort does it take to launch our projects."
"The calendar view in Asana has shortcomings and can be improved."
"It's difficult to have short-term collaborations with external users because the operations team owns the final licenses, and I work for marketing."
"For large teams, scalability should be improved."
"It's hard to integrate Asana into other parts of the company workflow, so integration is an area for improvement."
"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."
"You need to have an action plan, otherwise, it won't be as effective."
"The messaging feature could be better."
"We don't get enough notifications."
"Some of the out-of-the-box reporting is not immediately useful and although it can be configured or customized, there are still improvements that can be made."
"The administrative tabs are very confusing, especially in terms of configuring screens and users. It's not very intuitive versus many other applications that I have worked in the past. I have to go to separate sections than I think I have to in order to get to the place that I need to adjust something."
"The scheduling's kind of clunky in terms of its ability for us to see what stage work is at. They could have done better with that. It can be difficult to use."
"Configuring the UI in the content management system is too elaborate and too time-consuming."
"Its ability to create summary reports across multiple projects is very limited. In terms of the out-of-the-box reporting for summary reports, the reporting that we typically leverage is around forecasting for resources, timesheets, and actuals, and just looking at what is the capacity. There is no real summary of what work is being done and how work is being accomplished. So, what we typically do is that we get a copy of the data files from Enterprise One daily, and then we have a team that manages the data mod outside of Enterprise One. They use data from Enterprise One as well as other additional sources to provide the reporting that we share with the management. So, we leverage a lot of Enterprise One data for reporting, but we don't use the reporting capabilities within Enterprise One. So, reporting can be improved, and they could help us make more customized reporting. I know it is very configurable out of the box, but we have to leverage an outside data mod that pulls in a lot of data from Enterprise One. So, the reporting function, and being able to customize reports, is the area that could be very beneficial."
"I would like to be able to integrate with Oracle to supplement what we're currently doing with reporting."
"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."
"We are not very happy with the customer service. This is one of our main pain points. It doesn't cover the entirety of customer service, as there are reps who are really great and we've had good experiences. Many times, we've had people give us attitude, there was a delay in the response, or just a lack of interest. This got to the point where if there was a problem, we would rather try to solve it ourselves then call customer support."
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 "Extremely stable, user-friendly, and easy to navigate". 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.
