work

Cutting email production from 40 minutes to 5—and tripling weekly output

Two designers were manually coding a daily national email and had no capacity to develop personalized content. In a two-week engagement, I redesigned their production workflow and built an editor-native system of reusable, guarded email modules—without adding budget or interrupting scheduled launches.

Composite showing the guided UNIQLO email-production system and a segmented email output.
Role
  • Service Design
  • Workflow Research
  • Front-end Implementation
Result
40 → 5 minutes per build · 7 → 21 emails per week · 2-week rollout
Year
2018

Platforms
Internal email production system
THE BOTTLENECK

A personalization strategy was blocked by a fragile production workflow

UNIQLO wanted to create more relevant email content, but two designers were already at capacity producing and manually coding one national send each day. The inherited codebase was unreliable: a routine build took about 40 minutes, while troubleshooting could stretch the work to several hours. The team had neither the production capacity nor the dependable mechanism needed to segment campaigns by audience, region, or context. Designing more campaign concepts would not solve the constraint upstream.

Visual comparing one national UNIQLO email against different regional weather contexts in Portland, San Francisco, and Miami.
Regional mismatch: one national campaign shown against different local contexts.
THE DIAGNOSIS

The highest-leverage intervention was removing technical work from the designers

I spent a day observing the existing production process and mapping each step required to move from design to launch. Repetitive editing, code interpretation, and QA created most of the uncertainty. The intervention therefore had to do more than accelerate typing: it needed to remove existing defects, prevent designers from introducing new ones, and shorten the path to a validated build. Given the two-week timeline and $0 added budget, embedding a maintainable system in the team’s existing editor was more practical than creating a standalone application.

Before-and-after workflow comparing a manual, uncertain email build with a guided, repeatable process.Before-and-after workflow comparing a manual, uncertain email build with a guided, repeatable process.
Before and after workflow, including the 40-minute versus 5-minute contrast.
THE SYSTEM

Reusable blocks and guided fields made the safe path the fastest path

I rebuilt the workflow as three coordinated parts.

Standardized foundationI sanitized and modularized the inherited master code so every email began from a dependable source.

Reusable block libraryDesigners inserted approved modules through memorable shortcuts instead of locating, copying, and modifying old code.

Guided content fieldsEach module prompted only for values such as image URL, dimensions, and alt text, while the system protected structural code and repeated shared values automatically.

Guided template showing content prompts and protected structural email code.Guided template showing content prompts and protected structural email code.
System behavior: designers enter content values while the workflow handles structural code and repeated fields.

I tested the system against the active build queue, piloted it with the designers, added requested campaign variants, and created a video walkthrough and shortcut guide so the team could operate it independently.

THE OUTCOME

Build time fell 87.5%, giving the team capacity to triple weekly output

40 → 5 minBuild time
7 → 21Emails per week
2 weeksProduction rollout
$0Added business spend

During the pilot, average build time fell from approximately 40 minutes to five. The team increased weekly output from 7 to 21 emails while the new workflow was implemented alongside the normal launch calendar, with no added business spend.

That capacity enabled geo-based product recommendations, live polls, gender-segmented creative, closer alignment with the social team, and more product education. These were content capabilities enabled by the workflow; the project did not measure downstream subscriber or revenue impact.

Paired UNIQLO email examples showing differentiated customer-facing content enabled by the new workflow.Paired UNIQLO email examples showing differentiated customer-facing content enabled by the new workflow.
Customer-facing result: paired examples of segmented or context-specific email content.

Takeaway: Customer experience can be constrained by invisible internal systems. Improving the production workflow created more leverage than designing additional campaign concepts would have.