Travelers Insurance: Digital Experience Migration
Travelers runs 15 websites across personal insurance, business insurance and global brands, and none of them shared a single building block. With this Digital Experience (DXP) migration, I designed the modular component system underneath all of them. We proved it on a subsidiary site first, then it carried the new Travelers.com to launch.
Role
UX Designer
Team
Associate Creative Director
Art Director
4 Engineers
Product Manager
Tools
Figma, User Testing, AEM
Client
Travelers Insurance
Time
2023

15 sites, built from scratch
Every time Travelers needed a new web page, someone built it from scratch. Travelers.com, the Canada, UK and Ireland sites, and subsidiaries like Northland insurance had each grown one template at a time, and each had drifted a little further from the rest.
Then Travelers decided to move all 15 onto a new Digital Experience Platform and launch a new design system at the same time. The real job wasn't redesigning pages. It was designing the parts every page would be built from.
15
sites
migrated onto one platform
1
component library
shared by every brand, each in its own theme
3
breakpoints
every component built for desktop, tablet and mobile
400+
pages created
accessibility built into every component
What I did and the end result
Component exploration and design for hero, video cards, modals, sticky CTA bar, pagination, cards
Ensuring atomic component library aligned to accessibility standards of WCAG 2.1AA
200 un-moderated and 10 moderated usability tests
Template and page designs for Northlandins.com and Travelers.com
Reponsive design: 3 main screen sizes for desktop, tablet and mobile
Jan 2023
Northlandins.com
first brand live on the system
Mar 2024
Travelers.com
the flagship, launched March 11
A quote from the authors:
"We all know all the different possible uses, but we're treating each rewrite as a different project."
This calls for systems thinking. Instead of fifteen separate sites, I treated it as one connected system: the customers who use the pages, the authors who build them, the engineers who ship them, and the brands that need to stay distinct. Change any one of those, and it ripples through the rest.
Built from the atom up
Using atomic design, we built each level only from the one below it.
Atoms: type, colour, buttons, icons
Molecules: a form field (label, input and error message), pagination, search bar
Organisms: heroes, quote modules, claims panels
Templates: home, product and article pages
Fix a button once, and it's fixed in every quote module, hero and page that uses it.
Everything sat on the Travelers Design System and met WCAG 2.1 AA from day one. And brand lived in a separate theme layer, so one library could carry more than one brand.

Every component as a contract
A CMS component isn't done when it looks right in Figma. It's done when an engineer can build it, an author can fill it in and a brand team can theme it, without asking the designer.
In a system, the connections between the parts matter as much as the parts themselves. So, working side by side with engineering, I documented every component as a contract between the people who rely on it:
Data contract: the fields an author fills in
Interactivity: states and behaviours
Responsive behaviour: desktop, tablet and mobile
Styling options: what each brand can change
Fix a button once, and it's fixed in every quote module, hero and page that uses it.
Everything sat on the Travelers Design System and met WCAG 2.1 AA from day one. And brand lived in a separate theme layer, so one library could carry more than one brand.


11 page templates, one component library

01
Homepage

02
Personal insurance hub

03
Business insurance hub

04
Product page: Auto

05
Product page: Workers Comp

06
Editorial hub

07
Article

08
Campaign landing

09
Form

10
Contact us

11
Search results
Testing the system, not just the screens
In a library, one confusing pattern becomes confusion on every site that uses it. So before we locked the components, we ran 200 unmoderated tests and 10 moderated sessions with individual and business customers. We tested two layers separately, mirroring how the system was built. Usability tested the structure: can people find a clear path and act? Brand, look and feel tested the theme: how do the imagery and tone land?
200
unmoderated tests
via UserTesting
10
moderated sessions
live, facilitated sessions
2
audiences
individual and business customers
2
lenses
usability and brand, look & feel
WHO WE TESTED
People who might visit an insurer's website to learn about insurance, get a quote or find an agent online
USABILITY
GOAL
Identify potential usability issues and make recommendations to solve them
KEY QUESTIONS
Are users able to accomplish their goals and tasks?
Can users identify a clear path?
Are options and calls to action clear?
Do users have the right information to make a decision?
BRAND, LOOK & FEEL
GOAL
Understand user perceptions of the Travelers brand based on our designs
KEY QUESTIONS
What is the overall impression of the design?
How do users understand images and tone of voice?
Launch day!
In January 2023 we launched Northlandins.com, Travelers' commercial trucking subsidiary, built entirely from components curated for Travelers.com. The hero, quote module and 24/7 claims panel were the same parts, re-themed in Northland's blues and highway imagery. It looks like a trucking insurer, but underneath it runs on the same system.

The new Travelers.com launched on March 11, 2024, on the same foundation Northland had already proven in production. Personal insurance, business insurance and subsidiary sites now draw from one documented library, each in its own theme. Authors assemble pages from trusted blocks instead of starting a new project for every page.
