Try our new research platform with insights from 80,000+ expert users
Planview Portfolios Logo

Planview Portfolios pros and cons

Vendor: Planview
4.0 out of 5
1,888 followers
Post review

Pros & Cons summary

Buyer's Guide

Get pricing advice, tips, use cases and valuable features from real users of this product.
Get the report

Prominent pros & cons

PROS

Planview Portfolios provides comprehensive reporting features, valuable for executives and project management, offering a variety of out-of-the-box reports and analytics.
Resource management and capacity planning features in Planview Portfolios allow organizations to effectively monitor and manage workforce capabilities and project assignments.
Financial management tools integrated within Planview Portfolios assist in tracking expenditures, forecasting costs, and aligning project financials with business objectives.
Planview Portfolios enhances organizational transparency and accountability by consolidating all project information into one platform, facilitating improved governance.
The flexibility of Planview Portfolios supports various work methodologies, including Agile and non-Agile teams, aiding diverse organizational needs and project executions.

CONS

Planview Portfolios' inability to seamlessly integrate with market-leading Agile tools poses a significant challenge to users wanting to adopt agile methods.
Users have expressed dissatisfaction with Planview Portfolios' customer support, citing delays, lack of responsiveness, and inadequate assistance with legacy systems.
The complexity of using Planview Portfolios, combined with a steep learning curve due to the lack of templates, makes it difficult for new users to adapt and utilize its full capabilities.
Reporting capabilities in Planview Portfolios need substantial improvements, as users find the out-of-the-box reports insufficient and often rely on external tools like Power BI for effective data visualization.
Planview Portfolios faces challenges in performance and stability, with users reporting issues such as slow data loading, performance problems, and the need for frequent upgrades to resolve functionality limitations.
 

Planview Portfolios Pros review quotes

BO
Sep 24, 2021
Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool.
RP
Sep 17, 2020
Another good thing is that we can create custom reports, which is great. If I created a custom report, a tile that tells me how many people have logged in today. We currently have a little under 2000 users, and that's only users, we actually have integrations, that we created a custom form that sends hours directly to Planview. They're not using Planview directly, but they're sending their hours to Planview through an API.
KK
Sep 17, 2020
When it comes to managing project plans, Enterprise One is awesome at enabling us to see what stage work is at. I've always thought it was awesome because it's good whether we're doing a traditional WBS or we're linking in epics into projects that are supporting the programs and the strategies, I've always thought it was an excellent tool.
Learn what your peers think about Planview Portfolios. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
815,209 professionals have used our research since 2012.
MK
Sep 24, 2021
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.
JC
Oct 15, 2019
The solution’s integrated product portfolio has transformed our organization’s delivery because people are a lot more accountable. When you have no accountability, then people don't always deliver the way that you want them to. Once you get accountability, they know that somebody is watching and the way that they manage their work changes quite a bit.
NS
Oct 13, 2021
The solution view into resource capacity and availability helps us to manage work.
GS
Sep 29, 2021
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.
KB
Sep 21, 2020
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."
AH
Oct 15, 2019
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.
RB
Mar 2, 2022
We provided whatever feedback we had to the Planview team, and they went in and built those additional features that we requested. For example, they created a great way for our users to search for a specific resource, project, program, or role. We were not using some of the features, and we wanted them to not be visible, and they helped us with that. They also brought a feature to provide visibility into when a resource was never assigned to any task. There was no visibility to this before. This feature was really very good for visibility into the resource portfolio.
 

Planview Portfolios Cons review quotes

BO
Sep 24, 2021
The solution is stable. However, it's so robust, there's so much data, that it has the tendency to lag.
RP
Sep 17, 2020
The content management definitely needs to improve. We don't really use content management for projects inside Enterprise One. We have actually switched to a SharePoint site. We have a feed from Enterprise One every night of all the projects that are created.
KK
Sep 17, 2020
I think some of the administrative aspects of it could be a little easier, especially when it comes to designing reports. The reporting coming out of it could be a little bit better.
Learn what your peers think about Planview Portfolios. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
815,209 professionals have used our research since 2012.
MK
Sep 24, 2021
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.
JC
Oct 15, 2019
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?
NS
Oct 13, 2021
The out-of-the-box reports, as far as I can tell, are weak. We've had to build a lot of reports using Power BI, which we connected to it.
GS
Sep 29, 2021
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.
KB
Sep 21, 2020
We've been using it for a while, so it's about maturity. It's about being able to build out things in Agile groups and teams and some of that. Then really trying to drive into the direction of Lean Portfolio Management and more Agile program management, I think is where we're heading.
AH
Oct 15, 2019
I would suggest for the request module that they open up the fields and columns so it's like we are doing our work in the work module. You can't do that with today. We also have to make sure that the fields can go both ways with the request and work modules. Including fields in the column sets would be helpful, because today they only use attributes.
RB
Mar 2, 2022
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.