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 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."
"Stable Kanban style tool for collaboration and task management. It runs smoothly and has a straightforward setup."
"My task box displays all of our tasks, organized by day, helping us to focus on what needs to be done each day."
"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’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."
"Asana is a very simple interface for project managers to figure out, providing all the functions they need."
"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."
"I like that the data that we store is available for everybody. We're not trying to hide anything. Being an administrator, I know a lot about the tool. It is very easy to show somebody how to use the tool and get used to it. Hopefully that user doesn't come back and ask the same question twice is really what it is about. It's a very intuitive product as well. For what we use the tool for today, it's easy to learn and pick up."
"The most valuable feature for me is the ease and customizability of reporting."
"The portfolio and technology management are well built."
"The most valuable feature of this solution is the completeness of the standard, underlying metamodel."
"We can view a project both at the top level and dig into the particularities. It's given us greater visibility into the work itself."
"In my opinion, the financial planning feature is the most valuable feature of Planview Enterprise One."
"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."
"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."
"You need to have an action plan, otherwise, it won't be as effective."
"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."
"In Asana, there's no way to add a custom date field."
"There just needs to be a bit more direction on how to use it at the outset."
"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."
"The messaging feature could be better."
"It's difficult to have short-term collaborations with external users because the operations team owns the final licenses, and I work for marketing."
"The solution can be difficult for new users to use because of the interface."
"The biggest room for improvement are the scripted dialogues. The scripted dialogues are a logic that you set up to force a certain workflow or process to happen. It's very old in respect that there are no clauses that you can apply to that logic. That definitely can use a lot of room for improvement."
"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."
"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 don't use the Progression feature. We will use it at some point in time. Until then, we want to have a way to set time to help decide what's in the past, present, and future. It is one of the things we've been discussing with Planview."
"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."
"The resource area needs improvement. The improvements that have been made recently in the later versions have been good improvements, but I think there are some more improvements needed there."
"Our version is definitely set up a bit more waterfall world. It would be better if some of the agile features were more in the standard product."
"The solution needs to be better at accepting new ideas for upcoming releases."
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, SAP Portfolio and Project Management and Planview ProjectPlace. 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.