Adobe Workfront Reviews

The way that my company uses Adobe Workfront is primarily as a marketing solution for project management. We use it for gathering all the approvals needed, again using the marketing use case. We do utilize Fusion, so we have quite a bit of automation built in. We're up to 6,500 users, of which 6,000 are all in the marketing use case, but it includes legal approvals, risk approvals, and then director approvals.

The features of Adobe Workfront that I have found the most valuable so far are the data gathering capabilities through the custom forms. I think it's one of the most important, especially when you're in an industry where everything is so tightly monitored and audited. To be able to collect information and then build a report on that information easily and readily is probably the most important.

The second would be the approval process, and then the big bonus of it is Fusion, so the automation behind Fusion is what sets it apart.

Adobe Workfront helped in managing projects efficiently for me through the ability to see everything in one view with dashboards. I've set up dashboards for people, and even though I don't necessarily use them, a dashboard is essentially multiple reports in one view.

I think that Adobe Workfront could be improved in several areas, including reporting, which I've already mentioned. There are very specific things within the custom forms that I think could be improved, such as having different labels within forms instead of system-wide. The ability to hide options in a drop-down at the custom form level instead of system-wide would be another improvement.

There are times we have to create brand new fields because we need slightly different wording within the label. If we had the capability, we could easily trim down from over 1,000 custom fields to about 400 custom fields if we had the ability to have individual labels by form. So reporting is a big one, and I think there are some not huge changes needed, but improvements to custom forms and custom fields would be beneficial.

My experience with reporting in Adobe Workfront so far is that the reporting could be better. The ability to report is great, but I think it is too difficult. Regarding dashboards, they are crucial to be able to pull information from different levels, but that's also a negative because it is very difficult to do that on a report. If I have issue-level data and project-level data that I need to see, with some custom coding, you can do some of it in a report, but in general, if you have a lot of that blended data between levels, you need to use a dashboard, which requires two different reports due to the difficulty in pulling data at the different levels into one thing.

I've been working with Adobe Workfront for about three years now.

Overall, I would rate the stability and reliability of Adobe Workfront a ten. We've had minimal issues, almost none regarding stability.

I think Adobe Workfront is very scalable. We have gone from two or three marketing teams up to over 40 marketing teams and 6,500 users in a few years. It is not scalable in a way that you can self-onboard, so it does require support. But because of its flexibility, if you have the right support, you can onboard essentially any group and their specific use cases.

I communicate with the technical support of Adobe Workfront via ticket. My team will submit maybe 10 tickets a week, so not a lot. Personally, a couple of those tickets will be mine.

I think the effectiveness of Adobe Workfront's technical support is mostly good. There are situations where you recognize some of the tech support individuals and you know that they're going to have to hand the ticket off or aren't going to solve it, requiring escalation to a different level. However, in most cases, when you see who's taking care of the ticket, you know it will be handled.

I decided to switch from Jira to Adobe Workfront because Jira is just not designed for project management in a widespread way. It's really meant for tech teams to manage releases and their delivery processes, as opposed to what we use Adobe Workfront for, which is marketing and managing marketing campaigns or marketing projects.

The benefits and positive impact that I have seen from Adobe Workfront since the deployment is that during 2024, we onboarded about 2,500 users. We tracked all of the savings through Adobe Workfront, and at the end of the year, for those 2,500 users, we saved over 1,200 hours, or 1,200 man hours.

My impression of Agile project management features in Adobe Workfront is that it's adequate. I feel that's how it's marketed and it works fine for that. But again, what sets it apart are the custom forms, the reporting, and the automation. In all honesty, the project management feature alone could basically be done in just Excel, so I don't think it sets it apart.

I integrate Adobe Workfront with other technologies and third-party tools. We do some of the plugins and then we also do some with Fusion, which is beyond plugins.

I consider Adobe Workfront to be affordable. I think it's expensive, but what makes it affordable is that the license cost can be transferred. If someone is using Adobe Workfront and leaves the team or the company, you don't have to buy a new license for their replacement; you can transfer the license, so I think that makes it affordable.

