Brianne beatty

Brianne beatty

case study

systems design

Designing a Shared Interaction Language

Designing a Shared Interaction Language

As our product ecosystem grew, each team defined interactions differently. Users had to relearn patterns in every product, while teams duplicated work to solve the same problems.


We created a shared interaction language so products can look unique while always feeling familiar.

NDA protected - portfolio version

role

Product Designer

team

Design, Engineering, QA, Product

Design, Engineering, QA, Product

duration

4 weeks

platform

Web Application (Legacy System)

Web Application

(Legacy System)

disciplines

Systems

Accessibility

Interaction Design

NDA note

Product names, branding, and interface details have been anonymized. Visual examples are representative recreations, while the process, challenges, interaction framework, and design decisions accurately reflect the work.

01

The problem

Every product taught users different rules.

As products evolved independently, interaction states became fragmented. Users could not rely on visual cues to understand what was interactive, and teams repeatedly solved the same problems in different ways.

CHALLENGE

DETAILS

IMPACT

Inconsistent Interaction States

CHALLENGE

Inconsistent Interaction States

Each product defined clickability differently.

DETAILS

Each product defined clickability differently.

Users had to relearn interaction patterns.

IMPACT

Users had to relearn interaction patterns.

Accessibility Risks

CHALLENGE

Accessibility Risks

Focus and disabled states varied.

DETAILS

Focus and disabled states varied.

Accessibility quality was inconsistent.

IMPACT

Accessibility quality was inconsistent.

Duplicated Implementation

CHALLENGE

Duplicated Implementation

Teams rebuilt similar solutions.

DETAILS

Teams rebuilt similar solutions.

Slower delivery and increased maintenance.

IMPACT

Slower delivery and increased maintenance.

Palette Conflicts

CHALLENGE

Palette Conflicts

Visual identities diverged over time.

DETAILS

Visual identities diverged over time.

Consistency became harder to maintain.

IMPACT

Consistency became harder to maintain.

Before:

As products adopted custom artwork and palettes, clickability became harder to recognize consistently.


Similar interactions looked and behaved differently across products, creating inconsistent expectations for users.

Before:

As products adopted custom artwork and palettes, clickability became harder to recognize consistently.


Similar interactions looked and behaved differently across products, creating inconsistent expectations for users.

default

default

hover

hover

pressed

pressed

selected

selected

inactive

inactive

Multiple Products. Multiple Definitions of Clickable.

Users had to relearn interaction patterns while teams repleatedly rebuilt the same behaviors

Multiple Products.

Multiple Definitions of Clickable.


Users had to relearn interaction patterns while teams repeatedly rebuilt the same behaviors

02

process

Creating consistency without sacrificing identity.

The challenge wasn't visual consistency, it was behavioral consistency. Products needed the freedom to express their own brands while giving users a predictable interaction experience across the ecosystem.

01

Audit

Analyzed existing interactions across products to identify inconsistencies.

02

Align

Defined a shared set of states and behaviors that work everywhere.

03

Standardize

Built components and guidelines to ensure consistent behavior.

04

Validate

Tested across products for accessibility, usability, and technical feasibility.

05

Scale

Enabled adoption with templates, tokens, and ongoing governance.

03

the solution

One interaction model. Any palette.

We defined universal interaction states by consolidating familiar patterns into a shared system grounded in behavior, hierarchy, and accessibility. This created a consistent foundation without requiring users to relearn interactions.

Shared States

Shared interaction states behave consistently across products and content types.

Flexible Expression

Visual identity adapts while interaction behavior remains consistent.

Accessibility by Default

Accessibility requirements are built into every state by default.

Accessibility by Default

Accessibility requirements are built into every state by default.

Scalable Foundation

New products inherit the system without redefining interaction behavior.

Same behavior. Different expression.

default

default

hover

hover

pressed

pressed

selected

selected

inactive

inactive

TOP LAYER (ADAPTS):

Color, iconography, and artwork adapt to each product's brand and context.

FOUNDATION LAYER (STAYS CONSISTENT):

Shape, size, elevation, focus, and state behavior provide a familiar, accessible experience.

04

in practice

A flexible system that respects identity.

Products maintain their own identity while interaction patterns remain familiar.

Bright Palette

default

hover

pressed

selected

inactive

Balanced Palette

default

hover

pressed

selected

inactive

Muted Palette

default

hover

pressed

selected

inactive

The palette changes. The interaction language does not.

05

Outcome

Consistency without compromise.

By separating interaction behavior from visual expression, we created a system that scales across products while preserving the unique identities users already recognized and trusted.

Clarity

Users could more easily recognize clickable content across products.

Consistency

Shared interaction states created predictable experiences regardless of palette or artwork.

Scalability

New products could adopt the system without redefining interaction behavior.

© Brianne Beatty 2026

© Brianne Beatty 2026