Episode #90: Building a User-Focused Company Culture with Jared Spool

A user-focused culture is not created by adding more UX terminology to meetings. It grows when teams understand specific people, see how decisions affect their experiences, and act on what they learn. In Episode #90, Jared Spool explains why organizations get in their own way and how UX professionals can shift the conversation toward outcomes that matter.

Replace averages with real experiences

Jared argues that an organization should become a leading expert on its customers and users: what they need, what their current experiences are, and what better future experiences could look like. That knowledge cannot remain inside a research team. It has to be shared across the organization if it is going to influence decisions.

One obstacle is the tendency to average people out of research. Jared describes seeing a claims journey map reduced to a single line despite hundreds of thousands of annual claims. Combining a very bad experience with a very good one can produce an average that belongs to nobody. The useful questions are more specific: Who had the worst experience? Who had the best? What happened to each person, and why did the outcomes differ?

Individual stories reveal emotion, breakdowns, and moments of relief that an average journey can hide. They give teams concrete material for deciding what to prevent, preserve, or improve.

What you'll learn

• Why UX advocacy should begin with stakeholder outcomes, not UX vocabulary

• How detailed user stories expose problems hidden by averages

• Why leadership does not require a management title

• How feedback loops connect employee decisions to customer experiences

• Why strategic research must reflect the organization's specific situation

Connect UX to the success stakeholders need

When a stakeholder is skeptical of UX, Jared recommends asking what success looks like for that person. The answer might be higher revenue, lower churn, or another business result. The next step is to examine which customer experiences would support that outcome. What would convince an existing customer to buy more? What would help a new customer recognize enough value to start paying?

This framing avoids arguing for UX as an abstract discipline. It connects experience work to the result the stakeholder is accountable for. In competitive markets, price, features, and reliability can converge. Experience then becomes a meaningful way to differentiate.

Jared also separates management from leadership. Managers are appointed and are responsible for helping teams work effectively. Leaders emerge when someone develops a compelling picture of a better future and another person chooses to follow. That means a researcher, designer, support representative, or housekeeper can lead change without waiting for a new title.

Earn influence by improving the decision

Jared rejects the idea that UX needs a symbolic seat at a table. Teams invite people whose knowledge will improve an important decision. UX professionals earn influence by bringing information the group cannot make a good decision without.

His Disney examples show how this can happen from the front line. Hotel staff who receive calls about sick children hold valuable experience data. A housekeeper who arranged towels and children's toys into a playful scene received direct positive feedback, shared the practice with colleagues, and helped it spread. In both cases, employees closest to guests could identify opportunities to make an experience better.

The wider lesson is to treat customer-facing work as a source of research. Support calls, status questions, complaints, tips, and notes already contain signals. Organizations need a way to collect and route that information so it can influence the product or service.

Build feedback loops and research strategically

Large organizations often insulate employees from the consequences of their decisions. Jared uses insurance claims as an example. A processor may choose to finish a batch of work before sending updates, while customers experience the silence as anxiety. A better system could automatically communicate when a claim was received, reviewed, and moved to the next step.

Feedback loops make these consequences visible. Jared recommends real conversations with customers, including spending time with someone while a claim is in progress and checking in repeatedly. Surveys are not a substitute for hearing how the experience unfolded. Over time, patterns emerge, including the failures behind the worst outcomes and the conditions behind the best ones.

This work requires learned skills and a willingness to move beyond standard practices. Jared's concern is that UX teams can be strong tactically but weak strategically. A best practice ignores context; strategy responds to a specific organization, customer group, problem, and business model. A subscription business losing most new customers after one year does not simply need another generic usability method. It needs to understand the gap between the initial promise and the value customers actually experience.

Episode #90 challenges teams to make UX concrete: know whose life should improve, trace the experience in detail, connect learning to business outcomes, and create feedback loops that support better decisions. Listen to the full conversation on Spotify.