Adobe Workfront

Run marketing and creative work in Adobe Workfront, from the first request to the approved asset.

Overview

Adobe Workfront consulting for marketing, creative and content operations

Adobe Workfront is Adobe's work management platform, used mostly by marketing, creative and content teams. Work arrives through request queues, runs as projects built from templates, goes through review and approval, and is reported on in dashboards that show status and capacity. Workfront Planning adds a planning layer where teams define their own record types, such as campaigns, audiences and regions, and connect them to the projects that deliver them. Workfront Fusion is Adobe's integration and automation tool for connecting Workfront to other systems.

Workfront suits organisations where many people ask a central marketing or creative team for work: brand and campaign teams across several business units or regions, in-house agencies and content studios. The problems it solves are familiar ones: requests arriving by email and chat, no view of who is overloaded, and approvals lost in long email threads.

Great Minds is a Sydney-based systems integrator. We design the intake, templates and approval paths first, then configure Workfront to match, and connect it to the tools around it: AEM Assets or another DAM for finished assets, the CRM and campaign tools that launch the work, and project tools used elsewhere in the business. We delivered a global digital asset management program for a retailer that included automated workflows and integrations with ecommerce and campaign tools, and the same thinking applies to Workfront.

Capabilities

What we set up in Adobe Workfront

Most Workfront projects cover these four areas. For connections between Workfront and other Adobe products, see our Adobe integration page.

01Intake and request queuesRequest queues with forms that ask for what the team actually needs, routing rules that assign each request, and a triage step so work is prioritised before anyone starts.

02Project templates and approvalsTemplates for your common job types, with tasks, durations, roles and approval steps built in, so a campaign or a product launch starts from the same plan every time.

03Capacity and reportingRoles, resource planning and dashboards that show what's in progress, who is overloaded and how long work takes, built from data your team already enters.

04Planning, Fusion and DAM integrationWorkfront Planning for campaign and portfolio plans, Workfront Fusion for flows to other systems, and AEM Assets or another DAM connected so approved files land where they're needed.

How we deliver

A Workfront rollout, from process design to adoption

We roll Workfront out team by team. The first team proves the design, and the templates and reports it uses become the starting point for the next.

01Map how work flows today

Interviews and workshops with requesters, producers and approvers: request types, job steps, review rounds, hand-offs and the reports leaders want. We agree the design before configuring.

02Configure the core

Groups, roles, access levels, custom forms, request queues, templates and approval paths, built in a sandbox or preview environment and tested with real jobs.

03Pilot and connect

One team runs live work in Workfront while we add the integrations it needs, such as asset delivery to the DAM or status updates to project tools in other parts of the business.

04Roll out and hand over

Further teams onboarded in waves, role-based training for requesters, project owners and administrators, and documentation of every template, form and integration.

Australian considerations

What Australian teams should check

Personal information in briefs and files. Requests, briefs and creative files can carry personal information: customer lists for a campaign, photos of people, staff details. Under the Privacy Act's APP 11, that information needs protecting and shouldn't be kept longer than needed. We design forms that ask for references rather than raw data, and set access levels so only the people working on a job can open its files.

Hosting and connected tools. Ask Adobe where your Workfront data is hosted, and check the hosting of anything Workfront Fusion connects to. An integration can move data offshore even when each platform is set up correctly.

Licensing. Workfront Fusion is licensed separately unless your Workfront package includes it, and Adobe's guidance on connecting Workfront to AEM Assets has changed over time. We check both against your contract and Adobe's current documentation before designing integrations, so you don't build on something you haven't licensed.

FAQ

Adobe Workfront questions

What is the difference between Workfront and Workfront Planning?

Workfront manages the work itself: requests, projects, tasks, approvals and time. Workfront Planning sits above it, with record types you define, such as campaigns, products or regions, and views of how they relate. Teams use Planning to decide what to do and Workfront to deliver it, with records connected between the two.

Can Workfront connect to AEM Assets?

Yes. Adobe offers connectors between Workfront and AEM Assets, and Workfront Fusion can also create and update assets and folders. Which option suits you depends on your AEM version and how much metadata needs to flow, and Adobe's recommendations have changed, so we confirm the current guidance at design. Our AEM Assets page covers the DAM side.

Should our marketing team use Workfront or Jira?

It depends on who else is involved. Workfront is built around marketing and creative operations, with request queues, review and approval and Adobe integration. Jira suits teams already working alongside software and IT teams on Atlassian. Some organisations use both and connect them. Our Jira page covers the Atlassian side.

What is Workfront Fusion used for?

Connecting Workfront to other systems and automating repeat steps: creating projects from CRM or campaign records, moving approved files to a DAM, or sending status updates to other tools. It's licensed separately unless your package includes it.

We already have Workfront but few people use it. Can you help?

Yes, and it's a common starting point. We review how requests, templates and approvals are set up, talk to the people avoiding the tool, and simplify. Usually that means fewer custom fields, shorter forms and approval paths that match how decisions are actually made.

How long does a Workfront implementation take?

A first team with intake, templates and approvals can be running in weeks. A multi-team rollout with Planning and integrations is delivered in waves over a few months. We give you a scoped plan and price after discovery.

Case studies