Adobe Workfront, acquired by Adobe in late 2020, is a web-based project-management tool. It is designed for both IT and marketing teams, but can be implemented for any kind of project. Workfront offers all the features standard to project management platforms, as well as resource allocation, automation, and agile workflow.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
Workfront has better integration into the tools we use, like Adobe Creative Suite, Outlook, Salesforce, and our CMS and DAM. We needed a solution that could work well with our MarCOMM Stack and didn't need a whole lot of support. Although we're a small shop (license-wise) …
For the marketing department, Workfront goes WAY beyond my expectations and needs - unlike the out of the box ServiceNow technology that I was forced into at my last company.
I write music and sound design for multiple projects at the same time, all within the same company, sometimes as much as 8-10. It can be hard to keep track of and stay on top of notes and changes, but Adobe Workfront is great at keeping everything organized, and informing you of deadline changes as they occur.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
All that I've said already is why. I suppose the clearest way to say it is that at this point? I cannot imagine running the 300+ active projects in eMarketing without AtTask; it simply wouldn't be possible and even more; I wouldn't imagine why we'd try to find an alternative tool when we have one meeting our needs.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
I gave a rating of 10 on overall usability because Workfront is cloud based and very easy to use. Workfront also provides collaboration on projects which is critical to a projects success. The tool gives everyone high level visibility in their projects down to the smallest detail. Wonderful project management system, allows you to cut down on emails, meetings and no more spreadsheets for tracking your projects.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
Maintenance is required, but usually after work hours, Some days the proofing tool function is not operational, but this is a new function of the tool that WF is working out. the kinks on. Chrome is the best browser to use the system in and we find Firefox and Explorer lose some view functionality - Gantt Chart, Resource Grid
Workfront's performance has been very good. Everything always feels very fast and snappy in my experience. We have integrated it with custom scripts to create folder structure for media managing our projects. It works very well.
It would be nice if the support forms were more dynamic so you could add more information to the support ticket when you enter it to reduce back and forth with the support team member. Also communication on escalated tickets isn't always great. It's gotten better over the years but still needs improvement. Other than that, initial response on support tickets is really quick and the people I've dealt with have always been very professional.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
The training is very easy to use and you can simply choose the topics included in the course(s) that are most important to your training needs. After each training course, you are tested on what you have learned. If you need a refresher course, they provide Course Catalogs as well as instructor-led courses & workshops.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Most people learn as you go, a lot of this stuff requires trial and error throughout so my suggestion is to provide as much information in the upfront and keep it as simple as possible. You can add other tools and features as you go but everyone should have the basics down so no bad habits can start to develop. Be persistent with everyone, and don't be afraid to correct and talk through steps again so everyone is on the same page
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
Jira is mostly used as a bug locking tool or to track any new development for any specific region/EPIC. But Workfront has a lot of other features which are beneficial in project management. I still consider Jira and Workfront my top two options for project management and believe both have some of the other useful features which are required to manage any team.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
As I stated earlier, I didn't have to pay for Workfront myself- I'm a user under a large organization. I know it's not cheap to implement, I don't know how the price scales for a small-business, but I do like the product enough that I'm going to look into it in the future for my own company.
Our organization has thousands of users that use Workfront and it seems to hold up very well. I have not encountered any issues using it and I think it makes it very easy for multiple people to be involved in a project and keep things organized and clear for everyone involved.
Workfront allowed our company to have multiple offices and work remote and still have projects continually move through the agency
The platform allowed streamlined project management needs so PMs could look at a higher level of timing for resourcing needs for a given team
Workfront's ease of integration with other tech allowed for a lot of flexibility to meet the needs of individual wants/needs so that each person could do their best work
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
