Progressive Purpose

A case study on the design process used to create a dynamic web experience for Progressive’s purpose statement and the stories that support it.

Video Block
Double-click here to add a video by URL or embed code. Learn more

ROLES / Site mapping, prototyping, building tokens and components within Figma, partnering with developers

Brief

Progressive has had an incredible history of helping people, but had yet to compile all the great stories into one single destination. The goal of the Purpose site is to create a unique experience to share all these stories through captivating imagery, video and written text. The experience needed to be housed on the main Progressive brand website, but present itself with a distinctive visual identity that stands out on its own.

Site Map

The experience needed to be merged into the existing Progressive website, but new pages needed to be created to house the various content. Some of these pages included the homepage, campaign pages, program pages and stories.

Iteration

Since the Purpose site was being built into an existing platform, content modules within the prototypes needed to be derived from what already existed in the pattern library, but would later be modified to meet the needs of the Purpose brand. Early iterations followed existing module patterns and wireframing was bypassed because of this.

Visual Identity

To drive the identity of the site, a set of guiding principles were defined prior to design. These guiding principles were: show authentic humanity, be unapologetically bold, convey powerful expression, move from transactional to engaging, and use copy to convey action. These principles became the backbone to all design, photography and written language within the experience.

Black full bleed modules and a bold and expanded all-caps font were as well as candid in-action photography were used to convey these principles and stand out from the rest of the pages on the site.

UI Kit

I was tasked with creating a UI kit in Figma to enforce consistency among the components being used in the prototype, which showed the relationships between mobile and desktop components as well as component variants. This also became the source for developers to base their code.