Scaling Design Across 10+ Teams
The Head of Design asked me to mature design processes for 80+ designers across 10+ teams.
MY ROLE
Head of Design, Jetpack
OUTCOME
Practical roadmap
THE SHORT VERSION
A shared operating model for 10+ teams: aligned planning, clearer expectations, and practices that could scale.
Four moves
01
The gap
80+ DESIGNERS
+
PROBLEM
Design teams were using different engineering processes. Communication was siloed, and the same work was getting done twice.
DECISION
The Head of Design asked me to mature design processes across 80+ designers and 10+ teams.
RESULT
A shared operating model: aligned planning, clearer expectations, and practices that could scale.
02
Interviews
WHAT WAS WORKING
+
03
Workshops
RESPECT THE TEAMS
+
04
What happened
NO IMPACT NUMBERS
+
Scaling Design Across 10+ Teams

Company
WordPress | Automattic
Role
Head of Design Jetpack| Principal
Focus
Add focus
Scaling Design Across 10+ Teams

Company
WordPress | Automattic
Role
Head of Design Jetpack| Principal
Focus
Add focus
The problem
Lack of alignment across design teams working with different engineering processes.
Siloed communication between design teams across the org and between design and engineering in some teams.
Duplicative efforts due to a lack of consistency in workflows, highlighting the need for better alignment.
Approach
stakeholder interviews
Conducted in-depth interviews with design team members and team leads to understand their existing workflows, challenges, and needs.
Gathered insights on what was working well and what wasnโt.
collaborative ideation
Facilitated workshops to co-create potential solutions that could align processes while respecting team-specific needs
analysis
Categorized tasks into tiers to standardize expectations for design efforts (e.g., simple changes, component redesigns, complex feature development).
Identified frameworks such as decision matrices and prioritized collaboration points for design and engineering teams.
Outcomes and takaways
OUTCOMES
This initiative was delayed due to critical projects across the organization. While I do not have solid numbers to speak to its impact, I can offer some insight.
The audit examined:
Teams and leads reported feeling heard and valued during the process.
Leadership expressed satisfaction with the inclusive approach.
I set the foundation for sustainable, team-driven process improvements.
key takeaways
This project highlights my inclusive problem-solving approach, emphasizing the following:
Understanding and integrating diverse team needs.
A focus on action-oriented, applicable plans over documentation for documentationโs sake.
Co-creating solutions for alignment without rigidity.
Championing team ownership of processes for long-term success.
Outcomes and takaways
OUTCOMES
Through an inclusive audit and engagement process, I developed a practical, iterative roadmap for aligning core design components across functions, products, and teams without disrupting active product development. Seeded shared planning and prioritization practices across an 80+ person design organization and created the roadmap for broader adoption.
I also led lunch-and-learns on Jetpackโs work-management practices, including the design board, prioritization model, and team workflows I had introduced. These practices were adopted beyond Jetpack, creating greater consistency in how design teams planned, managed, and delivered their day-to-day work.
Established an incremental path toward a shared, componentized design system.
Extended successful Jetpack practices across the wider design organization.
Helped teams adopt clearer work-management and prioritization practices.
Created a foundation for sustainable, team-driven process improvements.
key PHILOSOPHIES
Start by understanding the different needs, constraints, and working styles across teams.
Favor practical, actionable plans over documentation that does not lead to change.
Co-create solutions with the people who will use them, creating alignment without imposing unnecessary rigidity.
Build team ownership into the process so improvements can continue without depending on a single person.
