A design system for 80 contributors that had to scale and stick

Volkswagen

·

2025

Overview

Situation

I led DesignOps for Volkswagen's web ecosystem over 8 months, within a small team at Accenture Song.

Situation

I led DesignOps for Volkswagen's web ecosystem over 8 months, within a small team at Accenture Song.

Problem

80+ contributors across regions had built working products, but each team had developed its own standards and documentation over time. The result: duplicated effort and growing inconsistency across the ecosystem.

Problem

80+ contributors across regions had built working products, but each team had developed its own standards and documentation over time. The result: duplicated effort and growing inconsistency across the ecosystem.

Challenge

Live products couldn't break during any transition. Multiple leaders had different priorities, and existing documentation had grown organically without a shared structure.

Challenge

Live products couldn't break during any transition. Multiple leaders had different priorities, and existing documentation had grown organically without a shared structure.

Disciplines

DesignOps strategy Design systems Cross-functional facilitation Component documentation

Disciplines

DesignOps strategy Design systems Cross-functional facilitation Component documentation

Impact

500+ components migrated to tokens, reducing inconsistencies and shortening design-to-code cycles. DS adoption grew and onboarding got faster across teams.

Impact

500+ components migrated to tokens, reducing inconsistencies and shortening design-to-code cycles. DS adoption grew and onboarding got faster across teams.

Overview

Process

Outcome

View Process

Approach

Adoption over authority: making standards stick without forcing them

I set up weekly design system syncs and built feedback channels directly into Figma. Intake forms replaced ad-hoc Slack requests. Blockers surfaced to leadership through structured loops instead of getting lost in threads.

The result: DesignOps went from a back-office function to something teams actively used.

Systemizing Decisions with design token infrastructure

I built a token system covering color, typography, spacing, and elevation, all mapped to VW brand guidelines. Each value went from raw hex to semantic name to usage token, so teams could apply consistent styles without memorizing values.

Component documentation

I refactored 500+ components with token variants, auto-layout, and accessibility states. Each component got structured docs: purpose, anatomy, states, usage guidelines. Teams adopted new versions on their own timeline, no forced migration.

Outcome

Key results

  • Less inconsistency across the ecosystem: tokens replaced hardcoded values across 500+ components, reducing duplicated effort between teams

  • Shorter design-to-code cycles: developers pulled token values directly from the system instead of interpreting specs

  • Higher DS adoption, measured by fewer detached or custom-made components across regional projects

  • Faster onboarding: structured documentation and intake forms reduced unmonitored requests from new contributors

  • Cross-functional syncs aligned leaders with different priorities on shared decisions, surfacing blockers earlier

Back to Home

Ivan Bonin

©2026

Ivan Bonin

©2026

Ivan Bonin

©2026