I rate Adobe Workfront a nine out of ten.

I am supporting this company to set up Adobe Workfront and automation using Fusion. The use cases are centered around our fintech company, which has numerous ongoing processes where people are working by remembering all tasks or steps to be followed. We are creating all the workflows and checking if there can be automation such as approval processes, clear view with dashboards, reports, managing time cards, and the workload balancer so we can better track the utilization of each resource. These are the use cases we are working upon right now.

One of the best things about Adobe Workfront is that we can immediately track each project. We can keep track of all tasks with the help of milestones that we can add to a project. We can monitor everything effectively.

The utilization and workload balancer allows us to clearly see if a person is over-utilized or if they are not getting utilized to at least 80 or 90%. This enables better tracking and work assignment with improved clarity.

We use custom dashboards in Adobe Workfront to see all statuses. The integration capabilities with other software are quite good, with straightforward connectivity. We have HTTP connectors if we need to connect with external systems via APIs. If we have any API endpoint for any external tool, we can connect it with Adobe Workfront using Fusion.

Reporting is a major part of Adobe Workfront, making it not just a workflow management tool but also a tool where we can get data and present it to executives through comprehensive reporting.

We haven't explored the agile project management features in Adobe Workfront yet. At this point, we are focusing on onboarding as many processes and automating as much as possible using Fusion.

The downtime, while not too long or frequent, is an area for improvement. As many companies are using Adobe Workfront now, Adobe should monitor all downtime and try to fix it as soon as possible, or implement measures to prevent downtime altogether.

I have been working with Adobe Workfront for two years now.

Adobe Workfront is stable.

Adobe Workfront is scalable.

I have escalated a few questions through the Admin Console or Adobe Experience League website's support tab. When a card is raised, someone always reaches out. In my two years of experience, there hasn't been a need to escalate anything because they respond within three to four hours.

Positive

We previously used Jira, which had limitations such as restrictions on assigning multiple users and complicated workflows that could only be created by system administrators. Adobe Workfront is more user-friendly with an intuitive layout. It is easy to learn and configure, with numerous online resources available directly from Adobe Experience League.

I joined the company after the initial setup was completed. For the initial setup, Adobe offered a third-party vendor who helped the company establish Adobe Workfront and automated several initial processes.

We have connected Adobe Workfront with Jira, our internal system, and several other systems via Fusion.

Currently, we build reports and dashboards based on requirements from internal users or end users. We do not have specific metrics to define if it is the best solution.

The per-user cost in the ultimate plan of Adobe Workfront is approximately $1,232 when purchasing 800 to 1,000 licenses.

The ultimate plan includes Fusion, which is an excellent automation tool. In the premier plan, which costs less, Fusion is charged extra based on per scenario. Since we have numerous scenarios running in automation, paying for each scenario separately is not cost-effective. The ultimate plan is the best option for companies.

I previously worked as an Adobe Experience Manager content author, building websites for the automobile industry. However, I found that Adobe Workfront requires more strategic thinking in terms of solution design, filter creation, and task management, making it a more engaging tool to learn.

Adobe Workfront is a fantastic tool for automating workflows, managing users, checking utilization, and approving timesheets. This is the best option that anybody can implement.

I would rate Adobe Workfront 8.5 out of 10, with points deducted primarily due to downtimes. As a product and solution, it deserves a 9.5 rating.

Adobe Workfront is a cloud-based work management platform, enabling teams and organizations to plan, track, and manage their work effectively. It offers a centralized management platform for work requests, project intake, data capture, project reviews, and collaboration between teams. Adobe Workfront provides tools for planning, allocating resources, tracking project progress, and includes features for Agile and hybrid work styles. It helps with resource management through capacity planning and skill-based resource assignment, ensuring the right people work on the right tasks.

Adobe Workfront facilitates collaboration across teams through shared workspaces, communication tools, and review and approval processes. These elements are important when tasks connect with the business. Reporting also plays a role, as we need to provide dashboard and reporting tools to gain insights into project performance and team productivity. Adobe Workfront acts as a central system for orchestrating all work within our organization.

In my company, we are a customer of Adobe.

