Your Design Team Doesn't Have a Skills Problem - They Have a Systems Problem

You hired good designers. They went through a rigorous interview process. They demonstrated strategic thinking. Then they joined your organisation and stopped being strategic. The problem is not what you think it is.

The Three Complaints I Hear Every Time

When a design leader, a VP of product, or a founder comes to us about their design team, the complaint is almost always one of these three. Sometimes all three.

Complaint 1: "My designers are not strategic enough."

They keep delivering screens instead of thinking about the problem. They wait for briefs instead of shaping direction. They never push back on product. They produce what is asked, on time, to spec - and that is exactly the problem.

I have sat in sprint meetings where the design team was giggling and comfortable. When I dug deeper, the reason was always the same: they were following instructions word for word. Product gave a brief. They executed. Nobody argued. Everyone was praised. The system rewarded compliance. So the team complied.

McKinsey's Design Index research across 300 companies found that 60% of design-and-development decisions in large organisations are made by a small number of employees in isolation - meaning designers are excluded from the very decisions they are then asked to execute. When you exclude someone from the thinking and then blame them for not thinking, that is not a skills problem. That is a systems problem.

Complaint 2: "Our design quality is inconsistent."

One project looks polished. Another looks like a different company made it. There is no shared design language, no consistent interaction patterns, no standard for what "done" looks like. The output feels like it was produced by five separate freelancers rather than a team.

In engineering, this does not happen. Why? Because code reviews are non-negotiable. Every piece of code gets reviewed against standards before it ships. There is a process, a cadence, a definition of quality.

Most design teams have nothing equivalent. Designs go from one person's screen to a Jira ticket without a structured review. No peer critique. No quality checkpoint. No shared criteria. Every designer operates as an island. The inconsistency is not because some designers are better than others. It is because no system exists to calibrate quality across the team.

Complaint 3: "We cannot retain senior designers."

You hire good people. They perform well for 12–18 months. Then they leave. You assume it is compensation or a better offer. It rarely is.

Gallup's research on team performance found that clarity of expectations is the single most basic employee need. When designers do not know what growth looks like, do not have a career progression framework, do not receive structured development feedback, and cannot see a path from where they are to where they want to be - they leave. Not because they found a better salary. Because they found a system that develops them. (The blog on the difference between a ₹12L and ₹30L designer is partly about this - the gap is often not skill, but the system that develops or fails to develop that skill.)

When a senior designer leaves, the cost is 1–2x their annual salary in replacement, onboarding, and ramp-up time (SHRM). But the real cost is invisible: the institutional knowledge they take with them, the relationships they built with stakeholders, and the 6–12 months before their replacement produces equivalent output.

The Same Designers. The Same Skills. Completely Different Output.

Here is the test that proves whether you have a skills problem or a systems problem.

Think about the designers on your team. Now imagine them at a design-mature organisation - one with structured design reviews, a seat at the strategy table, clear role definitions, an established research practice, and a leadership team that understands design's value. Would those same designers produce better work there?

If the answer is yes - and it almost always is - your problem is not the designers. It is the system they operate within.

McKinsey confirmed this at scale. They tracked 300 companies over five years and found that top-quartile design companies grew revenue 32% faster and total shareholder returns 56% faster than their peers. The difference was not that these companies hired better individual designers. It was that they built better systems for design: executive-level design leadership, cross-functional integration, continuous user research, and iterative processes. The McKinsey Design Index measures the system, not the people. And the system is what determines the output.

Deloitte's 2025 Global Human Capital Trends research puts a number on the gap: 93% of leaders say moving from rigid structures to flexible, skill-based systems is important to their success. Only 19% say their organisation is actually ready for it. That 74-percentage-point gap between knowing and doing is where most design teams are stuck.

What the System Is Actually Missing

Every complaint traces back to one or more of these five missing systems. These are not theoretical frameworks. These are the specific infrastructure gaps I see when I work with design teams at product companies - from 20-person startups to 500-person enterprises.

If the symptom is inconsistent quality → You are missing a design review cadence.

A design review is not "show your work and get compliments." It is a structured, recurring session where design work is evaluated against explicit criteria: Does this solve the stated problem? Is the interaction pattern consistent with the design system? What does the research say? What trade-offs were made, and why?

Without this cadence, quality is determined by the individual designer's judgment and the preferences of whichever stakeholder happens to be in the room. Some designers are stronger than others - but without a shared standard, even the strongest designer's work drifts.

