Work/Case study 01

120 hours to 1

Where
A healthcare marketing team
Roles
Web, email and SEO
Systems
Workfront, Workfront Fusion, WordPress, Google search data, GA4
Runs
Once every morning

I was the web developer on a healthcare marketing team. When the team lost its email developer and its SEO specialist, I took on both jobs. Then I built the system that does all three, and now I spend about an hour a week reviewing its work.

Web, email and SEO, held by one person
3roles
Three full-time roles’ worth of work a week
120hrs
My time a week now, reviewing and approving
1hr
Longest wait on any task that reaches me
1day
01Before

Three jobs landed on one desk.

I started as the web developer. Ten to fifteen website requests came through Workfront every week, and each one meant making the change, capturing it, submitting a proof and following up.

Then the team lost its email developer and its SEO specialist. Nobody assigned me their work. I wanted both jobs, so I took them.

Email meant two or three sends a week, each one built for fifteen brands and tested across mail providers in light and dark mode. SEO had no queue at all. It was a steady run of questions about search traffic, each one answered by hand.

Fig. 1A week of work across the three roles, every hour of it done by hand.
02During

Email first, then the whole queue.

I began with email because it was the hardest. An agent takes one design, as an image or bare HTML, and produces it for each of the fifteen brands, built to hold up across mail providers and in light and dark mode. It checks its own work in inbox previews and shows me the results as screenshots I can click through. Early on it took several passes. Now it usually gets an email right the first time.

Then I built the agent that reads Workfront every morning, through a Fusion scenario that connects it to Workfront. Working out what is owed is harder than reading a task list. I get tagged in updates, projects move forward in comment threads, and people finish tasks without marking them complete. The agent sorts that out and hands each job to the agent that does it.

Website requests go to an agent that makes the change through the WordPress API, down to replacing an image while keeping its address the same. It screenshots everything it touched and sends that to me. Once I approve, those screenshots go back to Workfront as a proof, with the right reviewers, or as a new version of a proof that already exists.

SEO became a different job. An agent builds trends from our Google search data and checks each one against GA4. Blog clicks up ten percent sounds like news until you see those visitors do not convert. Only the findings that survive that check get shared.

It was not right the first time. Early on the agent posted Workfront comments on my behalf and referred to me in the third person. That is the reason nothing leaves without my review.

Fig. 2The two agents. Each does every step but one, and it is the same step in both.
03After

About an hour a week.

I run it once a morning. I look through the screenshots, approve what is right, and the system submits the work, files the proofs and follows up. That comes to about an hour a week, and an hour may be generous. I almost never open Workfront itself.

Nothing that reaches me waits longer than a day. By the team’s Workfront numbers I carry the largest workload and have the fastest turnaround.

The SEO agent runs its own discovery every day and answers the questions I am sent. Those questions do not come through Workfront yet. I am pushing for that next.

Fig. 3The same week now. The one hour left is my review.
04Next

Have a process that runs on someone’s manual effort?