Managing Large Design Teams

A few months ago, one of my clients found herself leading a much larger team after a round of layoffs. The number of her direct reports had almost doubled, and her calendar was busting at the seams with meetings. As she shared her feelings of overwhelm, I asked her what seemed most daunting and most permanent. She thought of her one-on-ones with her team as a permanent feature and also the most strenuous ones. She considered them a necessary evil so she could do justice to the other parts of her role. In our conversations, she realized that it was time to reset her approach to work and create new ways of working with her team, establishing clarity, RACI matrices, approval processes for decisions, meeting protocols, and approaches to convey risk. If you are in a similar situation, you may also need to co-create the ways of working with your team and start implementing them, so they become an integral part of the team’s everyday functioning. Your team members will look to you for clarity. When everything is important, nothing is important. You need to empower your team with categorical prioritization and clear communication. As my client defined what mattered the most for her role in the next 3 months, it became clear to her that she would need to focus her attention on her priorities, strategically delegate, and let go of what is no longer essential. As we speak, she is managing her attention with great zeal. Here are some steps she took to reengineer her meetings- ➡️Clubbing operational discussions with teams that work across a value chain to accelerate coordination and reinforce shared execution responsibilities. ➡️Clubbing discussions that are around the same challenge or decision, e.g., hybrid working, peak season delivery planning, etc., to ensure common understanding, alignment, and consistency of action. ➡️Her one-on-ones now focus on driving strategic outcomes, removing roadblocks for her team, and developing her next-level leaders. My client has adapted, performed, and grown through this journey, which initially seemed like a change forced on her. She has moved from being overwhelmed about managing a large team to intentional leadership and developing a team of trusted colleagues ready to take on more challenges. What are you currently feeling challenged by? What practices and mindsets do you need to reset?

Managing the team: In today’s evolving workplace, managing a team—especially one composed of younger, impact-driven professionals—requires a transformational leadership approach. Employees now prioritize meaningful work, visibility, and rapid feedback over traditional perks or titles. They are not just looking for tasks; they want to be part of projects that matter, and they expect constant communication, recognition, and growth signals. In this context, the manager’s role becomes pivotal—not just as a task-giver, but as a narrator of purpose and a curator of opportunity. Since promotions or title changes may not always be feasible every few months, managers must keep the team inspired by sharing upcoming opportunities, involving them in strategic pilots, and offering skill-stretching assignments. Regular updates from leadership, transparent communication about business direction, and personalized feedback loops help maintain trust and engagement. Managers should also act as career designers, helping team members visualize long-term growth even when short-term changes are limited. By fostering a culture of micro-recognition, innovation pods, and internal storytelling, they can turn aspiration into action. Ultimately, the modern manager is not just a leader—they are a bridge between ambition and reality, guiding teams with empathy, creativity, and strategic foresight.

Don’t fall into this trap: Trying to scale a product with unscalable decisions. Many teams assume the solution is to hire more people, add more tools, or push harder. They think velocity will magically appear if everyone just works a bit more efficiently. But the problem isn’t effort. It’s decision debt. When every new screen requires fresh alignment When designers have to guess which version is “the latest” When small choices turn into big conversations The team slows down, not because they’re slow, but because there’s no clarity. What you need isn’t more process. You need fewer decisions. Here’s the shift high-functioning teams make: 1.) They stop solving the same problems twice. 2.) Instead of debating buttons, they decide once. 3.) Instead of customising every component, they standardise where it counts. 4.) Instead of relying on memory, they build shared language. That’s what a good design system does. It’s not a UI kit. It’s infrastructure for speed. Because the faster your team can move past the basics. The more energy they’ll have for the work that actually moves the product forward. Without it, everything feels like Day 1. With it, ideas ship faster, reviews shrink, and juniors grow without hand-holding. Most leaders want momentum. Few are willing to reduce decisions to get there. What’s one small decision your team keeps remaking that should already be solved? If this resonated, share it with someone leading a complex team. Follow Joe Woodham for weekly insights on design leadership, systems thinking, and what actually scales.