What a functioning system looks like: A 30–45 minute weekly review. Rotating presenters. Specific feedback criteria documented and shared. Attendance from at least one lead or manager who maintains the quality bar. Non-negotiable cadence - not cancelled when the sprint gets busy, because that is exactly when quality slips most.

If the symptom is "designers are not strategic" → You are missing a stakeholder integration protocol.

Design cannot be strategic if it enters the process after the strategy is already decided. In most organisations, product defines the problem, engineering scopes the solution, and design receives a ticket. By the time the designer sees the work, the strategic decisions have been made. There is nothing left to be strategic about.

This is the printer-not-author pattern. Design's job is to give the brief visual shape and deliver. Not to question whether the brief is right. Not to challenge the problem definition. Not to propose a different approach. The system has defined design's role as execution, and then leadership is surprised when the execution is not strategic.

Fewer than 5% of the companies McKinsey surveyed had leaders who could make objective design decisions. If the people approving design work cannot evaluate design thinking, the feedback loop incentivises visual polish over strategic depth. Designers learn very quickly what gets praised and what gets ignored. If the system praises compliance, it gets compliance.

What a functioning system looks like: Design enters before the brief is finalised - ideally at the problem definition stage. There is a defined moment where design contributes to scoping, not just execution. Joint reviews between design and engineering happen before handoff, not after. Design has documented authority to question the brief and propose alternatives. This is not about giving design veto power. It is about giving design a voice before the decisions are locked.

On getting design into the room where strategy happens: How to Get a Seat at the Product Strategy Table as a UX Designer.

If the symptom is role confusion → You are missing role clarity between IC, Lead, and Manager.

Ask five people on a design team who is responsible for what, and you will get five different answers. The IC is doing lead work without the title or the pay. The lead is doing IC work because they enjoy it and nobody told them to stop. The manager is a pass-through - relaying decisions from leadership to the team and output from the team to leadership, adding no strategic value in either direction.

These are the conveyor belt and one-person army patterns - and they are systems failures, not individual failures. The organisation never defined what each role owns. So everyone defaults to what is comfortable. Comfort does not produce growth, and ambiguity does not produce accountability.

What a functioning system looks like: Written role definitions. What does an IC own (individual project delivery, craft quality, personal skill development)? What does a lead own (design direction for a product area, cross-project consistency, mentoring ICs)? What does a manager own (team performance, stakeholder relationships, hiring, career development, process design)? Where do responsibilities overlap, and who has the final call? These definitions should be documented, shared with the team, and referenced in performance reviews.

If the symptom is design not being taken seriously → You are missing a design maturity roadmap.

Most organisations do not know what design maturity means. They hired designers. They gave them projects. They expected the quality of design to improve automatically. It did not.

Design maturity is not a designer's individual skill. It is an organisational capability. It requires investment in research infrastructure, stakeholder education, process definition, and leadership alignment. Without a roadmap, the design team operates at whatever maturity level the organisation defaults to - which is usually somewhere between "make it look good" and "we trust design to handle the visuals."

I have worked with design teams at organisations where UX was introduced two and a half years ago into a company with legacy products. The team exists, but design maturity is thin. Research is evaluative, not exploratory - the team validates decisions already made rather than informing decisions yet to be made. Product delivers information in chunks and does not treat design as an equal partner. The culture is not hostile to design. It just has no system for integrating design at a strategic level. That is a maturity gap, not a talent gap.

