Emily Giordano

MetLife

Build a shared design foundation for MetLife

I helped build and maintain MetLife’s global design system for teams across more than 50 markets. My work covered reusable components, visual standards, documentation, and reviews with developers and QA, translating design guidance into things teams could use.

One foundation for more than 50 markets

Shared components and guidance gave teams a consistent starting point across products, platforms, and markets.

A shared system saves teams from solving the same problem twice

After the team’s work with R/GA on the rebrand, I helped translate the recommendations into reusable components and practical guidance on Design.metlife.com.

A brief overview

A component is not finished until it works in code

I reviewed responsive components with developers and QA, checking the implementation against the rebrand’s standards. Those conversations connected design intent to the behavior and details people would actually use.

Document the choices teams need to make

I documented component features, variations, and live HTML demos. Teams could inspect how a component worked and when to use it, rather than reconstruct intent from a static mockup. Documentation and handoff were part of the product.

First look

Expand details

Make the visual rules reusable

I refined guidance for logos, typography, color, illustration, icons, and photography within the shared system. These standards gave product teams a common starting point while they worked on different platforms and market needs.

Treat icons as shared language

I helped align the icon library with the system’s visual standards. Consistent iconography made the foundation easier to reuse across products, rather than leaving teams to invent different symbols for the same idea.

What I learned

Adoption is the real output

A library has value only when teams can find, trust, and use it.

Documentation is product work

Clear guidance can prevent as much downstream rework as the component itself.

Consistency needs governance, not rigidity

A global baseline should create coherence while allowing for platform and market differences.

More projects

1 to 4 of 6

Generate Music in Premiere: an audio clip with prompt, Tempo, Loop, and variation controls.

Adobe · Generative AI

Create music that fits your scene

Create music that fits your scene with clear, editable generation controls.

Generate Soundscape in Premiere: video with four separate editable audio layers.

Adobe · Generative AI

Bring silent footage to life

Turn visible action into editable layers of ambience and sound effects.

Zipcar

Make late returns less painful

Help members report delays and recover when their car is late.

Zipcar

Evolve memberships to meet drivers’ needs

Introduce Zipcar’s first tiers for occasional and frequent drivers.

Zipcar

Keep payments moving with a flexible wallet

Make payment choice, backup charging, and recovery clear across app and web.

Zipcar

Paying overdue balances in app

Help members resolve an overdue balance directly in the app.

Emily Giordano

MetLife

Build a shared design foundation for MetLife

I helped build and maintain MetLife’s global design system for teams across more than 50 markets. My work covered reusable components, visual standards, documentation, and reviews with developers and QA, translating design guidance into things teams could use.

One foundation for more than 50 markets

Shared components and guidance gave teams a consistent starting point across products, platforms, and markets.

A shared system saves teams from solving the same problem twice

After the team’s work with R/GA on the rebrand, I helped translate the recommendations into reusable components and practical guidance on Design.metlife.com.

A brief overview

A component is not finished until it works in code

I reviewed responsive components with developers and QA, checking the implementation against the rebrand’s standards. Those conversations connected design intent to the behavior and details people would actually use.

Document the choices teams need to make

I documented component features, variations, and live HTML demos. Teams could inspect how a component worked and when to use it, rather than reconstruct intent from a static mockup. Documentation and handoff were part of the product.

First look

Expand details

Make the visual rules reusable

I refined guidance for logos, typography, color, illustration, icons, and photography within the shared system. These standards gave product teams a common starting point while they worked on different platforms and market needs.

Treat icons as shared language

I helped align the icon library with the system’s visual standards. Consistent iconography made the foundation easier to reuse across products, rather than leaving teams to invent different symbols for the same idea.