MartinMonteiroSr Domain Specialist at a healthcare company
Bryson HeathData Analyst at a tech services company
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"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."
"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."
"Planview has helped connect funding and strategic outcomes with work execution. That is the key use that we have for it. We use it to validate the work that we're doing and the funding that we need. The difference between the previous version and current version for us would be the ICPM and the way it gives us different scenarios. We can go in and build that out."
"I like that everyone is able to see the same data. All of our users who aren't just time reporters have read access to all the data that is out there. So, it is one source of truth where everybody can go in and see the exact same data that everybody else sees. It is transparent."
"The portfolio management gives you a view of all the projects as well as all the information about the total amount of effort, time, and cost being spent on the projects. It gives the organization how much money and effort should be spent towards projects so they can budget and do better capacity planning in the next fiscal year. It gives them visibility into their resources and if they have capacity."
"The biggest impact for using Planview currently would be to understand the true costs of projects. We are trying to get to a point where not only do we take into account technical costs, but what the business cost is. Trying to integrate our business right now into Planview is helping us identify the true cost of the investments that we make so we can try and understand their value."
"We have a fairly good picture of time tracking."
"The look and feel of it is pretty clean."
"I love the way it monitors all of the current and past projects, and it sends notifications to keep everything on the track."
"By using this software, I have adaptability in my work, and it can improve the production of our company."
"Asana has helped me (as an individual contributor) organize my daily work and given me a way to plan for longer term objectives."
"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."
"It's an easy way to communicate."
"Monitoring the progress of projects and tasks is very effective."
"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 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."
"We have required more time from our resource managers to spend time in the tool. The adoption has been slower than we would have hoped. So, I would think from a rollout perspective, if Planview could help us with material which gets non-Planview users or previously light Planview users to become more heavy users of the system, then this would help us with the rollout."
"There can be improvement on the sense of urgency because a lot of times we've exhausted everything that we can, and now, we're reaching out. So, it isn't a, "Well, have you tried to reboot this?" We've already done everything. Once we put in a ticket, there should be more of a sense of urgency on it."
"I would like to see more documentation pieces. Right now, they do have the content repository. I would like to see more out-of-the-box features with document repository capabilities."
"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."
"There's still a lot of reluctance within the organization. We're not using all of the capabilities that we have today. We're still doing our strategic and capital investment planning on spreadsheets rather than using the capabilities that exist within Enterprise One. I definitely need to leverage the experts here at Planview to help drive a culture change. There's just a lot of reluctance on behalf of people within the company to put data into the tool."
"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."
"This solution has a learning curve, where it is initially difficult to use."
"The inbox feature can be a little overwhelming if you are working with Asana just from its project boards and only checking it periodically."
"A user should be able to identify an assignee for specific tasks or task types while applying the template, or at a minimum, allow for a default assignee. As it is, the template gets created with the just task dates driven by the project start and end dates inputted by the user. In my current situation, I'm assigning myself to many tasks, so I have to do that manually every time. Even if I eventually start adding other people to assign tasks, there won't be more than a handful to do. However, those few people will have multiple tasks. It would be nice to be able to select those individuals during the setup rather than having to do so manually once the project has been created."
"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."
"There just needs to be a bit more direction on how to use it at the outset."
"The interface can also be customized to fit and accept many tools for better performance and customer service improvement."
"We are on the Flex licenses."
"We have unlimited licenses for all of our functionalities. Since we went global, we went with that model."
"The cost of other pieces and integrating them in needs improvement."
"We have portfolio managers, resource managers, project managers, and time reporting licenses. These are the licenses that we have."
"I don't think we have necessarily purchased everything that I would have liked to have seen."
"We have several hundred licenses. It costs us several hundred thousand dollars a year."
"We overbought our licenses. We looked at our needs three to four years down the road and tried based our contract on that. However, we were over aggressive. We use about a third of the licenses that we have. We're looking to adjust the makeup so we can start utilizing the amount of money that we are spending. Right now, we're overspending, and my organization is not seeing the value in Planview because we are paying so much for licenses that we're not using."
"Our licensing costs are probably $150,000 to $180,000 a year with 270 licenses total."
"The price of this solution makes it quite accessible, and the plans fit my budget."
"Asana has two different types of structures: company vs workspace. Company is really best if all the users you plan to assign work to are all internal (have the same corporate domain in their user ID email address). Once one person signs up (even for a free account) with a corporate email address, Asana will automatically relate that person to that company, if it already exists. If you plan to use it for external collaboration as well as internal, then creating a workspace is a better approach."
"It has a free version."
Asana is web-based software-as-a-service that helps teams coordinate and manage their work. It helps companies move faster by making sure everyone knows the team’s plan and process and who is doing what by when.
Each user can create projects using a list, board, calendar, or timeline view. Within each project, users can add tasks, subtasks, sections, comments, attachments, start and due dates, and custom fields. Project and task followers get notifications on changes or comments on the project and/or task in their Inbox. Individual users can see all of the tasks they're responsible for across all of their projects in a view called My Tasks.
Asana is available in English, French, Spanish, German, and Portuguese.
AtTask is a cloud-based Enterprise Work Management solution that helps marketing, IT, and other enterprise teams conquer the chaos of excessive email, redundant status meetings, and disconnected tools. Unlike other tools, AtTask Enterprise Work Cloud is a centralized, easy-to-adopt solution for managing and collaborating on all types of work through the entire work lifecycle, which improves team productivity and executive visibility. AtTask is trusted by thousands of global enterprises, like Adobe, Cisco, HBO, House of Blues, REI, Trek, Schneider Electric, and ATB Financial. To learn more, visit www.AtTask.com or follow us on Twitter @AtTask.
Asana is ranked 5th in Project Management Software with 5 reviews while Workfront is ranked 8th in Project Management Software with 1 review. Asana is rated 9.0, while Workfront is rated 10.0. The top reviewer of Asana writes "A user can create custom templates with any project, but the templates should allow for a default assignee". On the other hand, the top reviewer of Workfront writes "Great technical support, quick to set up, and offers excellent collaboration capabilities". Asana is most compared with monday.com, Trello, ServiceNow IT Business Management, Jira and Zoho Sprints, whereas Workfront is most compared with Jira, ServiceNow IT Business Management, monday.com, Broadcom Clarity PPM and Wrike.
We monitor all Project Management Software 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.