Alight Worklife Design System
Led the design system unifying brand and product across a global HR platform serving 36M+ users. Drove cross-functional alignment across Design, Product, and Engineering, establishing governance and workflows adopted across multiple product teams.
Supporting benefits experiences for 70% of the Fortune 100 required design infrastructure capable of scaling complexity, governance, and consistency across the platform.
Product Design Lead · Design System · Alight Solutions · 2020–2026
The challenge
Restructuring eliminated design specialties while the platform continued to scale, increasing risk of inconsistency and rework.
Approach
Established governance, fidelity decision frameworks, and structured intake processes that turned subjective design decisions into shared, enforceable standards.
Impact
40%
Reduced design rework by resolving fidelity decisions during intake rather than mid-project, shifting design from reactive execution to predictable delivery.
Context & Constraints
The design system operated inside a distributed product organization supporting multiple product lines. Operating within a Product-led organization, the team built governance and system infrastructure while navigating ongoing restructuring and shifting priorities.
Organizational Structure
- Design systems leadership reported into Product rather than a centralized Design organization
- Distributed team supporting multiple product lines across the platform
- Direct reports included specialized roles such as accessibility experts
- Long-term design partnerships across teams provided continuity and institutional knowledge
Timeline & Scope
- 5 years of active design system development
- Multiple concurrent initiatives: AWLDS interface, modal governance, fidelity frameworks
- Ongoing throughout organizational instability
Tools & Technology
- Figma for design and prototyping
- Jira for backlog and governance
- Storybook for component documentation
- ZeroHeight for design system documentation
💡 Key Learning
Operating without dedicated design leadership required governance artifacts that could defend themselves. Frameworks needed to work asynchronously, be shareable, and defensible without me in the room.
Research & Discovery
Audits and stakeholder interviews revealed several critical operational pain points.
Scope Creep
Product and Engineering frequently requested design polish mid-project without re-estimation
Inconsistent Expectations
Stakeholders couldn't distinguish between design fidelity levels or understand the associated effort
Modal Proliferation
Teams were creating modals and dialogs without considering interaction patterns or accessibility implications
Governance Gaps
No formal intake process meant design system requests bypassed refinement and went straight to backlog
🎯 Key Finding
60% of design rework stemmed from fidelity decisions made mid-project rather than during intake. Stakeholders viewed design polish as 'free' rather than understanding the complexity and time investment required.
Strategic Framework
Developed governance frameworks that made design complexity visible and defensible, anchored by a fidelity decision matrix mapping project needs to appropriate fidelity levels and effort.
1. Low Fidelity
Wireframes, basic layouts (2-4 hours)
2. Medium Fidelity
Styled mockups, basic interactions (8-16 hours)
3. High Fidelity
Polished UI, detailed interactions, animations (24-40+ hours)Formalized an intake process that clarified requirements before design system requests entered the backlog.
- Business impact justification with measurable goals
- Fidelity level selection with stakeholder approval
- Accessibility requirements identified upfront
- Complexity assessment and time estimate
🛡️ Governance Principle
Fidelity decisions are made during project intake and documented in the ticket. Any upgrade in fidelity mid-project is treated as a formal scope change requiring re-estimation.
Design System Architecture
Established a clear component hierarchy with defined tiers based on complexity and reusability.
Foundation
Design tokens, typography, color, spacing
Core Components
Buttons, inputs, basic layouts
Composite Components
Forms, data tables, navigation
Patterns
Complete workflows like login flows, dashboards
⚙️ Technical Decision
Built composite components from core primitives rather than creating standalone solutions. This reduced maintenance burden by 60% while increasing consistency.
Implementation & Adoption
Rollout Strategy
Phase 1
Foundation tokens and core components (3 months)
Foundation tokens and core components (3 months)
Phase 2
Governance frameworks and documentation (2 months)
Governance frameworks and documentation (2 months)
Phase 3
Complex patterns and adoption support (ongoing)
Complex patterns and adoption support (ongoing)
🤝 Collaboration Win
Office hours attendance dropped 40% after three months, because documentation improved enough that teams could self-serve.
Challenges & Tradeoffs
Challenge 1: Resistance to Governance
The Problem:
Product teams initially viewed intake frameworks as bureaucratic obstacles.
What Worked:
Framing governance as a way to protect everyone’s time. Product gained more predictable timelines, Design avoided unnecessary rework, and Engineering received clearer specifications. This required establishing intake as a prerequisite for design and engineering work, preventing unscoped requests from entering the backlog.
Challenge 2: Maintaining Quality During Restructuring
The Problem
Five years of organizational instability created constant context switching and loss of institutional knowledge.
What Worked
Creating asynchronous, standalone artifacts that teams could reference and apply without requiring my direct explanation.
🧠 Operational Insight
Design systems scale when governance and documentation allow teams to make consistent decisions without relying on the design system team.
Reflection
What I'd Do Differently
I would have implemented the intake framework in month 1 rather than year 2. The first year of ad-hoc requests created expectations that were painful to reset later — and the governance work would have been far easier before patterns calcified across teams.
Key Lessons
- Accessibility must be integrated early to ensure inclusive patterns scale
- Naming conventions should align with engineering to reduce friction
- Shared libraries create a common language that accelerates collaboration
Adopted across multiple product teams, establishing shared standards across a platform serving 36M+ users.
The system reduced design rework by 40% and increased design capacity by 35% over five years.
It shifted design from reactive execution to a governed, predictable system, where decisions were made upfront and aligned across teams.
The result was faster delivery, clearer expectations, and consistent outputs at scale.
In Partnership With
DESIGN
3 Designers
COPY
1 Writer
A11Y
2 Accessibility Experts
DEV
3 Engineers
He loves collaborating,
so go on. Reach out.
CONTACT
FOUNDER WORK
FOLLOW
© 2026 Russell Beaver. All rights reserved.