Design Advocacy

• Design Advocacy is the practice of championing user-centered design throughout an organization. • It builds the culture, processes, and shared understanding needed for UX to thrive. • Effective advocates use data, storytelling, and strategic relationships to shift organizational mindsets.

stellae.design

Strategy

Design Advocacy is the ongoing effort to elevate the role of design and user experience within an organization. It goes beyond individual projects to shape organizational culture, processes, and decision-making. Advocates work to ensure design has a seat at the strategic table, that user research informs business decisions, and that the entire organization develops empathy for users. This involves education, demonstration of value, building coalitions, and gradually shifting how the company thinks about the role of design.

Why It Matters

Design advocacy is the practice of championing user-centered design within organizations that may not yet prioritize it. Without deliberate advocacy, design decisions get overridden by engineering constraints, business shortcuts, or stakeholder opinions detached from user evidence. Effective advocacy elevates design from a service function to a strategic partner, directly influencing product quality, user satisfaction, and long-term business outcomes.

Real-World Examples

Jared Spool's UX Metrics at UIE

Jared Spool famously demonstrated design advocacy by tying a major e-commerce site's $300 million revenue increase to a single UX improvement — removing a mandatory registration wall from checkout. By framing the design change in revenue terms, he gave executives a business case they could not ignore. This approach established a template for quantifying UX impact that advocates still use today.

IBM's Enterprise Design Thinking Program

IBM invested in a company-wide design thinking program that trained thousands of employees across all functions in user-centered methods. By embedding design practices into engineering and business teams rather than isolating them, IBM created a culture where advocacy was distributed. The program measurably improved product outcomes and reduced time to market across their enterprise portfolio.

Counter-example

Design Team Presenting Only Visual Mockups to Executives

A design team presents polished high-fidelity mockups to C-suite stakeholders without any supporting user research data, business metrics, or problem framing. Executives evaluate the designs based on personal taste rather than evidence, leading to subjective feedback cycles that undermine design credibility. This approach weakens advocacy by reducing design to decoration rather than positioning it as a strategic discipline.

Role-Specific Guidance

Common Mistakes

• The most common mistake is advocating with passion instead of evidence — emotional arguments about good design alienate business-minded stakeholders who need data to justify investment. Another frequent error is positioning design as a gatekeeper rather than a collaborator, which creates adversarial relationships with engineering and product teams. Teams also fail when they advocate only for large strategic changes while ignoring small, high-impact improvements that build credibility incrementally.