Adobe Workfront has helped our organization by centralizing project management, improving visibility across teams, and aligning work with business priorities. Features like real-time dashboards, automated workflows, and resource allocation have reduced manual follow-ups and increased accountability. As a result, we’ve seen better collaboration, faster project delivery, and clearer reporting for leadership.

Adobe Workfront is an easy tool to use with multiple functionalities available. As per the Adobe Campaign Classic, Adobe Workfront is very easy, and we can use it with manual works. Adobe Workfront acts as a centralized platform, providing a single source of truth for project tasks and resources. It supports Agile methodologies such as Kanban and Scrum, enabling teams to manage projects in iterations and adapt to changing needs.

Users can create and customize workflows to fit specific team processes and project requirements, automating tasks and streamlining approvals.

Adobe Workfront provides information for users, teams, and leadership, built from reports, calendars, and external pages, offering a personalized view of project status, issues, and other key metrics. The reporting features are used to provide robust capabilities to track and analyze project performance, resource collections, resource allocations, and other key metrics. Users can create various reports including list reports, chart reports, and matrix reports, using combinations of filters, views, and groupings to customize the displayed data. Adobe Workfront also offers the ability to schedule report delivery and share reports with other users.

There are multiple scheduling and delivery options available in the reporting areas. It acts as a centralized platform for work requests, project intake, data capture, project reviews, and collaboration between teams. Adobe Workfront provides tools for planning, allocating resources, tracking project progress, and includes features for Agile and hybrid work styles.

There are several features that could improve Adobe Workfront. Enhancing search functionality is important; we can optimize integrations and streamline workflows. Specific areas for improvement include expanding name search capabilities and enabling dual filtering for project type and owner. Improving the efficiency of converting issues to projects is also essential; when converting issues to projects, users should remain on the same page rather than being redirected. A success notification with a link to the new project would suffice.

We can enhance integrations, such as ensuring Adobe Workfront integrates more seamlessly with other Adobe products like Experience Manager and Creative Cloud. Additionally, administrators should have easier ways to enable and disable email notifications with a simple on-off switch. To improve project performance, we can implement a clear design with larger titles, dividing lines, and immediate error messages for invalid numbers.

Adobe Workfront is stable and has a good reputation for stability. Although some users report performance issues and minor bugs, these are addressed quickly. Adobe Workfront provides a stable foundation for project management, and its stability has improved over time, with no major bugs affecting the tool. Status-wise, it is well monitored for server reliability and potential issues; overall, it is very stable.

When issues arise in Adobe Workfront, such as when working on a workflow and a random field or URL is not working, or we are unable to open the workflow or template, we need to contact the Adobe support team. The Adobe support team provides assistance to users and administrators by addressing issues, answering questions, and offering guidance on using the platform effectively. They offer various support channels including phone, online resources, communities, and forums.

They help troubleshoot issues by resolving technical problems encountered while using Adobe Workfront. They provide answers and guidance on how to resolve issues, such as clearing cookies and cache, and assist in best practice configuration and optimization of the platform. They manage access to Adobe Workfront and related resources like the Workfront community, and multiple support channels are available. The Adobe support team consists of authorized support contacts within a company who have specific credentials to access support resources like the help desk or innovation lab. Users can submit support cases online through Experience League or other relevant pages like Adobe Commerce.

The initial setup in Adobe Workfront is straightforward. The process involves managing users or groups and integrating with Adobe products. This includes setting up domains and enabling SSO if needed, and instance setup requires Workfront domains configuration and single sign-on settings, along with importing projects and creating custom forms to capture specific information related to the projects and tasks. These configurations are important and very simple for initial setup.

Adobe Workfront features include expenses associated with a project or task that are not related to labor hours. This can include items such as mileage, supplies, software, licenses, and travel costs. To retrieve expenses in Adobe Workfront, you navigate to the specific project or task where the expense was added and look for the section typically labeled expenses in the left panel. This section lists all expenses associated with that particular project or task.

