Compared to Broadcom Clarity, there was some flexibility with blueprints, etc. You can create a blueprint for different business groups or different customers. Planview AdaptiveWork doesn't have something like that.

If they can build up something like a view price. It's still a traditional way where you have to create different instances for different customers. The PPM solution uses queries if I'm rolling out for different divisions. In that case, I have to create different instances for each region because each division may have a different look and feel. But if I have a blueprint, then it's very convenient. I can create multiple interfaces for different processes. Broadcom Clarity has some access control on those viewpoints.

One specific area for improvement could be implementing a development environment to test workflows with live production data.

I felt like the slide publisher isn't that user-friendly. I think it wasn't that easy to use or to figure out because of formatting constraints, or maybe we need to get better at understanding some of its limitations. Slide publisher is something that we're definitely interested in, and it was great in theory, but when we put it to use, it didn't serve our needs. So we aren't using it currently.

For the most part, I think the workflow management capabilities are sufficient based on what I've seen in my role as the team admin on some of the earlier teams that I've been on. However, there was difficulty updating the schedules on the fly without relining all the data. At Dell, we're always trying to match the project schedules to reality. So many of the dates start shifting, and people are getting frustrated with managing the schedule because the dates keep changing, and we have to keep fixing them. 

And I think that there are maybe too many dependencies added to the schedules that they've created. Some of the dependencies are needed because they have to hit a specific delivery date. So, it's kind of like, "Okay, if you don't use that, then technically you can push past that delivery date." So, they constantly have to shorten certain parts of the schedule to keep the dates from shifting. I think that was the biggest complaint in terms of the workflow piece.

As far as automating life cycle service requests goes, we've done some configuration just in project intake. That was about as much automation as we've done. We've also used Clarizen to generate a schedule using certain templates on the due date and then backtrack. So yeah, we've done some automation on that. It wasn't easy to automate, though, because the project manager would still have to go in and do some updates and fixes every time, so it's never fully automated. I think it was always just semi-automated, and they still had to put in a decent amount of work to get the schedule correct.

Clarizen could be a little bit more visually appealing. A gap I've felt with Clarizen is that improvisation is necessary to get that aesthetic feel. I've also noticed that if we customize a report too much, going back and changing things adds a lot of overhead time.

We find Clarizen's reporting and analysis helpful, but there's always room for improvement, especially with the customization part of it. If I start customizing too many things, Clarizen tends to get slow in our environment and especially if I'm tunneled in an environment, like if I'm connected to my VPN.

Clarizen could also improve the way they handle licensing. For example, our company purchased a certain number of licenses; I don't remember if it's 50 or 100. But, if a user is someone wanting to get just a high-level overview of a project, they are considered a separate license, not just a view license. Clarizen should come up with a licensing structure that would allow some users to get an overall picture of the project without consuming a license. I would say that only active project managers or users actively looking at the Work Breakdown Structure elements should be counted as licenses. 

Also, workflow configuration is good with Clarizen, but it is lagging in maturity. The workflow features have not been effective for what we are trying to do. We use standalone tools for projects that we need the workflow functions for. We stopped using Clarizen for this because it did not serve a purpose for us. We use Asana and other such tools. 

Also, when you log in to Clarizen, it just shows you a pie chart. It would be great if we could choose these visualizations, like we can with Power BI. Instead of just a pie chart, I would like to see a donut or another visualization.

It could be more user-friendly. I think it is too overwhelming, initially, in terms of possibilities and so on. They should help more in providing a way of working so that you can gradually move up. For further integration with a SQL server, my feeling is that they lack skillsets for that here.