Rethinking the Design Leader’s Job Description

Design leaders are often caught between board-level expectations and daily reality. Executive teams quote the familiar ROI figures — McKinsey’s 56% shareholder return premium, Forrester’s 100-to-1 return on UX investment — yet the teams tasked with delivering those numbers are typically small, overstretched, and expected to cover hundreds of projects. The gap between promise and capacity is not a resource problem; it is a role definition problem.

When design leaders see themselves as implementors — the people who run the research, build the prototypes, and execute the tests — they guarantee failure at scale. The alternative is to reposition the role around enabling others. This is not about relinquishing quality or control. It is about choosing between being hands-on with 10% of initiatives or meaningfully influencing 90% of them.

From Doing to Enabling

The practical shift involves four areas of focus: targeted services, coaching and mentoring, reusable resources, and organizational standards. Each one moves the design leader from the center of execution to the edge of influence.

Targeted Services

Rather than scattering effort across every project, concentrate on high-value interventions that multiply impact:

  • Discovery phases for major initiatives. If critical projects start with a user-focused foundation, they are far less likely to fail later. A structured assessment, such as the Strategic User-Driven Project Assessment (SUPA), can validate ideas against audience value, user needs, feasibility, and risk before heavy investment begins. This ensures the organization builds the right things, not just things right.
  • Project-specific design guidance. Periodic UX audits, milestone-based design reviews, and check-ins keep user-centered thinking present throughout development without requiring full-time attachment to any single team.
  • Workshops and problem-solving sessions. Rather than solving design problems for teams, lead sessions that help them solve their own. This transfers capability and confidence, so future challenges are met internally.
The key is to be strategic about where you spend your time, focusing on activities that will have the greatest ripple effect across the organization.

Coaching and Mentoring

Coaching is one of the most efficient ways to scale influence. Three formats work particularly well:

  • UX office hours. Set aside regular time when anyone can drop in with quick questions. Small issues get resolved before they become systemic, and stakeholders learn through informal interaction.
  • One-on-one or group coaching. Scheduled check-ins with product teams keep UX priorities visible and give individuals a direct channel for guidance. These sessions can also be used to mentor those who show particular interest in user-centered practices.
  • Tailored problem-solving sessions. When a team hits a specific obstacle, provide bespoke guidance. The immediate issue gets resolved — and the team internalizes the reasoning, making them more autonomous next time.
The goal isn’t to turn everyone into UX experts but to help them understand enough to make better decisions in their daily work.

It is also necessary to accept a temporary dip in output quality. If teams are criticized for not meeting an expert bar on their first attempt, they will disengage. A supportive environment that allows incremental improvement builds long-term capability. Enthusiasm matters more than perfection at the outset.

Creating Resources

Demand for UX support rarely abates. Persistent resources allow teams to act independently and consistently:

  • Design systems. A comprehensive system with reusable components, documentation, and design-development alignment embeds UX best practices into the interface itself. Teams work faster and fall into fewer traps when the default path is a good one.
  • UX tool suite. Pre-selected tools for research, prototyping, and testing save teams from evaluating options themselves. Curating the stack keeps quality predictable and onboarding minimal.
  • Research repository. A centralized store of findings across projects reduces duplicate effort and lets different teams leverage each other’s discoveries. Patterns that emerge from one initiative become visible inputs to another.
  • Vetted supplier lists. When external agencies are required, a shortlist of trusted providers ensures consistency and reduces procurement risk.
  • Self-service training. On-demand videos, interactive exercises, and step-by-step guides let people learn exactly when needed. Unlike scheduled workshops, self-paced material improves retention and application.
These resources should be practical and accessible, making it easy for teams to do the right thing.

Setting Standards

Standards provide a safety net for decisions made outside the design team’s direct view:

  • Design principles. Six to ten core principles, agreed upon by stakeholders across the organization, give everyone a shared reference for judgment. When people vote on these principles, they are more likely to honor them.
  • UX policies. Standardized processes for work requests, user research, and stakeholder involvement set expectations early. Non-specialists understand what is required of them, which prevents friction later.
  • Project prioritization guidelines. Clear criteria for how initiatives get sequenced and resourced prevent UX from being treated as a post-hoc concern. If user value is aligned with organizational goals at the planning stage, the design function is not forced to defend itself later.
The key is to make these standards helpful rather than bureaucratic — they should enable better work, not create unnecessary obstacles.

The UX Playbook

These components converge in a single source of truth: a UX Playbook. This living document contains the services, coaching options, resources, and standards teams need to deliver quality experiences without direct, daily oversight. It serves both as a reference manual and as tangible evidence of the design leader’s value. When it is kept current and visible, it shifts the design function’s identity from internal service provider to strategic partner.

The transition is not comfortable. It demands releasing day-to-day control over specific outputs and trusting others to represent UX principles in their own contexts. But meaningful, organization-wide change is only possible when leadership is exercised through others — not around or despite them.