Change the system. Keep the brand.
A shared styling foundation removed repeated page edits while leaving room for programs to remain distinct.
A shared catalog change could become a series of separate jobs. V6 catalog styles did not automatically inherit the surrounding program’s template styles, so each program needed manual alignment. I owned the effort to make common changes carry across applicable programs while preserving the branding that made each one distinct.
At a glance
- Shared updates reached applicable programs without page-by-page styling edits.
- Released in 2025, with smoke validation and production updates coordinated in batches.
Approach: Preserved legacy variables while separating shared presentation from program-specific branding and coordinating release dependencies.
Production release and propagation are owner-confirmed; architecture visuals are illustrative reconstructions.
Explore the complete case study.
Read the design decisions, supporting visuals, validation and outcomes, including clearly labeled reconstructions and evidence notes.
Prefer a conversation? Email Erika.
