Scaling cross-product UX
with an accessible Design System

Scaling cross-product UX
with an accessible Design System

I was part of a cross-functional team responsible for maintaining and evolving a
Design System powering several large-scale products. The Design System is public, you check it here.

The challenge was to ensure consistency, accessibility, and scalability across multiple teams - while keeping up with new business requirements, technical constraints, and evolving accessibility standards.

Impact

Impact

Impact

  • Increased adoption of the Design System across teams (+34%)

  • Reduced design–development friction through clearer documentation and governance.

  • Improved accessibility compliance, leading to more inclusive and consistent product experiences.

My Role & Team

My Role & Team

My Role & Team

  • Product Owner

  • 2 Dev

  • 2 Product Designers (including me)

  • Accessibility Expert

Timeline

Timeline

Timeline

2024 - 2025

Challenge

Challenge

Challenge

Fragmented adoption

Users struggled with basic tasks. Important flows (e.g., IBAN updates) were buried, leading to frustration and unnecessary calls.

Teams used components inconsistently, creating inefficiencies.

Balance between flexibility and governance

Users struggled with basic tasks. Important flows (e.g., IBAN updates) were buried, leading to frustration and unnecessary calls.

Needed to empower innovation while maintaining cohesion.

Accessibility gaps

Users struggled with basic tasks. Important flows (e.g., IBAN updates) were buried, leading to frustration and unnecessary calls.

Some components lacked clear WCAG/ARIA guidance.

Discovery

Discovery

To identify pain points and opportunities, I ran a series of audits and workshops:

  • Surveys to assess adoption, pain points, and consistency issues.

  • Cross-team workshops to align needs between designers and developers.

  • Benchmarking against leading design systems (Atlassian, Shopify Polaris) for scalability and accessibility patterns.

Key insights:

Inconsistent components usage caused design debt.

Users struggled with basic tasks. Important flows (e.g., IBAN updates) were buried, leading to frustration and unnecessary calls.

Documentation lacked examples and accessibility notes.

Users struggled with basic tasks. Important flows (e.g., IBAN updates) were buried, leading to frustration and unnecessary calls.

Developers needed code snippets and update logs to stay aligned.

Users struggled with basic tasks. Important flows (e.g., IBAN updates) were buried, leading to frustration and unnecessary calls.

Design System Evolution

Design System Evolution

We transformed the system into a scalable, accessible, and developer-friendly framework. Key improvements included:

🧩 Design Tokens

For colors, typography, and spacing to ensure global consistency.

🪆Reorganized Libraries

Improved structure and naming for faster adoption.

👁️ Accessibility Docs

Added guidance and ARIA examples to every component.

🛠️ Version control and update logs

Ensured teams always worked with the latest updates.

Impact

35 → 69 %

adoption rate of the Design System across teams

Reduced design–development friction through clearer documentation and governance.

Improved accessibility compliance, leading to more inclusive and consistent product experiences.

Let's connect !

olgarogozhnikova@gmail.com

Copied!

© 2025 Olga Rogozhnikova. All Rights Reserved.

Let's connect !

olgarogozhnikova@gmail.com

Copied!

© 2025 Olga Rogozhnikova. All Rights Reserved.

Let's connect !

olgarogozhnikova@gmail.com

Copied!

© 2025 Olga Rogozhnikova. All Rights Reserved.

Create a free website with Framer, the website builder loved by startups, designers and agencies.