Workfront reporting tools allow for the creation of custom reports to view and analyze expenses across multiple projects and tasks, providing a comprehensive overview of expense costs. To manage expenses in Adobe Workfront, various expense types can be created, such as software and travel, with defined units and rates to standardize expense tracking. Users can add expenses to projects or tasks, detailing descriptions, expense types, planned and actual amounts, with fields available as per user permissions and system configuration within Adobe Workfront.

In Adobe Workfront, I have used the custom dashboard for organizing and displaying relevant reports. This custom dashboard provides information for users, teams, and leadership, and is built from reports, calendars, and external pages, offering a personalized view of project status, issues, and other key metrics.

To create a dashboard, you navigate to the dashboard area from the main menu, click New Dashboard, and give it a name as per convenience. The dashboard is essentially a canvas where we can add reports, calendars, and external pages. After that, we can add reports and other content or create new ones directly within the dashboard builder. Then we can add a report, navigate to a dashboard, and choose the newly created dashboard. We can customize a dashboard appearance and layout according to our needs.

Making a dashboard the landing page means it is a new Adobe Workfront experience; we can make a dashboard the landing page for specific users or groups. To navigate, we have the option to set up interface and layout templates, edit the relevant template, and add the dashboard.

The capability of Adobe Workfront is very important. While working on Adobe Workfront, if some things are not working properly, we have the functionality—it is a cloud-based work management platform, enabling teams and organizations to plan, track, and manage their work effectively.

I rate Adobe Workfront 8 out of 10.

I have 3.4 years of experience in Adobe Workfront. I don't know any other product as I have only worked with Adobe Workfront.

I am a consultant, working on various aspects such as Adobe Workfront configuration and multiple integrations. I would address myself as a solution architect or consultant.

I have worked with two organizations. One is a complete service-based organization where I worked for the creative agency, financial organization, and support-based organization. Now I'm working with a product-based company for my internal team and internal people.

The most valuable feature of Adobe Workfront that I have found is the external lookup. External lookup inside the custom forms helps users to get the outputs based on the API. Based on that API, the key and value pair enables users to get region information if it was in the country. The fields are based on the logic.

Data Connect is one of the very useful features. We can use Adobe Workfront data into advanced charts. There is a limited chart structure and limited visual representation inside Adobe Workfront, but Data Connect gives very complex charts, and everything we can easily implement within Power BI or Tableau. The data store will be in the data warehouse, which is a third-party feature where we can write queries and filter information.

The dashboards are collections of reports. When we want to filter information, such as group projects, groups of information, or document approvals, we can create reports and fetch all the reports into one dashboard. Based on the dashboard action, I can share the dashboards with specific teams. If it's a creative team or creative owner team, they can view that on their homepage. They can get a bundle of information such as what they are working on, pending approvals, reviews, and everything they can view on the homepage without going completely inside the system.

The user interface needs improvement. It currently has a list feature that appears technical, but it needs enhancement to be smoother and more colorful. When hovering over something, it should show information about the particular feature.

The performance needs to be smoother, and there is room for improvement in Data Connect while writing queries and integrating with other analysis tools. The boards feature needs improvement to work more smoothly and provide easier connection with projects. A Kanban board needs to be connected with other projects, and that process should be more streamlined.

I would rate my use of the solution as six.

When it comes to reliability, Adobe Workfront is excellent. When there is server maintenance or issues, the Adobe team announces that they are going to perform service tasks and the system will be down for a specific duration. We are always aware of what is happening. There is no data loss, indicating good reliability with Adobe Workfront. From an integration perspective, if data is missed once, it will capture that missed data another time.

The solution is really scalable. Considering features that need more scalability, I would mention the Kanban and Gantt chart. The Gantt chart needs more scalability as it's quite hard to understand for new users or project managers. Apart from that, everything is good and really scalable.

I have connected multiple times with technical support for API-oriented queries. In my initial days, I raised queries with the Adobe team. They have a good supporting team with levels from L7 to L1. If L5 does not understand, it moves to L4. If they can't solve it, it moves to a higher level. We can get good solutions, but it takes some time. In many instances, we resolved issues ourselves instead of waiting for the Adobe support team's L4 response.