Let's be honest: extensive cross-team coordination is often a symptom of a larger problem, not an inevitable challenge that needs solving. When teams spend more time in alignment than on building, it's time to reconsider your organizational design. Conway's Law tells us that our systems inevitably mirror our communication structures. When I see teams drowning in coordination overhead, I look at these structural factors: - Team boundaries that cut across frequent workflows: If a single user journey requires six different teams to coordinate, your org structure might be optimized for technical specialization at the expense of delivery flow. - Mismatched team autonomy and system architecture: Microservices architecture with monolithic teams (or vice versa) creates natural friction points that no amount of coordination rituals can fully resolve. - Implicit dependencies that become visible too late: Teams discover they're blocking each other only during integration, indicating boundaries were drawn without understanding the full system dynamics. Rather than adding more coordination mechanisms, consider these structural approaches: - Domain-oriented teams over technology-oriented teams: Align team boundaries with business domains rather than technical layers to reduce cross-team handoffs. - Team topologies that acknowledge different types of teams: Platform teams, enabling teams, stream-aligned teams, and complicated subsystem teams each have different alignment needs. - Deliberate discovery of dependencies: Map the invisible structures in your organization before drawing team boundaries, not after. Dependencies are inevitable and systems are increasingly interconnected, so some cross-team alignment will always be necessary. When structural changes aren't immediately possible, here's what I've learned works to keep things on the right track: 1️⃣ Shared mental models matter more than shared documentation. When teams understand not just what other teams are building, but why and how it fits into the bigger picture, collaboration becomes fluid rather than forced. 2️⃣ Interface-first development creates clear contracts between systems, allowing teams to work autonomously while maintaining confidence in integration. 3️⃣ Regular alignment rituals prevent drift. Monthly tech radar sessions, quarterly architecture reviews, and cross-team demonstrations create the rhythm of alignment. 4️⃣ Technical decisions need business context. When engineers understand user and business outcomes, they make better architectural choices that transcend team boundaries. 5️⃣ Optimize for psychological safety across teams. The ability to raise concerns outside your immediate team hierarchy is what prevents organizational blind spots. The best engineering leaders recognize that excessive coordination is a tax on productivity. You can work to improve coordination, or you can work to reduce the need for coordination in the first place.

One of the most common design mistakes in growing organisations is trying to turn a large group of senior managers into a team   In many organisations there’s a layer of managers sitting just below the executive who report into different exec members   A common response is to try to organise them into a single team – even though, in reality, this group is far larger than any effective team could ever be   At that scale, it’s not a team problem, it’s a coordination problem.   This layer is often the one the organisation was built on. Many of these leaders have grown with the organisation over time. They’re fiercely loyal, deeply committed and care enormously about protecting what’s been built   That loyalty matters and it’s precisely why this layer can end up carrying far more than is visible.   When organisations try to force a group like this into a team shape, the strain doesn’t usually show up as open conflict. It shows up more quietly, in how people make sense of what’s going on around them   Strategy gets interpreted individually rather than collectively. People try to infer intent from fragments of information and under pressure those interpretations often skew negative.   🔹Other teams’ actions get misread as lack of care or competing agendas  🔹Constraints elsewhere are experienced as poor judgement  🔹Tensions that should be held collectively get absorbed individually    What’s happening underneath isn’t disengagement. It’s fragmented sense-making At the same time, decision-making becomes harder than it needs to be   When it’s not clear who decides what, escalation starts to feel like the safest option – not because people want to push things upwards, but because the risk of getting it wrong feels too high    The deeper issue here isn’t capability, it’s design   A group of this size works better when it’s treated as a system, not a team. That shifts the focus away from cohesion towards coherence – from purely trying to make everyone aligned, to being clear about how leadership work actually happens across the organisation   🔹Shared sense-making – so people don’t have to interpret strategy alone  🔹Clear decision rights – so it’s obvious what sits locally and what genuinely needs escalation  🔹Explicit priorities and tensions – so trade-offs like growth versus capacity, or volume versus quality are named rather than quietly carried  🔹Simple coordination mechanisms   When this is in place, something subtle but important changes and a large, diverse group of senior managers starts to operate as a coordinated leadership system   This is the kind of work Dani and I love as OD practitioners   It's not about "fixing" people or running team-building for groups that can’t realistically be teams, but helping organisations design ways of working that match the reality of scale, pressure and growth Where is unclear decision-making quietly draining energy and being mistaken for disengagement?

Earlier today I sent the same question to a handful of design leaders I respect, people running design teams at serious product companies: "How do you keep design quality consistent when you can't review everything your team ships?" Every single one of them, independently, described a version of the same playbook. First, they write their judgment down. Design principles, design systems, documentation. An agreement on what good looks like that exists outside anyone's head. Second, they distribute the reviewing. Frequent crits, peer feedback, principal designers who own parts of the product and run the sessions there. Third, they triage themselves. They personally review only the work with the highest stakes or the most contention, and trust the team with everything else. It is a solid playbook. But one answer was different. One of these leaders, someone I consider excellent at this, told me that on a good week he makes it to half of the reviews. Half. On a good week. Nobody said it as a complaint. It was said as a fact of the job, the way a football coach accepts that on match day they cannot touch the ball. Whatever the coach knows only matters if it made it into the players during training. That is what the answers revealed to me. Design leadership at scale was never about reviewing more. It is about how far your judgment travels when you are not in the room. The principles you wrote, the standards you repeat in crits, the questions you always ask, that is the part of you that reaches the work you will never see. And the distance is growing. Companies everywhere are flattening their structures, and design is losing leadership layers faster than most functions. The leaders who remain cover more teams, more products, more decisions than the playbook was designed for. From here the math resolves in one of two ways: the leader becomes the bottleneck, or quality quietly settles at whatever the principles and the crits can hold on their own. If you are also a design leader, audit where your judgment actually lives. If it only lives in your calendar, in the reviews you personally attend, it stops the moment your calendar fills up. If it lives in artifacts your team actually uses, it ships with every screen. That gap, between what a leader knows and what their team ships, is the most interesting problem I have touched in years. Interesting enough that I am building something to close it. More soon.

