
SCALING DESIGN
CAPABILITY
THE CHALLENGE
When I joined Zoro, design was growing quickly but lacked the organizational structure needed to scale effectively. The team was primarily delivery-focused, with no dedicated research function, no design operations discipline, and no shared systems to support consistency, quality, or long-term efficiency.
As the product organization expanded:
-
UX maturity varied widely across teams
-
Research was ad hoc or absent
-
Design systems efforts had stalled due to unclear ownership
-
Accessibility was treated as reactive remediation rather than preventative practice
-
Designers lacked clear growth paths and leveling clarity
The organization needed to evolve design from a service function into a durable, multi-discipline capability.
ORGANIZATIONAL SYSTEMS IN PRACTICE
DESIGN APPROACH
I focused on building the foundational structure required to mature UX at scale, not just increasing headcount.
Key elements of the approach included:
1. Establishing New Design Specialties
-
Built Research and Design Operations as dedicated functions from the ground up
-
Defined ownership boundaries so design systems, tooling, and governance lived within Design Ops
-
Clarified how research, design, and product partnered across discovery and delivery
2. Maturing Design Operations
-
Centralized design system efforts under Design Ops to improve consistency and adoption
-
Introduced operating rhythms, reviews, and shared practices across teams
-
Established clearer intake, prioritization, and collaboration models
3. Developing Talent & Career Infrastructure
-
Created a design career path and skills matrix to support leveling, growth, and promotion
-
Clarified role expectations across IC and leadership tracks
-
Used the framework to guide hiring, feedback, and development conversations
4. Driving UX Maturity Intentionally
-
Set explicit team goals around improving UX maturity
-
Used internal personas, roadmaps, and team summits to align around shared vision and values
-
Framed accessibility and systems work as quality and risk mitigation, not compliance tasks
OUTCOMES
While I was at Zoro:
-
Research and Design Operations became established, embedded functions
-
Design systems gained clearer ownership and improved adoption
-
UX maturity increased across teams through shared practices and expectations
-
Designers had clearer growth paths and development frameworks
-
Design operated with greater consistency, leverage, and strategic influence
Design shifted from reactive delivery to a more mature, scalable organizational capability.
DECISIONS I INFLUENCED
-
Influenced the creation and structure of Research and Design Operations as dedicated design specialties
-
Defined where design systems ownership should live to support scale and governance
-
Established career frameworks to improve designer growth, retention, and leveling clarity
-
Shaped how UX maturity was measured, discussed, and prioritized across teams
-
Positioned accessibility and systems work as quality and risk mitigation investments







