Company: Wunder Mobility
Duration: 3 months (2025)
Role: Product Designer & Design Strategy
Team: 3 people (myself + 2 frontend developers)
Wunder Mobility operates shared mobility services across 150+ cities, managing multiple product lines: B2B fleet management dashboards, white-label consumer apps for different markets, and internal operations tools. As the company scaled rapidly, our design and development processes became chaotic.
The core problem was fragmentation. We had 40+ variations of basic components like buttons across products, six different CSS frameworks in use, and no shared design language. Developers were rebuilding the same components repeatedly, designers were recreating similar patterns for each new market, and our brand experience was inconsistent across touchpoints. Simple design updates took days to implement, and launching in new markets required weeks of custom development work.
As Senior Product Designer & Design Strategy Lead, I led the creation of WuCraft - a comprehensive design system to unify our product ecosystem. Working with two frontend developers, I took a strategic approach: establish a shared design-development vocabulary, create reusable component standards, and build documentation that serves as both design guide and technical reference. My focus was solving organizational problems, not just creating beautiful components.
1. Discovery & Audit I conducted a comprehensive audit of existing components across all products, cataloging every button, form field, and UI pattern we were using. Through team interviews, I identified the biggest friction points: designers and developers were speaking different languages, handoffs were painful, and there was no single source of truth for design decisions.
2. Foundation Building Established the core design language: color palettes with semantic naming, typography scales, spacing systems using an 8pt grid, and interaction patterns. The key innovation was creating naming conventions that worked for both design tools and code, reducing the translation layer between design and development.
3. Component Development Working closely with our two developers, we built the essential component library starting with the most frequently used elements: buttons, form inputs, cards, and navigation components. Each component included multiple variants but maintained consistency in behavior and appearance. We piloted the system with our main dashboard product to test real-world usage.
4. Documentation & Rollout Created comprehensive documentation that served as both design guide and developer reference. Rather than forcing adoption, we demonstrated value through improved velocity and consistency. Conducted training sessions and provided ongoing support as teams adopted the system across different products.