Positive

My complete experience has been with Adobe Workfront. I used Primo productivity management before, but I found Adobe Workfront to be a very user-friendly environment. Primo productivity management had too much information.

During the initial setup, one of the major challenges I faced was understanding business needs in relation to Adobe Workfront requirements. Their terminologies are quite different when it comes to Adobe Workfront. The initial conversation with our client and understanding their features was crucial. It was challenging to transform functional requirements into technical requirements. After six months, I understood how to implement their requirements appropriately.

I am a consultant, so I don't actively use Adobe Workfront. My role is to help customers learn how to use it, set it up, or optimize current use cases.

Adobe Workfront is a very broad platform. When examining its primary function, it excels at project management and collaborative work management. The flexibility of it and the ability to make it do things that it wasn't necessarily intended to do is really one of its strong suits because you can use it for many things beyond overall project management in terms of general metadata compiling.

The organizational structure within the system is flexible enough to add different types of users and different types of organizations, and you can have them be as visible or as hidden to other users as desired. There is an inherent factor of security involved where you have the ability to have multiple functions operating within the same instance without any of that work overlapping or anybody being able to see what's going on in those other areas unless intended.

I've been getting many requests recently for use in the agile space, and their agile tools are not as good as they could be, not as good as competitor products. In terms of the overall platform, they move in specific directions, and I don't know if those directions necessarily always take a full customer-base approach rather than catering to the demands of their higher-level customers. They could stand to democratize a little bit.

Whenever discussion turns to Adobe, pricing always gets to be difficult. I've been through a couple of contract renewals in past roles and the cost can get down into the nickel-and-dime sort of thing, where functionality is really hampered if you're not willing to spend for the highest level of licensing.

I have been using Adobe Workfront in my career for about nine years.

It is cyclical with Adobe Workfront. As they go through improvements and enhancements, I tend to find that there is a bit more tendency toward downtime and instability. But overall in the last three years, the stability of the platform has been pretty consistent and reliable.

There has been a shift since Adobe purchased Adobe Workfront in 2019-2020. There has been a gradual shift where in some cases support goes offshore, and I feel there's not as much depth of understanding of the product as there has been in the past when it was all region-based support. I find that some answers require going through lower-level support that may not necessarily be able to help, and it takes longer to get those answers.

There is an admin function inherent to Adobe Workfront. Every organization should have at least one global system administrator, and that person should be responsible for maintenance, understanding improvements, and enhancements. The only time you need to rely on Adobe support is if you have a problem that you can't figure out yourself. It is considered a citizen admin system, and you don't need to be an IT professional to be an administrator.

Positive

You definitely need a professional to help you through the initial setup of Adobe Workfront. The system has so much depth and possibility that unless you have a very well-mapped-out use case and somebody to help guide you through that, it can be very overwhelming and daunting. But with that kind of support, it's relatively easy to maintain as long as you know what you're doing with it.

From the time you begin a discovery to actually implementing Adobe Workfront to the point where you could use it, if people put the right amount of time into it, it takes anywhere between four to six months.

Nothing really compares to Adobe Workfront. There are lots of work management platforms available, but they're either more specific to an industry or methodology, or they're just not as robust as Adobe Workfront. Jira is an excellent tool for development but not so great for marketing project management. When looking at platforms on the opposite end of the spectrum such as monday.com or Workamajig, they don't have the depth of function that Adobe Workfront has.

I would rate the support an eight on a scale from 1 to 10, with 10 being the highest.

I'm a huge fan, supporter, and champion of Adobe Workfront. I rate it a 10 for everything overall.

I work for an organization that is an official Adobe partner.

We specifically implement Adobe Workfront for other clients as Deloitte is a partner of Adobe. We work with different clients to implement Workfront and streamline marketing resource management with DAM and related solutions. I have been in a lead position role for the past two years, starting as a Workfront co-dev before growing into Fusion automation integration. I have over seven years of experience within the marketing space, digital marketing strategies, and brand growth.

