As eazle grew, we added more markets, more teams, and more complexity. Designers were embedded in product team, each running on their own timeline with their own priorities. Without a shared structure, we risked falling into fragmented patterns — inconsistent UX, duplicated components, and siloed thinking. We weren’t short on talent. But we lacked a system to keep quality, coherence, and collaboration high — without turning everything into bureaucracy. The real challenge was designing the design process: giving designers the autonomy to solve meaningful problems without compromising on alignment, craft, or velocity.

I started by getting the structure right. I reorganized the team into product-aligned teams with embedded researchers, but introduced shared rituals that cut across team lines: weekly critiques, bi-weekly product reviews, and monthly showcases. These weren’t just ceremonies — they were calibration points. I pushed for vertical ownership (designers owning key flows end to end), while reinforcing horizontal alignment through common experience tenets and regular cross-team reviews. I also tightened the loop between the design team and the design system team. I didn’t own the system directly, but I made sure the right conversations were happening — connecting designers with the system team early so new needs and patterns flowed both ways. In 1:1s and team sessions, I coached toward better decision-making, not just better visuals. The focus: context, clarity, and impact. Why this? Why now? How does it scale?

We maintained a high level of design consistency and product quality across a growing platform — with multiple teams working in parallel. Designers moved faster, duplicated work dropped, and the UX started feeling coherent across the product. Our rituals created more feedback earlier in the process. Instead of polishing screens in isolation, designers shared in-progress thinking and pushed each other. That made the work better — and built trust across the team. The connection to the design system also became healthier. Designers started proposing system updates instead of hacking around them. And when new patterns emerged, they were built in ways that scaled across markets and flows.

The biggest shift wasn’t visual — it was cultural. Designers stopped asking, “What should this look like?” and started asking, “What’s the right way to solve this here?” They understood the product context better. They challenged product decisions with data and rationale. They started to lead.

Scaling design isn’t about standardizing everything — it’s about creating the right constraints, the right rhythms, and the right conversations. When teams are aligned on principles and connected through structure, quality becomes a byproduct. Not a bottleneck.