Have you ever looked at an extremely skilled design team and felt like their output was largely middle-of-the-road or generally unextraordinary? It's usually from a structural leadership bottleneck. Giving highly competent people hard restrictions strips away their autonomy, turning a complex heuristic problem into a mindless, algorithmic task. And the data backs this up. Haaaaaaaard... Sam Glucksberg ran a version of the famous 1945 candle problem experiment out of Princeton University: Two groups, same creative task. One group was incentivized. The other wasn't. The incentivized group took 3.5 minutes longer to solve the problem. According to Daniel Pink's related framework, structure helps with routine work, but for creative work, external control narrows cognitive focus and actively diminishes problem-solving. Design is a heuristic discipline so every brief is essentially its own candle problem. Delf-determination theory reinforces this from the motivation side—for people to do their best work, three psychological needs have to be met: → Autonomy, or the freedom to choose how → Competence, or the ability to exercise mastery → Relatedness, or feeling connected to the team and mission Strip away autonomy and you bottleneck your most capable people with your own cognitive limits. Robert House's path-goal theory says directive leadership is effective for inexperienced workers facing ambiguous tasks, but for high-ability, high-experience people it becomes redundant and is regularly perceived as micromanagement, which tanks satisfaction and motivation. Google confirmed this at scale via a Project Aristotle study, which analyzed 180+ teams and found that psychological safety is the single strongest predictor of team effectiveness. So here's what actually happens when you over-direct senior creatives: ☒ You pay a premium for their brain ☒ You micromanage the execution ☒ Their cognitive capacity gets bottlenecked by your instructions ☒ The result: friction, churn, and expensive people producing forgettable work High-level talent minus autonomy equals a massive pile of technical debt. Management research call the solution "loose-tight leadership": ☑ Tight on the what: Clear goals. Defined constraints. Hard success criteria. Non-negotiable timelines. ☑ Loose on the how: Total flexibility on process. Trust in execution. Room to experiment. Smart designers don't want a blank canvas. They want a defined sandbox with clear parameters and freedom to achieve the goals their own way. So the TL;DR for design leadership: Get the hell out of their way! 😂 Which side of this equation is your team currently stuck on — unclear boundaries, or zero autonomy? #designleadership #productdesign #uxstrategy #designops #creativeleadership ⸻ 👋🏼 I'm Dane—a designer creator + mentor. 🙃 Rated PG-13 for hard facts + adult language. ❤️ If you liked this post a 👍🏼 would be the bee's knees. ➕ Follow for more of my shenanigans in your feed.

Every design org I walk into has the same problem. They just describe it differently. "Our designers are drowning — 4 people covering 10 scrum teams." "We need a NorthStar experience but the team is stuck in feature factory mode." "I think we need to hire a CDO but I'm not sure what I'd even ask them to do." Different words. Same issue: the design function has outgrown the way it's organized, and nobody has the time or vantage point to figure out what needs to change. That's the work I do now. I've led design orgs from 5 to 285 people — at ServiceNow, GE Digital, Compass, Cisco's security business, and Google Cloud. I know what a healthy design org looks like because I've built them. I come in as a fractional CDO and within two weeks assess the whole picture — talent, process, toolchain, strategy. Not with a framework someone sold me at a conference. With an approach I call workflow archaeology: understand how work actually moves through the organization before you change anything. The real bottleneck is almost never what leadership thinks it is. At one company, everyone assumed they needed more designers. The actual problem was that every decision required a round trip through Figma, a handoff spec, a dev build, and a review cycle. We collapsed that by moving to code-first design. Capacity improved because we removed a broken process, not because we added headcount. At another, the team was talented but directionless — no shared vocabulary between product, design, and engineering. My partner Jorge Arango and I ran a two-day ontology workshop before touching a single tool or process. Everything after moved faster because people were finally solving the same problem. Here's what makes this moment different: the boundaries between design, engineering, and product are dissolving. AI can generate production-ready components. PMs can prototype without waiting for a designer. Engineers can explore UX alternatives in code before a spec exists. Most organizations haven't rethought who does what, or why. That's an organizational design question, not a tooling question. Most design orgs don't need a transformation. They need someone who will look at how work actually happens and make targeted changes that unlock the team — a toolchain shift, a staffing model change, rethinking how disciplines collaborate, or helping leadership understand what design should actually be doing for the business. The companies that get this right don't hire a full-time executive and wait six months for a strategy deck. They bring in someone who's seen the patterns and can start making things better in weeks. If your design org is stuck and you're not sure why, I'm happy to talk. Greg Petroff is a fractional Chief Design Officer with experience at Google Cloud, ServiceNow, GE Digital, Compass, and Cisco. He partners with Jorge Arango through Unfinishe_ (unfinishe.com).

