Wale Design System (ADS4)

A scalable, governed design system that enables consistency, speed, and cross-team alignment across Acowale’s product ecosystem.

Organisation

Acowale

Timeline

3 Months

Date

Dec 1, 2023

— Nazar E Moin Sheikh,

Associate Product Designer

Constraints:

The design system needed to support multiple live products with active users, legacy UI patterns, and parallel feature development. It had to balance flexibility for diverse product needs while enforcing consistency, accessibility, and visual coherence across teams. The system also needed to align with existing engineering constraints and codebases—without slowing down delivery or experimentation.

“Designed and scaled a governed design system to improve consistency, design velocity, and collaboration across Acowale teams.”

As Acowale’s product suite scaled, design decisions became increasingly fragmented across teams. Similar components were rebuilt repeatedly, visual styles drifted between features, and design-to-development handoff lacked a shared standard. New designers faced a steep onboarding curve, while engineers had to interpret inconsistent designs across flows. This resulted in slower execution, avoidable rework, and growing difficulty maintaining a cohesive experience across products.

Earlier versions of the system were either incomplete or too loosely governed, which limited adoption across teams. ADS4 was created as a more structured and scalable iteration—designed to act as a single source of truth while still allowing teams to adapt components to real product needs.

Goals

- Establish a single source of truth for design across Acowale products - Reduce repeated design effort and experience inconsistencies - Improve collaboration between design and engineering - Enable faster feature delivery without sacrificing quality - Make onboarding easier for new designers and contributors

Creative сhallenges

The biggest challenge was designing a system that could scale across multiple products without becoming overly rigid. Too much flexibility risked inconsistency, while too much control slowed teams down. Another challenge was aligning existing UI patterns into a cohesive system—without breaking live products or disrupting ongoing development.

Solution

The system was designed to be intuitive for everyday use. Components were documented with clear usage guidelines, states, and examples to reduce ambiguity during design and handoff. By prioritizing ease of adoption, the system encouraged consistent usage across teams—rather than becoming a theoretical reference that designers avoided.

Solution Journey

Outcome

1. Faster design execution due to reusable, well-documented components 2. Improved consistency across multiple Acowale products 3. Reduced design and engineering rework 4. Easier onboarding for new designers 5. Stronger alignment between design, product, and engineering teams

Contact

Let’s connect

Interested in working together or discussing an opportunity? Reach out, I’d love to chat.

Nazar e Moin Sheikh

Product Designer