Charles Augello

HomeCase studiesDesign system

Designing and building an enterprise design system

Product teams kept reinventing the same UI patterns, which slowed delivery and raised usability and compliance risk. I helped establish a shared, accessible system that made speed safe and repeatable.

Role
Senior UX Lead / Design System Contributor
Timebox
Incremental delivery over multiple sprints; initial decision-ready system in 14 business days
Environment
Regulated enterprise with multiple product teams and inconsistent UI patterns
Standards
WCAG 2.1 AA and regulatory guidelines
Outputs
Enterprise UI components, accessibility-compliant patterns, usage guidelines, scale-ready documentation
30%less design and development rework
14 daysto an initial decision-ready system
Fewerreview cycles through standardized accessible patterns

The decision to enable

Product and engineering teams were repeatedly reinventing UI patterns, slowing delivery and increasing usability and compliance risk. Leadership needed to decide whether to invest in a shared design system to accelerate delivery without compromising regulatory requirements.

Key decision: Can a standardized, accessible design system materially increase delivery speed and consistency across teams?

Rapid insight and opportunity identification

I partnered with product, engineering, and marketing stakeholders to assess existing UI fragmentation. Through heuristic reviews, pattern inventories, and analysis of delivery bottlenecks, we identified high-impact components that teams repeatedly rebuilt.

Within the first week, we prioritized a focused set of foundational components that would deliver the greatest speed and risk-reduction benefits.

System design and prototyping

In close collaboration with engineers, I co-created reusable UI components designed for both design and development efficiency:

  • Componentized layouts and controls
  • Variants supporting multiple states and contexts
  • Built-in accessibility considerations (contrast, focus, keyboard behavior)

Prototypes were validated with product teams and engineers to confirm usability, feasibility, and adoption readiness.

Accessibility and compliance by default

Accessibility was a non-negotiable requirement. Each component was designed and reviewed against WCAG standards and regulatory guidelines. Clear usage guidance helped teams apply components correctly without additional review cycles.

By embedding accessibility into the system, teams could move faster while reducing compliance risk.

Enablement and adoption

To ensure adoption, I focused on enablement as much as design:

  • Created clear documentation and usage guidelines
  • Partnered with engineers on implementation standards
  • Facilitated walkthroughs and working sessions with product teams
  • Mentored designers and developers on system usage

This approach reduced friction and encouraged consistent use across teams.

Outcomes and impact

  • Reduced design and development rework by 30%
  • Accelerated prototyping and delivery cycles across multiple teams
  • Improved consistency and usability across customer-facing platforms
  • Reduced review effort by standardizing accessible patterns
  • Established a foundation for future system expansion

Scale readiness

The system was intentionally designed to scale:

  • Modular components extendable by future teams
  • Clear governance and contribution guidelines
  • Documentation supporting onboarding and reuse

These practices allowed new teams to move quickly without sacrificing quality.

Reflection: AI-first evolution

Today, I would further enhance the system by:

  • Using AI to detect pattern drift and inconsistencies
  • Accelerating component creation through AI-assisted variants
  • Generating real-time usage insights to guide system evolution

The principle remains unchanged: systems exist to make speed safe and repeatable.

Building or fixing a design system in a regulated space?

Email me