2U · LIVE EXPERIENCE SYSTEM · ORGANIZATIONAL LEVERAGE

More than 1,000 experiences could not keep being one-off pages.So we built the system underneath them.

More than 1,000 live experiences across 500+ programs made one-off page design impossible to sustain. I led four designers in creating shared templates and rules with content, analytics, and engineering. The system cut design time by up to 75% and supported 10× more testing.

SYSTEM ARCHITECTURE · LIVE PROGRAM + CONTENT RULES

Live university program implementation board

TEMPLATE FAMILIES · ONE GRAMMAR, DISTINCT JOURNEYS

DEGREE
2U DEGREE template
BOOTCAMP
2U BOOTCAMP template
EXEC ED
2U EXEC ED template

IMPACT

1,000+LIVE EXPERIENCES SUPPORTED
≤75%REDUCTION IN PAGE-DESIGN TIME
10×TESTING-VOLUME INCREASE
Few → manyFEW TEMPLATES SUPPORTING 1,000+ EXPERIENCES

THE SCALE PROBLEM

Variation was real.Rebuilding every page was not the answer.

Every program had real differences in brand, credential, schedule, evidence, and content. Treating each page as a one-off made the work slow and uneven, and very little learning carried from one program to the next.

Competitive and higher-education template analysis
AUDIT THE LANDSCAPE · Recurring structures, gaps, and competitive patterns.
Current template inventory showing repeated variation
SEPARATE SIGNAL FROM LEGACY · Keep meaningful differences and remove inherited production habits.

INITIAL BELIEF

More templates would absorb the variation.

The portfolio had grown by adding page types and local exceptions.

AUDIT EVIDENCE

The same structures kept recurring.

The audit separated product-specific needs from variation created by legacy production habits.

ARCHITECTURAL DECISION

Create one grammar with governed flexibility.

Stable sequencing, flexible modules, rules over one-offs, and repeatable experiment seams.

THE ARCHITECTURAL SHIFT

We did not need a bigger template library.We needed a system for making experiences.

01

Stable page grammar

A consistent sequence for orientation, value, proof, outcomes, curriculum, requirements, and conversion.

02

Flexible modules

Sections adapt to product type, available evidence, content depth, and institutional brand.

03

Rules over one-offs

Defined when a module appears, how it behaves, and which variants are appropriate.

04

Experiment-ready seams

Created repeatable places to test messaging, proof, order, forms, and personalization.

DEGREE

Deep proof, curriculum, requirements, and long-form decision support.

DEGREE full template review board

BOOTCAMP

Accelerated outcomes, skills, financing, and a tighter conversion rhythm.

BOOTCAMP full template review board

EXECUTIVE EDUCATION

Immediate relevance, schedule, credibility, and concise action.

EXECUTIVE EDUCATION full template review board

SCALE WITHOUT GENERICISM

The system had to support many institutionswithout becoming visually anonymous.

Flexible color, typography, imagery, logos, and module combinations allowed institutional identity to remain visible while shared interaction and production rules did the operational work.

Institutional brand flexibility palette 1
Institutional brand flexibility palette 2
Institutional brand flexibility palette 3
Institutional brand flexibility palette 4

THE SYSTEM CREATED CAPACITY TO LEARN

Reusable structure made experimentationfaster, cleaner, and cumulative.

Because the page structure stayed stable, teams could test the message, evidence, module order, form, or personalization without rebuilding the page each time.

Repeatable full-page experiment structure
FEATURED SCALE · FULL PAGES
Governed hero experiment variants
PAGE VARIANTS
Reusable accordion interaction states
INTERACTION STATES

ORGANIZATIONAL LEVERAGE

Scale came from shared judgment,not just reusable components.

DESIGN LEADERSHIP

Four-designer workstream

PRODUCT

Roadmap and prioritization

ENGINEERING

Implementation constraints

CONTENT + ANALYTICS

Narrative and experiment evidence

DESIGN SYSTEM

Components, tokens, accessibility

DESIGN LEADERSHIP

I led a four-designer workstream and used regular critique to keep decisions and craft consistent across hundreds of programs.

TEMPLATE GOVERNANCE

Clarified what belonged in the core system, what varied by product family, and what justified a new pattern.

DESIGN-SYSTEM PARTNERSHIP

Connected the page architecture to shared components, tokens, responsive behavior, and implementation constraints.

OPERATIONAL FEEDBACK

We kept revising the templates after launch using production issues and experiment results.

The leverage was not in owning every page.

It was giving designers and partners one dependable way to decide, build, critique, and improve work across the portfolio.

THE OUTCOME

A small set of rules createdoperational leverage across 1,000+ live experiences.

The system cut the work required for each new page and gave teams a common way to review, build, and test. Accessibility and program-specific needs were part of the template from the start.

1,000+LIVE EXPERIENCES SUPPORTED
≤75%FASTER PAGE-DESIGN TIME
10×TESTING-VOLUME INCREASE
SystemTEMPLATES, RULES, GOVERNANCE, LEARNING