What Design Leaders Wish They Knew Before Scaling Their First Service Design Project

Scaling your first service design project feels like stepping into uncharted territory. Even seasoned UX professionals find themselves surprised by the unique challenges that emerge when moving from small, scrappy teams to structured, multi-departmental initiatives.

After talking with design leaders across government agencies, fintech startups, and educational institutions, a clear pattern emerges: the lessons that matter most aren't about design tools or methodologies: they're about people, politics, and persistence.

Your First Hire Sets the Tone for Everything

"Your legacy is the people you hire," says Aarron Walter, former VP of Design Experience at InVision. This wisdom hits different when you're scaling service design because you're not just building a team: you're building a culture that needs to work across departments.

The mistake many leaders make? Hiring for specific skills instead of hiring people who can adapt and grow. When you're scaling service design, you need team members who can navigate ambiguity, communicate with non-designers, and stay curious when faced with complex organizational challenges.

Sarah Chen, who led service design scaling at a major fintech company, puts it bluntly: "I hired a brilliant researcher who couldn't explain their findings to our product managers. All that insight sat on a shelf. Now I hire for communication first, skills second."

The practical takeaway? During interviews, ask candidates to explain a complex design decision to someone without a design background. Their ability to simplify and connect will matter more than their Figma proficiency.

Stakeholder Buy-in Isn't a One-Time Achievement

Here's what every design leader learns the hard way: getting initial approval for your service design project is just the beginning. Maintaining support throughout the scaling process requires continuous effort.

"Bad things happen when people feel left out," notes design strategist Mike Monteiro. This is especially true in service design, where your work touches multiple departments and impacts various user touchpoints.

The most successful leaders we spoke with implement what they call "stakeholder maintenance": regular check-ins, design reviews, and progress updates that keep everyone informed and invested. It's not about seeking permission for every decision; it's about preventing surprises that can derail months of work.

Marcus Rivera, who scaled service design across three government departments, shared his approach: "Every two weeks, I send a 3-minute update video to all stakeholders. It shows current work, upcoming decisions, and how their feedback shaped our direction. It's more work upfront, but it's saved us from getting blindsided by changing priorities."

Structure Emerges From Pain Points, Not Planning

Small teams can operate on Slack messages and coffee conversations. Growing teams can't. The challenge is knowing when to add structure without killing the collaborative spirit that made your initial work successful.

The leaders who scale successfully don't try to predict what structure they'll need. Instead, they pay attention to friction points and address them as they emerge. When the same questions get asked repeatedly, they create documentation. When handoffs get messy, they define roles and responsibilities.

Lisa Park, who grew a service design team from 3 to 15 people at an ed-tech startup, explains: "I tried to implement a formal review process too early, and everyone hated it. Six months later, when we were stepping on each other's work, the same team was begging for clearer processes. Timing matters."

Design Maturity Isn't Uniform Across Your Organization

This insight catches many leaders off guard. While your service design team might be operating at a high level, different parts of your organization will be at different stages of design maturity. One product team might have senior designers running sophisticated user research, while another has junior designers focused mainly on visual polish.

The temptation is to embed service designers directly within existing teams, but this often backfires. Instead, successful leaders create center-of-excellence models where service design expertise can be shared across teams while maintaining consistency in approach and quality.

"I learned that you can't just drop a service designer into any team and expect magic," reflects David Kumar, who led design scaling at a healthcare platform. "You need to assess each team's design maturity and tailor your support accordingly. Some need hands-on coaching, others need strategic guidance."

Start Small, Then Spread Knowledge Intentionally

The most successful service design scaling happens through pilot projects that demonstrate value before expanding organization-wide. But here's the key insight many leaders miss: success isn't just about completing the pilot: it's about deliberately spreading the knowledge gained.

When a service design project succeeds in one area, successful leaders don't just document the outcomes. They move team members from successful projects to new initiatives, creating a network of people who understand both the methodology and the organizational context.

Jennifer Walsh, who scaled service design across multiple city departments, uses what she calls the "pollination strategy": "After each successful project, I strategically place team members in different departments. They carry the DNA of good service design practice with them, and that's more powerful than any playbook."

Measuring Impact Requires Upfront Investment

One of the biggest regrets shared by design leaders is not establishing clear metrics from the beginning. When you're scaling rapidly, it's tempting to focus on output: number of projects completed, personas created, or journey maps delivered. But stakeholders care about outcomes.

The leaders who maintain long-term support for service design initiatives invest early in measurement frameworks. They establish baselines for user satisfaction, operational efficiency, and business metrics before beginning major work.

"I wish I'd spent more time on measurement infrastructure in the first six months," admits Tony Chen, who led service design at a fintech startup. "By year two, when executives wanted to know our impact on customer acquisition costs, I had anecdotes instead of data. It almost killed our funding."

The most effective measurement approaches combine quantitative metrics (task completion rates, support ticket volume, conversion rates) with qualitative insights (user sentiment, employee feedback, stakeholder satisfaction).

Flexibility Beats Rigid Processes Every Time

As your service design work matures, priorities will shift. What worked during rapid early-stage development may alienate customers who now need stability. Similarly, the processes that served a 5-person team won't work for a 20-person organization.

The leaders who thrive during scaling remain adaptable. They treat processes as experiments, not commandments. When something stops working, they change it quickly rather than forcing people to adapt to outdated methods.

"I used to think consistency meant doing things the same way every time," reflects Maria Santos, who scaled service design at a government agency. "Now I realize consistency means achieving the same quality outcome, even if the approach varies by project or team."

Your Tools Should Enable, Not Dictate

Finally, don't underestimate the importance of choosing the right tools for collaboration, but don't overcomplicate things initially. The best tool choices enable cross-functional collaboration and can grow with your team.

Start simple: even a shared library of components in Figma can provide enormous value. The key is choosing tools that non-designers can engage with and that support the collaborative nature of service design work.

Moving Forward With Confidence

Scaling service design successfully requires balancing structure with flexibility, ambition with realism, and technical excellence with human connection. The leaders who succeed invest heavily in their people, maintain relentless communication, and remain adaptable as circumstances inevitably shift.

Most importantly, remember that every organization's scaling journey will be unique. These lessons provide a foundation, but your specific context: industry, company culture, existing design maturity: will shape how you apply them.

The goal isn't to avoid all mistakes but to fail fast, learn quickly, and keep moving forward with the knowledge that scaling service design is as much about organizational change management as it is about design methodology.