The main use cases involve organizational marketing resource management for Adobe Workfront where clients plan, strategize, and track the progress of marketing initiatives across different collaborating teams. We implement Workfront across teams and groups, defining their workflows within the tools for seamless login to one platform where they can collaborate and manage daily activities while keeping leadership informed through visibility reports. The primary focus is streamlining the entire content supply chain for marketing departments of different organizations.

Currently, we have DAM integration with Adobe Experience Manager assets and proofing capabilities, which is Adobe Workfront's best USP. The recently launched Workfront planning feature allows users to plan and strategize marketing initiatives within the platform, beyond just managing intakes and campaign briefs. The combination of Adobe Workfront and Fusion enables seamless integration with various tools, including use cases where we generate creative briefs and campaign contents using large language models and generative AI.

Adobe Workfront supports scrum and Kanban boards for agile teams. Teams can create iterations and push tasks to those iterations, enabling agile framework implementation with reporting on iterations and burn-down charts as native functionality. The workload balance and resource planner facilitate better team planning, which is crucial within the agile framework.

The organization needs to define schedules within Adobe Workfront for effective capacity planning. Multiple factors need consideration, ensuring users actively log times so capacity planners reflect actual team capacity, helping project owners and sponsors plan accordingly.

Adobe Workfront offers a streamlined process that is more user-friendly compared to other tools in the market. It provides comprehensive features with built-in integration for creative tools, addressing the pain point of creative collaboration in the content supply chain. The platform excels in team collaboration and external user onboarding, allowing collaboration with external agencies with limited access requirements. The tool can be customized in ways that are user-friendly and easily understandable for end users.

The platform helps filter database information for different users of Adobe Workfront. We can create combinations of reports to track projects and tasks based on statuses using wildcards. Users viewing reports see specific items under their name through defined filters, which provide real-time information and good user experience. Team-level dashboards offer a holistic view of team progress across different work items.

The platform could benefit from additional customization features. The external lookup field, which allows custom API calls to fill data, is limited to two thousand results, which is insufficient for many API calls. While this was increased from two hundred based on customer demands, there is room for further improvement.

The native connector currently only allows users to pick assets from AEM, but should also enable pulling content fragments that users want to link to projects or tasks. Incorporating content fragment selection in the native connector with AEM assets would be a significant enhancement.

Certain regions experience latency issues when dealing with large quantities of projects, which could be improved from Adobe's side.

I have four years of experience in Adobe Workfront implementation and Fusion.

During the design discovery phase, we encounter situations where there are product limitations but customer needs persist. These challenges are addressed by communicating with Adobe about potential implementations and finding workarounds for product limitations. This creates opportunities to develop innovative solutions to better serve clients and fulfill their requirements.

Positive

Having worked with Asana, Wrike, and Primavera, I would rate Adobe Workfront as the best MLM tool, scoring ten out of ten. While other solutions have their own customizations, Adobe Workfront stands out for its user-friendliness.

Organizations have been successfully using Adobe Workfront for the past decade, including renowned MNCs and large corporations for their site management, asset management, and entire content supply chain. Adobe is positioning it as their project management tool in competition, and they have been the foster leaders for the past two years. They continue to bring more innovation to the product, which will help scale up marketing teams and work more efficiently in the coming five to ten years. Based on my experience, I rate Adobe Workfront 8 out of 10.

I am a developer using Adobe Workfront, and I was designing the workflow for the client. I was more into the Fusion side, Adobe Workfront Fusion, focusing on the automation and integration, where I have been working for almost two years. When compared with other project management tools or workflow tools, Adobe Workfront is far better than other tools in the market now. It has a good UI. Being an Adobe tool, it is far easier to connect Adobe Workfront with other Adobe tools, which is an added advantage when compared with other tools. It also has its own API, allowing us to connect with other applications. Being an Adobe tool, it easily connects with all other Adobe ecosystems, which is good. That is the main advantage here.

I was working in a startup previously, where we implemented Adobe Workfront for two types of companies: one is an enterprise and another is a medium-level company. For the enterprise, they have multiple tools to integrate with Adobe Workfront for their workflow. For the medium company, there are typically one or two types of integrations involved. This tool is adaptable for any type of company. Whether it is enterprise, medium, or startup, whatever workflows they want, we can easily set them up in Adobe Workfront.