The most common conversation I'm having with design leaders right now is how to handle the anxiety their team members are exhibiting during this chaotic AI moment. In my response, I draw upon the core leadership concepts for cultivating trust, tailored to the current context. 🧐 Know how the team actually works. Perhaps the biggest change teams are seeing is in how work gets done. Deep understanding of process, practices, tools, informal workarounds, and standards is necessary. Without it, these changes become an imposition—confusing, arbitrary, inhibiting. 🗣️ Messages match lived experience. Leaders know the importance of maintaining positivity to keep their team's spirits up. But go too far, and that positivity becomes toxic. "Everything's fine! Just keep at it!" causes teams to disengage. Or leaders insist nothing is changing, while their teams are anxious about job security, skill relevance, and being measured against robots. Acknowledging tension isn't giving into negativity, it's being honest. And it provides an opportunity for optimism such as real productivity gains; the ability to directly address design debt; being freed to "move left" and tackle more strategic challenges. 📈 Follow through on your commitments. Design leaders primarily make two commitments to their teams: their professional development, and keeping them on work worth doing. AI tooling is threatening what many perceived to be their core skills. Providing space for learning—whether AI tools themselves or adjacent skills—and practice becomes imperative. All this acceleration brings more work. For leaders, "discernment" means filtering out what isn't worth doing, so teams tackle projects with true potential. 🫪 Vulnerability. The leaders navigating this moment best are explicit about how they don't have all their answers. They name their own uncertainty, show what they're trying, and admit when something doesn't work. Leaders must model uncertainty, so that their team members can be honest about their own. When leaders perform confidence they don't have, their teams hold back their own challenges, and you don't really know what's going on with them. 🦺 Psychological safety. Tools emerge and change faster than any one person can track, new applications are invented daily, and professional norms haven't caught up. In a chaotic environment, people need psychological safety: to be able to experiment, fail, admit confusion, ask questions, and even push back on leadership direction without fear. At this moment, "performance" needs to be about learning more than it is about output. If someone's efforts haven't resulted in delivery gains, but they and the team are wiser, that's a win. If this resonates, consider joining the upcoming Intentional Design Leadership Circle, a 6 week cohort starting April 15 hosted by Jesse James Garrett and me, where we provide space for leaders to reflect, connect, and grow. https://lnkd.in/gmb9rq7R

Design leadership breaks long before teams do. That gap is the blind spot. Most leaders don’t see it until it is too late. Historically, most Design Executives are operating as the system and the operator. Running the org, chasing alignment, fixing narratives, stepping into every gap. It works… until it doesn’t. On a certain scale, this becomes the bottleneck. If you’re still the one: 🔸 Translating design to the business 🔸 Stitching together planning and priorities 🔸 Managing the narrative across execs 🔸 Jumping into every “urgent” situation You don’t have a capacity problem. You have a structure problem. This is where a strong Chief of Staff (CoS often your Head of DesignOps) changes the game. Not as support. As a force multiplier. A great CoS doesn’t just “help.” They: 🔸 Own the operating system (planning, rhythms, decision flows) 🔸 Shape and carry the leadership narrative when you’re not in the room 🔸 Turn scattered signals into direction and decisions 🔸 Surface the hard truths early, before they become executive escalations 🔸 Extend your reach across product, engineering, and business leadership The shift is simple, but not easy: You stop being the hub for everything. You start designing how the system runs without you. You get time back and, most importantly, you regain altitude. ✅ Space to focus on influence, not coordination ✅ A leadership team that operates, not escalates ✅ Better decisions, made earlier, with better context ✅ Stronger, more consistent executive presence from your org Most design orgs wait too long to make this move. Usually, once the strain is already visible. By then, the issue is no longer capacity. It is about structure. What is your experience with the CoS in your team? If you don’t have one, what is holding you back? #Design #Leadership #CDO #ChiefDesignOfficer #DesignOps #ChiefofStaff #UX #COS