All work

(Case Study)

Pharma Design Systems & Multi-Brand Architecture

Building digital governance across 15+ therapeutic brands.

Consumer care hub homepage — A new offer to help Americans save

The challenge

A major pharma organization's digital ecosystem had grown organically across more than 15 therapeutic brands. Each team had its own design language, its own information architecture, its own approach to regulatory review. The result wasn't a system. It was 15 systems pretending to be one.

The cost was real. Operational inefficiency. Inconsistent patient and HCP experiences. Compliance risk that varied brand by brand. A speed-to-market problem in therapeutic spaces where launch timing matters in millions of dollars. Resource waste across 60+ team members running concurrent projects without shared infrastructure.

The leadership team needed digital governance that could support a multi-billion dollar therapeutic portfolio without slowing the brand teams down.

The approach

I led the architecture and governance of three enterprise design systems, each serving a different audience and use case across the portfolio.

The work happened in three layers. The first was strategic — direct partnership with CTOs and senior business strategists on multi-million dollar digital initiative planning, including ROI documentation that could be reported to the board.

The second was architectural — defining the modular component logic, taxonomy, and content frameworks that would govern brand work across the portfolio. Each brand operates inside its own sandbox, working out particular content needs and creative expression within the governance framework. The system is intentionally restrained. Working with copywriters, medical strategists, and regulatory partners, I helped brand teams build information architecture that served both the system and the scientific story.

The third was operational — a governance training program shared with copy, design, and media partners. The training teaches the correct way to leverage the system, the tolerance to which it can be modified, and best practices for initial setup. The goal isn't compliance enforcement. It's knowledge sharing.

A specific innovation worth naming: I led the development of distribution channels for the Patient Design System, including a QR-based mobile wallet card for iOS and Android that gives patients fast access to co-pay information and medication support. It was an industry-first in pharma — only possible when the design system is built to support new patterns instead of resisting them.

Knowledge sharing, and helping people alleviate their fears about a new design system — instead of seeing it as a constraint, but as an opportunity to get to market faster and be creative within regulated design constraints.

Typographic scale documentation for the design system
Modular step component module documentation

Selected outcomes

$3.5M+ in digital transformation investment

Documented at the executive level across the portfolio — and the program continues to expand under new leadership.

Three design systems serving three audiences

One focused on DTC and unbranded work, one on HCP-facing unified content and resource repositories, and one focused specifically on patient support onboarding.

Industry-first mobile wallet integration

QR-based, FDA-compliant patient medication information deployed across iOS and Android for co-pay and patient support access.

Accelerated speed-to-market

Across product launches spanning day-one through 5-year study implementations.

Optimized vendor management

Across offshore and onshore development teams, reducing costs while maintaining brand consistency across 15+ brands.

Scalable infrastructure

Built to support future therapeutic area expansion and global market entry. Markets that don't use specific talking points can omit components without breaking the system. Time-to-market improves visibly.

Color palette and WCAG accessibility documentation
Vaccine content audit and scientific story strategy

What this means

A design system isn't a Figma library. It's organizational infrastructure. The version that survives — the version brand teams actually use five years later — is the one whose governance is as carefully designed as its components.

This engagement is that work. Less visible than a single product launch. More valuable.

Working through something similar?