What a functioning system looks like: An honest assessment of where your organisation sits on a design maturity model (Nielsen Norman Group's is a good starting point). A 6- and 12-month roadmap that identifies the specific gaps: Is it research infrastructure? Stakeholder buy-in? Process definition? Executive understanding of what design contributes beyond visuals? The roadmap addresses the organisation, not just the team - because design maturity is an org-level problem that cannot be solved by training designers alone.

If the symptom is losing senior designers → You are missing a feedback and growth system.

When designers do not know what "good" looks like at the next level, do not receive structured development feedback, and cannot see a career path - they leave. The departure looks like a retention problem. It is actually a development system problem.

Only 20% of C-suite leaders strongly agree that their HR function and workforce practices improve worker performance (Deloitte, 2025). That means in 80% of organisations, the systems that are supposed to develop people are not working. Designers experience this as stagnation: they are doing the work, getting decent reviews, but not growing. The organisation has no mechanism to close the gap between current performance and next-level readiness.

This is also where the IC-to-manager transition breaks. The organisation promotes a strong IC into management without preparation, the transition fails, and the designer concludes they are not built for leadership. The hidden cost of that pattern is two losses in one decision: you lose your best IC and gain an untrained manager. Both losses are systems failures. On what happens when that promotion goes wrong: The Hidden Cost of Promoting Your Best IC Designer to Manager.

What a functioning system looks like: A defined competency framework for each level (IC, lead, manager). Quarterly development conversations that are about growth, not status updates. A career ladder that is documented, shared, and connected to real progression criteria - not just years of experience. Recognition structures that make designers feel seen. If you do not have a system for developing people, the people you develop will be developed by someone else.

Audit Your Design Team's Systems

How to Fix the System Without Replacing the Team

The instinct when design output is underwhelming is to fire and rehire. Get better people. Find designers who are "more strategic."

This almost never works. The new designers enter the same system, face the same incentives, produce the same output within six months. You have spent the replacement cost (1–2x annual salary per person, per SHRM) and changed nothing. The cycle repeats.

Instead, approach it the way you would any other business system that is underperforming:

Diagnose before you prescribe. Use the audit above. Identify which of the five systems are missing or broken. Be honest - most organisations are missing at least three.

Fix one system first. You do not need to transform everything at once. Pick the system causing the most visible damage. Usually it is stakeholder integration (design is excluded from decisions) or review cadence (quality is inconsistent). Fix one. Let the team experience what a functioning system feels like. The impact is visible within one quarter.

Invest in systems training, not just skills training. The gap is rarely that your designers cannot use Figma or run a usability test. The gap is that nobody in the organisation knows how to set up the infrastructure where design can function at its full potential. That is a leadership and organisational design challenge - not a "send them to a workshop" challenge.

Measure the system, not just the output. Track whether design enters the process before or after scoping. Track whether design reviews happen weekly. Track whether career development conversations are scheduled quarterly. Track whether role definitions exist. If you only measure what the team produces, you will keep blaming the team. If you measure the system, you can fix the system.

If This Sounds Like Your Team

If you recognised your organisation in two or more of the symptoms above, the problem is diagnosable and fixable. It does not require replacing your team. It requires building the systems your team needs to operate at full capacity.

Our corporate training programme is built for exactly this. We work with design teams at funded product companies and help them build design-specific systems: review cadences, stakeholder integration protocols, role definitions, maturity roadmaps, and leadership development for the people managing the team. Not generic management training. Systems that make your existing designers more effective.

The conversation starts with a systems audit. Book a training call and we will assess which systems are missing and what it takes to build them.

Sources & References

• McKinsey & Company - "The Business Value of Design," October 2018. 300 companies, 5 years, 2M+ data points. Top-quartile design: +32% revenue, +56% TRS. <5% of leaders can make objective design decisions. 60% of design decisions made in isolation.
• McKinsey - "Are You Asking Enough from Your Design Leaders?" February 2020. 200 design leaders + 100 executives. 90% not reaching design's full potential. Only 10% at highest maturity. Only 14% set quantified design targets.
• Deloitte - 2025 Global Human Capital Trends. 93% say flexible structures important vs 19% ready. Only 20% of C-suite strongly agree HR practices improve performance.
• Gallup - "State of the American Manager." Clarity of expectations is most basic employee need. 70% of team engagement variance attributable to the manager.
• SHRM - Managerial replacement cost: 90–200% of annual salary.
• Xperience Wave - direct observation from corporate training engagements with design teams at product companies across India.

About the Author

Murad is Co-founder and Head of Design at Xperience Wave, a UX design career development company based in Bangalore. He has 13+ years of design leadership experience across fintech, healthtech, and industrial technology. The systems patterns in this blog come from direct work with design teams at product companies across India through XW's mentorship and corporate training programmes.

Read Next

• On what happens when you promote your best IC without preparation: The Hidden Cost of Promoting Your Best IC Designer to Manager.
• On getting design a seat at the strategy table: How to Get a Seat at the Product Strategy Table as a UX Designer.
• On the conversations that separate senior designers from the rest: 5 Conversations Senior Designers Have That Junior Designers Don't.

- Murad, Co-founder & Head of Design, Xperience Wave