You can set up the complete workflow from start to end with Adobe Workfront, such as content creation, content publication, and getting that approval process, storing it somewhere. You will get the entire end-to-end process through Adobe Workfront.

There are two kinds of dashboards in Adobe Workfront. One is a normal dashboard and an interactive dashboard. A normal dashboard is a combination of multiple reports, allowing us to create several reports and merge them in one place and add them to the dashboard. The other is interactive viewing where you can provide the URL of other applications or services. This allows you to get details from the same dashboard. Dashboards are also good to know about who is working on a higher level, as they can easily understand how the programs, portfolios, and projects flow, including how much it is spending. Some basic details are easily accessible in the single dashboard.

I use the custom dashboards in Adobe Workfront.

When it comes to the benefits of using Adobe Workfront, I am not sure about the other tools, but here we can set up different time zones and costs. For example, if it is India, it is in Indian rupees, and if it is the US, we can set it as dollars. This kind of customization I can see in Adobe Workfront. In other tools, I have not seen this kind of option. Additionally, external API calls are available, allowing us to set some business rules, such as a pop-up that says, 'do not delete this' or 'do not update this.' Some kind of warning pop-ups can be based on business rules. Based on the recent updates, we are now waiting for the chatbot AI or something similar, which should be available soon, maybe in the next quarter.

I have been using Adobe Workfront for almost two and a half years.

Adobe Workfront is stable. I have not faced any challenges with the stability of Adobe Workfront. From storage only, we are facing some challenges, which is why we are transferring those assets into the digital asset management tool. Other than that, we have not faced any kind of challenges.

Scalability in Adobe Workfront means it does not have its own storage space, since it is not a digital asset management tool. It is a project management tool. When it comes to scalability, if you have a large number of assets, you have to integrate Adobe Workfront with any other DAM, digital asset management tool. Then you can increase the scalability of storing the spaces.

I have previously used different solutions.

Setting up Adobe Workfront is easy to do. The only thing is getting the requirements and converting the requirement of the business solution into the technical solution. That is the only thing we have to do. Once we find those requirements, we can easily set it up. The UI is so easy when compared with other tools, and we can easily set up the entire workflow.

I would recommend Adobe Workfront to other people, particularly from the domain of MarTech. It will be very useful for those involved in creating campaigns and similar activities, as it is far better. On a scale of one to ten, I rate Adobe Workfront a nine out of ten.

Adobe Workfront was primarily our main project management software for creative projects. Anything requested by the creative department would be done through Workfront, from submission via a creative brief to fulfillment and archiving of final assets on project close. We used Adobe Workfront Fusion to automate various workflows, triggering actions in Workfront to communicate with other software platforms.

Workfront centralizes the tasks, the assignment of tasks, and documents required to do the work, streamlining communication and information availability, thus improving organization and reducing dependency on decentralized methods like email or servers.

Adobe Workfront offers a low barrier to entry, which makes it user-friendly and requires minimal training. It is designed specifically for creative work, making it suitable for a creative environment. 

Another valuable feature is its flexibility in task management, allowing users to use project templates and modify tasks as needed. Workfront automates archiving final assets, centralizes task assignments, and facilitates communication on project or task updates. It provides a robust platform to manage and review creative processes, enhancing clarity and accountability.

Adobe Workfront could improve its interface, which may benefit from an overhaul for better consistency between the web interface and the API. The current setup was not originally designed API-first, leading to some confusion and differences in available functions. 

Additionally, the low-code environment in Workfront Fusion is beneficial yet sometimes limiting, and it might be more powerful with enhancements.

In various capacities, I worked with Workfront for five years, where I was mainly focused on its use as a creative operations manager.

Overall, I would say the solution has a +90% uptime. However, there were times when the platform struggled with stability, resulting in some inconsistency in operations. Workfront provides tools to recover from such failures, which is helpful in maintaining productivity.

We had enterprise-level tech support, which was satisfactory. Support generally responded within twenty-four hours, and critical issues were addressed even faster, often within minutes. 

