We are implementing Workfront now
August 11, 2017
We are implementing Workfront now
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Workfront
- Manage digital work processes
Our project managers currently use multiple documents and spreadsheets to track their work. We are implementing Workfront to alleviate disparate processes. It will provide one central location for information on every client program.
Pros
- Workfront's support system is great. Their support reps respond quickly and are patient even when you are not. If the support rep doesn't always know the answer they are great about researching and following up with you.
- Workfront is incredibly customizable so you can configure it in a way that works for your company. We find that when building process into Workfront there are several ways to go about it.
- We love the custom forms and the ability to put metadata on every object in Workfront.
Cons
- The reporting/views and fields available are not always intuitive. For example, when creating a document, task or issue report/view, you cannot access the program or portfolio information/metadata unless you calculate it through to the project level. This equates to a lot of extra calculated fields and work, that in my mind, should not be necessary.
- The integration with Proof HQ needs some work. We were Proof HQ users first and have begun the Workfront implementation. Eventually, they will be integrated where users access Proof HQ through Workfront. The approvals process in Proof HQ is much more robust that Workfront's; however, the reporting that Workfront provides on the Proof HQ processes and approvals is severely lacking which makes visibility on Proof HQ approvals difficult.
- There are 3 levels of objects in Workfront: Portfolios, Programs and Projects. There is no way to tie Projects together except to create an issue on the first Project, then convert the issue to another Project. Complicated text mode fields must then be created and placed on a view/report to see if/how these projects are tied together. There should be a better way to tie projects. Our solution was to change the use of the Program object (to have a Program = a Client IO, rather than the Program = Brand). Further, the Portfolio and Program access is tied together. You cannot provide different access to Programs vs. Portfolios which makes our solution a little cumbersome.
- We are still in process of implementing Workfront. It's a slow roll out, one to two departments at a time. So our impact thus far is minimal but I can say having every program/project in a single system has provided a lesser need for email chains, meetings and "he said/she said" conversations.
I have very little experience using other systems like Workfront. My background is more in billing systems and order processes. All I can say is it beats Google Docs and endless email chains.
Our managers now have the ability to see real time progress on client campaigns. Since we can tie these campaigns to expected revenue that is extremely beneficial as well. At this point, we have only rolled out to our Account Executive team, but will bring in our Creative Design and Legal/Regulatory teams next month. Everyone is very excited about the ability to have a single source of truth and collaboration.
We have had several consultants from Workfront during our implementation. We have found that after a while, our knowledge starts to outweigh that of our consultant. Toward the end of our relationship with our last consultant, it seemed that his standard answer was "open a ticket". We switched consultants (to one with a different skill set - Proof HQ rather than Workfront implementation). So far he has helped, but our relationship is young, only about two weeks now.
Comments
Please log in to join the conversation