Designers working at scale absorb hundreds of inputs, requirements, opinions, and constraints, then distill everything into a product that’s simple and intuitive—all while adapting to new tools and processes. That work asks them to step outside their comfort zone, take risks, and put themselves in a vulnerable creative headspace against a backdrop of rapid tech shifts, lean companies, and AI regularly disrupting how people think and work.

The job of leading such a team demands flexibility, compassion, grit, and taste. There’s no playbook, but thinking from first principles and questioning your own assumptions gets you far.

Start with team health

Nobody brings their ‘A’ game when they’re stressed, overworked, burned out, or afraid to raise problems. Successful creative collaboration rests on trust between team members and a shared mission—a kind, fearless crew that levels with each other without critiques landing as personal or belittling.

  • Offer both synchronous and asynchronous venues so the loudest voice in the room doesn’t always dominate decisions.
  • Invite sharing at every project phase. A rough sketch and the final_final_final design should be equally acceptable to post.
  • Check in regularly through 1:1s, career discussions, and team feedback surveys, so lurking problems surface early.
  • Be realistic about bandwidth. Don’t overcommit and set the team up to fail.
  • Model vulnerability and candor—admit when you don’t know the answer or are wrestling with a problem yourself.
Bright, abstract collage of colorful geometric shapes arranged in a grid on a blue background. Designs include flower-like bursts, petal forms, checkerboard tiles, and overlapping curves in various colors like orange, pink, purple, green, red, and black.

Encourage experimentation and shifting roles

Designers spike in different ways: a problem that confounds one is a dream project for another. Track everyone’s superpowers and growth areas, and in larger organizations group complementary skillsets so teams feel balanced and members learn from each other.

This matters more as research, design, product, and engineering draw closer and people shift across specialities and role boundaries. The aim is a team built to adapt that feels excited about change.

  • Move designers closer to production with more AI prototyping and code experimentation. The faster they can evaluate real things, the quicker they make good decisions—a flywheel effect on productivity.
  • Create spaces to share experiments and document lessons. Figma has a #design-wip channel where designers post ideas, sketches, or functional Figma Make prototypes of product flows.
  • Bring cross-functional collaborators into the process—at Figma’s design crits, designers often invite them for fresh perspectives and a more inclusive workflow.
  • Parallelize execution and invention. Keep shipping while also reimagining how the work evolves with the tech landscape.

Treat craft as a differentiator

In a crowded market, useful, well-executed products set you apart, build loyalty and advocacy, and drive growth—especially in enterprise software, where craft is often an afterthought. Even when everyone agrees craft matters, other pressures get in the way: great execution requires attention to detail, so some projects take longer or demand hard trade-offs, like prioritizing UX refinements over more features.

Moving fast, teams may skip visual consistency and clarity and accumulate design debt that drags down customer satisfaction. Cut scope, not corners: a well-considered, tightly scoped solution beats a half-baked, more ambitious one, and getting the balance right delivers impactful work at a reliable cadence while building credibility.

  • Aim for excellence and communicate it widely. Define what great craft looks like for your product, revisit it, document before-and-after examples of going the extra mile, and flag which surface areas matter most.
  • Use metrics to tie better design to business value. If simplifying a workflow improved conversion, make noise about it; a delightful detail that improved goodwill is qualitative evidence of brand value.
  • Show that quality accelerates engineering efficiency. Well-built, reusable design components aligned to code let teams move faster and focus on novel work.
Abstract digital scene depicting a figure in a red shirt reaching toward a distant, glowing horizon. The figure stands on a path made of colorful, rectangular banners that stretch into the distance. The environment blends painterly textures of green and white with surreal, vibrant shapes and floating forms.

Build bridges across the org

As a company scales, bureaucracy can overrun care for great products. Teams ship the org chart, narrowly pursuing their own incentives instead of the greater good; “that’s not my problem” attitudes sprout, and designers reuse poor UX patterns because another team set bad precedent.

Design leaders must actively defend against this. Watch for inefficiencies—projects drowning in ambiguous meetings, teams working in isolation toward similar outcomes, groups struggling to align—then create space for those people to talk. Sometimes a new Slack channel, a meeting, or a short proposal for operational change is enough.

  • Share your thinking, not just deliverables. Async walk-throughs and project recaps broadcast progress and lessons; try Loom videos or simple slide decks.
  • Run regular cross-functional workshops where designers present recent work and pose open questions to partners outside their team—good for feedback, visibility, and alignment.
  • Set up tiger teams when a problem needs experts from across the company. Form them explicitly as a formal working group; if it works out, the experience can inform future org design.
llustration of people working together along a twisting, infinity-loop-shaped ribbon. The characters are shown in pairs or groups collaborating on various design and development tasks, including reviewing text, color palettes, layouts, charts, and code. Speech bubbles and thought bubbles emphasize communication. The background is light purple

Be judicious about process

Macro uncertainty leaves teams anxious, and leaders sometimes respond by adding checkpoints for constant oversight, review, and approval. Useful in moderation, too much process turns creativity into a dull factory environment. The sweet spot is just enough. Trust everyone to make good calls and bubble up challenges, and leave room for projects to wander before landing on the right solution, so that wandering doesn’t feel like a mistake.

To support autonomy, coach designers to develop an editorial sensibility about their work, so they self-edit and drive decisions instead of checking in for permission—leaning on you for support and refinement rather than direction.

  • Which decision would you make if it was entirely up to you? Builds ownership and confidence in making calls.
  • How would you explain this concept to a user? Pulls teams out of internal debates and tests whether the design is simple enough to state in plain language.
  • How does this proposal support our business? Pushes designers to evaluate ideas against company goals, helping more projects get a green light.
  • How might we simplify it? Now edit, edit, edit.
Abstract digital artwork with a vibrant blue and pink gradient background. In the center, a yellow square contains geometric icons including a blue play button, red circle, and various lines and shapes. Surrounding the square are multicolored 3D shapes—such as arrows, orbs, and squiggles—radiating outward in a circular pattern.

Set the terms for the next chapter

Growth itself is a healthy signal: more products, more people, and more teams suggest the work matters. Left unmanaged, though, that expansion produces directional confusion, teams assembled by accident, and duplicated effort. A small amount of discipline in how headcount is added prevents most of it.

Sizing the team before adding to it

  • Hire only when you can justify it. An open req is not an obligation to fill it. Know what a new hire contributes and where they will concentrate over the coming 6 to 12 months.
  • Watch team ratios. If a designer has too few engineers behind them, they spend their time on vision work that never ships. In that situation, deferring the hire until partner teams staff up may be the better call.
  • Treat new roles as gap-fillers. Audit the team's strengths and weaknesses periodically and adjust hiring to match. A group strong on visionary thinking but weak on product quality needs craft specialists; a group executing well but short on capacity may simply need more of what already works.

Leave room for lightness

Design work is hard even under ideal conditions. Part of a manager's job is relieving the pressure at the points where it peaks: a bad pun in Slack, a five-minute icebreaker opening a meeting, or a moment of recognition after a major win. These are small gestures, but they give people a chance to relate to one another as people, and a bit of that joy tends to show up in the work itself.

Built deliberately, not by default

Adaptability is not a property that emerges on its own. It comes from leaders acting intentionally, explicitly giving permission, and encouraging people to keep pushing at what seems possible. Expect some trial and error along the way. What matters most is fitting the approach to your own team and their particular needs. Those needs will shift, but the principles hold regardless of what comes next.