Overall, I would rate the support at 75% to 80% in terms of effectiveness.

Positive

The initial setup had a steep learning curve, particularly in setting up request queues and project templates. The documentation was adequate yet not excellent, leading to challenges in setting up a new Workfront instance, taking about a week instead of two days.

I took over an existing implementation of Workfront and subsequently expanded it by bringing in a new department. I began by asking them to define their processes simply and create project types and approval flows based on those high-level descriptions.

The return on investment for Workfront comes from improved organization and availability of information rather than monetary gains. Centralizing the tasks and communications in Workfront eliminates the decentralized methods used earlier, providing unambiguous tracking of requests and making collaboration seamless.

Workfront incurs around a hundred thousand plus dollars per year. Licensing is strict, particularly with free accounts, however, it offers flexibility in project access, which could be enhanced further to suit enterprise needs better.

I would recommend Adobe Workfront to organizations of a certain size with significant numbers of requesters and workers, particularly for creative groups needing centralized task management and collaboration. If a group is smaller, Workfront might not be the best fit, and a more compact solution should be considered. 

Overall, I rate Adobe Workfront a seven out of ten.

We use Adobe Workfront for project management where users manage their projects, add tasks to the project, track their timeline, and get approvals from project managers.

I work on the developer side where we handle all the requests in Adobe Workfront. These Agile projects are handled by project managers, with a dedicated project manager for every country and brand. We primarily lead the development side of Adobe Workfront.

The best features in Adobe Workfront from my perspective are the project management and automation from the back end, the tool called Workfront Fusion where we can automate processes. The approvals, layout templates, and setup area in Adobe Workfront are also valuable features.

I utilized the customizable dashboards in Adobe Workfront extensively.

Regarding role-based access control, Adobe Workfront logins have a limited session duration, requiring users to re-login periodically. This enhances security during screen sharing and other activities, making it a secure application.

With the help of reports in Adobe Workfront, end users can oversee all assignments to a specific project. We created a report that reduced efficiency by 50%. We also created quarterly reports tracking newly added users with comprehensive details.

In Adobe Workfront, there is a limit of 2,000 users that can be shown on a page. I would suggest increasing this to something around 10,000 so end users can search all objects more efficiently. Currently, users need to navigate through multiple pages to view all entries. Apart from this, I don't have any major improvements to suggest.

I have been using Adobe Workfront for three years.

The initial setup of Adobe Workfront was clear. With the help of documentation, we completed all tasks and encountered minimal issues. When issues arose, we reached out to Adobe and raised tickets with them.

In our project, we did not use any resource plans and utilization in Adobe Workfront. These aspects are handled by the project manager and end users themselves. As developers, we don't handle resource planners and utilization requests.

I am not sure about any disadvantages or cons of Adobe Workfront at this time.

The customer service is pretty good. When we raise technical issues with Adobe Workfront, they respond based on priority and resolve them within two or three business days. For enhancements, the process may take months, but they inform us once they release new products or integrations.

I would rate the tech support of Adobe Workfront as eight out of ten.

I have not worked with any other project management solutions before Adobe Workfront.

The initial setup of Adobe Workfront was clear. With the help of documentation, we completed all tasks and encountered minimal issues. When issues arose, we reached out to Adobe and raised tickets with them.

I did not integrate Adobe Workfront with the Creative Cloud or Experience Manager solution, but one of my senior leads has integrated it with AEM assets and AEM DAM from scratch.

I have worked on Jira from a developer perspective, though not extensively on the administrative side. I am familiar with task management aspects of the platform.

The main difference between Adobe Workfront and Jira is that Adobe Workfront is more focused on marketing, allowing users to get approvals, create tasks, and provide project managers with an overview of all organizational projects. Jira is more oriented toward developer software and development work.

Adobe Workfront is an excellent tool for marketing purposes, providing comprehensive project overviews, and creating reports and dashboards.

As a less experienced professional, I am not in a position to provide extensive suggestions regarding Adobe Workfront.

My overall rating for Adobe Workfront is 7 out of 10.