Lessons from Growing a Platform Org 3X
Scaling a design team is not like scaling engineering. You cannot just subdivide the problem, add people, and watch throughput increase. Design teams face a different kind of complexity: the more designers you add, the harder it becomes to maintain a coherent vision and a consistent user experience. The complexity doesn't grow linearly. It compounds.
Over the past three years, I grew our platform design organization from 10 to 30 designers. That growth was driven by real pressure: a company expanding quickly and a product becoming genuinely complex. But adding headcount was, honestly, the easy part.
The harder work was building the structural and cultural foundations that would let a larger team operate without sacrificing quality or speed. What I learned in the process wasn't just about hiring. It was about building systems that scale alongside your people. Systems that empower instead of constrain, that give guidance without dictating, and that can evolve as the organization matures.
The Foundation: A Hybrid Model Built for Scale
Early in our scaling journey, I recognized that neither a purely centralized nor a fully embedded design model would work. Centralized teams become disconnected from the day-to-day rhythm of product development. Fully embedded designers drift away from cross-product consistency and shared vision. Both extremes create real costs.
The answer was a hybrid model that has proven remarkably well suited for platform organizations: designers embedded within cross functional product teams, supported by a layer of design leadership that spans across those teams.
Each designer works closely with a product manager to solve problems daily. That relationship is consultative, not hierarchical. The designer brings expertise to help frame the problem space and explore solutions. The PM owns product decisions. In parallel, each designer is guided by a design lead who may not be their direct manager but serves as the design authority for that product area. The design lead maintains quality standards, supports professional growth, and holds coherence across the broader platform experience.
This structure delivers three things that matter at scale. It keeps designers close to their product counterparts, so design has a voice early rather than arriving late to validate decisions that have already been made. It creates natural communities of practice through the design leads, preserving shared standards and organizational learning. And it offers designers a visible career path, whether they want to deepen their craft or move toward leadership.
I've heard the concern that hybrid models dilute design quality or create confused accountability. Our experience has been the opposite. By defining decision rights clearly and building regular coordination between leadership layers, we've actually strengthened accountability while giving designers the right support at the right moment.
Cultural Scaling: Intentional Evolution, Not Preservation
When your team triples in size, you cannot simply preserve your existing culture. What worked for 10 people breaks at 30. The goal isn't to keep the culture intact. It's to evolve it with intention.
At one point I looked around and realized that 70 percent of our designers had been with the company for less than a year. You cannot rely on osmosis or informal mentorship to transmit your values at that scale. That realization led to a structured onboarding program specifically for designers, one we are still actively improving. We rely heavily on feedback from designers who have just gone through it, because their perspective reveals blind spots that are invisible to people who've been here for years.
Rather than orienting new designers around tools and processes, we built the program around three principles: user advocacy, business understanding, and collaborative problem solving. We're expanding beyond shadowing into activities that demonstrate those principles in practice. Every new designer conducting user interviews within their first month. Every new designer collaborating with their PM on a business value assessment. Every new designer participating in cross team design critiques before they've shipped anything.
Our design review process also had to change. Full team critiques don't work when your team is 30 people. We moved to a rotating schedule where projects get focused, substantive attention from a smaller and deliberately diverse group. Quality stays high. People's time is respected.
The biggest cultural lever, though, was scaling my layer of design leadership. I depend on these leaders not just for quality, but for extending design's influence across the organization. I've invested in their growth through stakeholder management training, executive exposure, and business acumen development. In return, they've become trusted advisors to their product counterparts. They've shifted design conversations from visual execution to strategic direction. Without them, none of the rest of this would hold together, regardless of how many individual contributors we added.
Process Evolution: Getting Upstream
As the organization grew, the most important process change wasn't about how we ran design reviews or managed files. It was about when design shows up in the product development cycle.
We've been deliberately moving upstream, introducing design earlier in solution definition. That shift changes what designers can actually do. When you're upstream, you help shape requirements. When you arrive downstream, you execute against decisions that were already made without you.
A critical part of this shift has been elevating our Design Leads to become genuine members of the leadership team for every product in our platform ecosystem. These leaders ensure design is considered from day one, not retrofitted at the end. They represent user needs and experience coherence in rooms where product direction is being set.
The result has been a move from reactive execution to proactive influence. That's not a subtle difference. It changes how design contributes to outcomes, and it changes how the rest of the organization understands what design is for.
Aligning With Business Objectives
A design organization that scales successfully has to demonstrate clear business impact. That's non-negotiable at any size, but it becomes harder to ignore as you grow.
We introduced individual goals for every designer aligned to broader company objectives. The intent was simple: every person on the team should be able to articulate how their work connects to what the organization is trying to accomplish. Not in abstract terms, but specifically. We're preparing a second iteration of this process with our Design Leads involved from the beginning, which will sharpen our focus and give each designer greater clarity about their contribution.
I'm currently exploring measurement frameworks to strengthen this alignment further. The Google HEART framework, Happiness, Engagement, Adoption, Retention, and Task success, offers a useful structure, and I'm working with my design leadership team on how to map each design initiative to specific business metrics. The goal is a shared language between design, product, and executive leadership so we're having conversations about outcomes rather than preferences.
We're also considering quarterly reviews where teams present not just the work but its measurable impact on business results. That changes the nature of the conversation entirely.
One thing I've learned: the way you frame your work matters as much as the work itself. When we present design outcomes as business wins rather than design improvements, we earn different kinds of support. That framing has already helped us secure additional research resources and has started to shift how design is perceived, from a service function that produces deliverables to a strategic driver of value.
The One Lesson That Stays
Scaling a design team well requires equal attention to structure, culture, process, and business alignment. Any single one of those in isolation is not enough.
But if I had to distill it to one lesson, it's this: design your organization for where you're going, not where you've been.
Too many design leaders build structures around their current team's strengths. That approach breaks as you scale, and the reorganization that follows is painful. A better approach is to design the organization you'll need two years from now, then grow your people into it. That forward orientation has let us scale without the typical growing pains, because the structure was ready before the pressure arrived.
The true measure of a design organization isn't its size. It's its impact on the people who use what you build, and on the business that depends on those people coming back. Focus on that impact and the rest of the decisions become easier.