[Event Follow-Up] Scaling Marketing Operations: McKesson’s Automation Journey with Workfront & Fusion – June 16, 2026 | Community
Skip to main content
CynthiaBoon
Adobe Employee
Adobe Employee
June 16, 2026

[Event Follow-Up] Scaling Marketing Operations: McKesson’s Automation Journey with Workfront & Fusion – June 16, 2026

  • June 16, 2026
  • 1 reply
  • 70 views

 

Join Chris Perez, Sr. Director of Digital Marketing, and Amanda Letbetter, Director of Operations, Marketing Services at McKesson Corporate Affairs, where they share how they tackled the challenge of scaling work distribution and project management across a high-volume, multi-brand environment.  

Starting from a highly manual process, where project managers were juggling dashboards, Outlook calendars, and spreadsheets to assign work, they launched a Workfront Fusion automation scenario that now handles intake routing, project scoring, resource assignment, and template selection automatically. The result? So much time saved, allowing their teams to reclaim time to focus on higher-value strategic and collaborative work. 

If you weren’t able to attend live, or want to revisit any part of the session, you can access the resources below: 

Thank you for being part of the community and be sure to register for more upcoming events!  

 

1 reply

KristenS_WF
Level 7
June 16, 2026

Just watched the recording--great presentation.  Chris and Amanda--could you possibly speak in a little more detail as to how you are calculating availability to make assignments (slide 9, specifically the Review Current Project Load and Review Time Off Custom API modules)?

 

Thanks.

ChrisPe14
Level 2
July 10, 2026

Thanks for the question.

Availability is calculated using a combination of three factors:

  • Project score – a weighted measure of a team member's current workload.

     

  • Project status – the status and stage of active projects assigned to the individual.
  • PTO – time off recorded in Workfront.

For PTO, we evaluate whether a team member has any scheduled time off within four days of a project's due date. If they do, that is factored into the availability assessment to help avoid assignments that could be impacted by planned absences.

The due date used for this evaluation varies by project type (for example, Target Send Date, Webinar Date, etc.), but the logic is applied consistently regardless of which date field is being used. In all cases, the automation assesses whether the selected due date falls within four days of a scheduled PTO period before considering that resource available for assignment.

One thing I don’t think we mentioned in the demo was that Amanda’s team previously created a Fusion scenario to set the project score back to zero when a project’s status changes to complete, or scheduled to send. This prior automation also assists with ensuring that as work comes off of someone’s plate, we have an accurate depiction of where it stands when a new request comes in. 

One thing I don’t think we mentioned during the demo is that Amanda's team previously built a Fusion scenario that automatically resets a team member's project score to zero when a project's status changes to Complete or Scheduled to Send. This automation helps keep workload calculations accurate by removing completed work from the scoring model, ensuring we have an up-to-date view of resource availability when new requests are submitted.