Scaling Design Decisions Across a Fragmented Web Ecosystem
Company
Volkswagen
Accenture Song
Product
DesignOps
Year
2022
Role
Design Product Lead
As Lead Product Designer over eight months within a small DesignOps team, I established a scalable design operations framework for Volkswagen's fragmented web ecosystem, creating shared decision-making standards, cross-functional rituals, and design token infrastructure that unified +80 contributors across disciplines and regions without disrupting live, business-critical products.
Over 80 contributors across disciplines and regions worked independently on Volkswagen's web ecosystem — using different workflows, documentation sources, and decision-making processes. This led to duplicated efforts, inconsistent outputs, and growing friction between design and development teams.
Constraints
Live, business-critical web surfaces — any change carried production risk
Multiple design and product leaders with conflicting priorities
Legacy documentation and limited development capacity slowing adoption of shared standards
Risk
The challenge was not component design — it was designing how alignment and decisions could scale safely across 80+ people. Without a structured framework, every attempt at standardization risked either being ignored or breaking live products.
Approach
How to make DesignOps visible to distributed teams?
1.
Establishing cross-functional visibility and rituals
Before proposing any system change, I needed to understand where teams were actually struggling. I led a comprehensive audit of the existing ecosystem — foundations, UI libraries, and user guides — to identify gaps in documentation, consistency, and governance.
Based on that audit, I designed structured engagement channels: intake forms to capture component requests systematically, regular cross-functional syncs to reduce decision cycles, and feedback loops that surfaced blockers directly to leadership. The goal was shifting DesignOps from an invisible back-office function to a shared resource teams actively engaged with.
Key DesignOps improvements:
Intake form connected to team needs assessment (measuring request volume and pain points)
Regular cross-functional syncs connected to alignment velocity (reducing decision cycles)
This framework shifted teams from working in isolation to proactively engaging with DesignOps — requesting help, offering input, and participating in rituals without being asked.
How to implement standards without disrupting live products?
2.
Systemizing Decisions with design token infrastructure
Outcome & Impact
Faster Development Cycle
Design token adoption enabled smoother collaboration between design and code, reducing friction in handoffs and enabling teams to implement changes more confidently and consistently.
Component Scalability & Accessibility
The design token framework and DesignOps rituals established during this project became foundational infrastructure, supporting consistent experiences across Volkswagen's web ecosystem and enabling future scalability.
