Rethinking UX: From Firefighting to Strategic Leadership

Most UX teams are chronically under-resourced. Often, the “team” is a single person, and the number of projects touching user experience far exceeds what that person can realistically handle. The result is a constant state of firefighting, where the deeper goal—improving the overall experience—gets lost in a sea of tactical deadlines.

Complaining about headcount won't change the math. The realistic path forward is to reconsider what a UX professional's role actually is, and how a small team can maximize its impact without growing to a size that can touch every detail of every product.

The Trap of Artifact-Centric Thinking

UX work is often defined by its activities: prototyping, user research, interface design, usability testing. But viewing these as the core deliverables is a trap. They are means to an end, and they are time-consuming and resource-intensive. For a small team, these activities can monopolize attention while delivering relatively little lasting value across the organization.

The true purpose of the team is to tangibly enhance the customer experience, not to produce a volume of design artifacts. That shift in framing has a major implication: those tactical activities may not always be the most effective use of the team's time.

Experience Evangelists, Not Implementers

With limited bandwidth, UX teams must move from a tactical, project-based mindset to a strategic, leadership-oriented one. The goal is no longer to execute UX tasks, but to influence the broader organization and inspire others to champion user experience improvements themselves.

The most effective path to this transition involves focusing on four areas: shared resources, training, consultative services, and community building.

Building Shared Resources

Creating valuable, reusable resources is a fast and effective way for a new UX team to demonstrate its worth. Rather than starting with project work, focus on establishing a core set of living assets. The most impactful typically include:

  • User Experience Playbook: An online hub with articles, guides, and cheatsheets covering everything from running surveys to A/B testing.
  • Design System: A library of UI components that lets product teams prototype quickly and accelerate development sprints.
  • Recommended Supplier List: A vetted list of external UX specialists that other departments can confidently hire for specialized help.
  • User Research Assets: A repository of personas, journey maps, and behavioral data for the organization’s primary audience segments.

These resources are not one-off documents. They need to be treated as services the team maintains and refines over time. And crucially, their role extends beyond utility; they serve as an ongoing demonstration of the team's value.

Scaling Through Training

Education is the most direct way to extend a small team's reach. By training the wider organization, the UX team turns colleagues into practitioners, prioritizing and championing customer experience even when the UX team isn't in the room.

Training should combine live workshops with self-paced learning materials, placing greater weight on the latter since it can be created once and refreshed periodically. Most self-directed content integrates well into the playbook and can be custom-written for organizational specifics or purchased when the subject matter is more generic.

Beyond that base layer, the team can supplement with mentorship sessions, lunch-and-learn presentations, and possibly an internal conference. Since the devil is often in the details for real design challenges, these sessions also serve as a gateway for offering more individual support.

Offering Advisory Services

A UX team doesn't need to be on every project to make a meaningful contribution. Redirecting effort toward consultative services can be considerably more impactful. Common service offerings include:

  • UX Reviews: A UX professional audits an existing digital service and delivers a prioritized set of improvement opportunities.
  • UX Discovery: New ideas are assessed early to determine if they address a genuine user need before heavy investment.
  • Workshop Facilitation: Guiding product teams through exercises to better understand user needs or apply design thinking to shape new concepts.
  • Consultancy Clinics: Regular open slots where colleagues can drop in and get advice from a UX expert.

A critical constraint here is to stay in the role of advisor, not implementer. The purpose of these services is to guide and empower other teams, and slipping into execution mode defeats that purpose and drains the team's limited resources.

Community Cultivation

Building a UX community creates a force multiplier for the team. This network of advocates is essential for spreading best practices and maintaining a culture that values customer experience.

The first step is a mailing list or community messaging channel. Through these platforms, the UX team can share research insights, tips, and wins from across the organization, and challenge members with questions or activities. For instance, a community-built and organization-wide design principles initiative is a powerful catalyst for culture change. Friendly internal competition is also effective, such as having teams rate their own services against the System Usability Scale.

The essential goal is to keep these champions engaged and spreading the message within their own functional teams, while continuously looking to grow the group. Some organizations find it worthwhile to offer community members exclusive advantages, such as priority access to UX resources or early enrollment in special educational programs.

Making the Transition from Firefighting

Moving a tactical, project-driven UX team toward this leadership model is rarely simple. Its position is often defined by past expectations. That's why establishing a new, explicit mandate—and securing visible support from senior management—is an essential first step.

Reframing the team as a center of excellence (CoE) is a powerful way to communicate the change in scope internally. The term is widely understood by leadership as a group that develops deep knowledge and distributes it broadly, which powerfully signals that the focus is shifting from individual execution to organizational enablement.

The mandate and KPIs must follow that lead. Objectives should be anchored on education and empowerment rather than project deliverables, and metrics should track organizational UX literacy, user satisfaction, and productivity—not the success or failure of isolated initiatives. Accomplishing this transition is an effort of a different magnitude, but the payoff is considerable: a UX team that is no longer the bottleneck to better user experience, but rather the driver of customer-centric innovation enterprise-wide.