My Role

I led the design of Spark’s documentation platform, defining its structure, interaction model, and content system to ensure teams could quickly find and apply guidance. Key contributions included:

• Designing scalable page templates for foundations, components, and implementation

• Establishing consistent patterns for usage, accessibility, and code examples

• Creating a documentation framework that enabled designer contribution and engineering consumption

I also partnered with UX Research to evaluate effectiveness and iterate based on company-wide feedback.

Platform Design

The platform is a fully responsive, centralized site that brings together:

• Foundations (type, color, layout, spacing, motion)

• 200+ components with variations and usage guidance

• Implementation support across HTML, CSS, JS, and React

Each component includes accessibility considerations and code examples, enabling teams to move from design to production with clarity and consistency.

The platform also supports theming, shared resources, and scalable templates, allowing it to adapt across diverse product ecosystems—even where legacy constraints limit direct code reuse.

Adoption & Enablement

To drive adoption, I focused on reducing friction and enabling teams to learn and implement the system independently.

I developed a comprehensive training program covering system principles, component usage, and implementation. In partnership with engineering, this became a self-serve onboarding experience that reduced training time by 88% (4 hours to 30 minutes) and eliminated the need for recurring live sessions.

The platform also provided:

• Figma libraries and shared design assets

• Implementation guidance and versioning support

• Page templates for common workflows

• A curated product showcase highlighting strong implementations

In a later iteration of the homepage, I introduced adoption metrics to make impact visible and encourage broader adoption across teams, including system usage and product coverage.

Impact

The platform became the central hub for Spark and was adopted across all product teams in the organization.

A company-wide survey showed 80%+ satisfaction among designers, product managers, and engineers. Lower scores were primarily tied to teams with legacy constraints, rather than gaps in the system itself. By enabling self-serve learning and providing a clear, centralized source of truth, the platform:

• Reduced onboarding friction

• Increased consistency across products

• Scaled adoption of the design system across the organization

Context

Spark was designed to support multiple enterprise products across different technology stacks. Because it was intentionally framework-agnostic, a traditional component library alone wasn’t sufficient.

Teams needed a centralized platform to access system guidance independent of implementation technology, especially at a time when design tools lacked built-in documentation capabilities.