UX Leadership & Influence

UX Leadership Strengths Model Self-Assessment

Use when: understanding your natural leadership style and identifying where to invest in growth.

UX practitioners tend to lead through one of five strengths. Understanding yours helps you play to it while deliberately developing the others:

The Architect (34.7% of practitioners). Excels at setting and inspiring others with overall design vision and direction. Helps others envision the future state, creates blueprints and frameworks that build shared understanding, and creates inclusiveness to get people on the same page. The architect's superpower is making the invisible visible — turning abstract strategy into concrete direction that a team can rally around.

The Foreperson (30.6%). Excels at maintaining momentum on a project. Incorporates input and makes others feel listened to, navigates critique and feedback without losing progress, and communicates adjustments while setting expectations. The foreperson's superpower is keeping things moving — absorbing organizational friction without letting it slow the team down.

The Orator (25.6%). Excels at communicating ideas and insights effectively and persuasively. Breaks down big ideas into their core parts to ease comprehension, captures and shares the thought process that led to an idea, and leads others toward conclusions. The orator's superpower is clarity — making complex things simple without losing their meaning.

The Interpreter (9.1%). Excels at understanding what stakeholders care about and communicating how UX can achieve business goals. Demonstrates the value of UX to others and builds the business case for investment. The interpreter's superpower is translation — converting UX value into the language of revenue, efficiency, and competitive advantage. This is the rarest strength among UX practitioners, which is why organizations often struggle to fund UX work.

The Evangelist. Excels at cultivating trust, building relationships, creating a following, and sharing a message. The evangelist's superpower is belief — their conviction gains strength when others adopt it, and they build the organizational momentum that turns UX from a department into a culture.

Distribution data from ongoing NN/g conference surveys shows Architect and Foreperson as the most common strengths, with Interpreter significantly underrepresented. This matters: the rarest strength — translating UX to business value — is often the one organizations need most. If the Interpreter isn't your natural strength, it's the one most worth developing.

Vision Definition Foundation

Use when: you need to articulate where you're going before you can get others to follow.

A vision is an impactful, future-state view of the experience users will have with a product or organization. Good visions are: attainable (aspirational yet in reach), experience-focused (connected to users, not technology), specific (tailored to the product and users, not generic), research-based (grounded in what you've learned from users), practical (pragmatic yet impactful), and shared (communicated across the entire team or company). A good vision statement addresses three elements: the target customer (the who), the benefit or need addressed (the why), and what makes it unique (how it's different).

Visions fail when: there's no buy-in or stakeholder alignment, the vision is too generic (could apply to any product), there's no champion keeping it alive, or there's no plan to deliver it. Without a plan, a vision is just words.

UX Team Vision Core Method

Use when: you don't have a say in the company vision but want to define your team's purpose and direction.

A company vision answers: "What impact do I want my brand to have on my community/industry/world? How will my brand ultimately interact with customers?" A UX team vision answers a different question: "What impact do I want my team to have on my company/product/users? How will my team ultimately interact with other teams and stakeholders?" You can create a UX team vision even when the broader organization hasn't articulated one.

Example: "We own and continually improve the design system, enabling product teams to innovate, learn, and deliver with optimal speed and quality." This identifies the who (product teams), the why (to make them more effective), and the how it's different (a living design system, not rigid page-based templates).

Shared Vision Process (Three-Step) Core Method

Use when: creating a vision collaboratively rather than dictating one from the top. Especially valuable for cross-functional teams.

Three steps, each with a distinct goal and output:

Step 1 — Planning. Goal: understand the current state by bringing stakeholders together. Activities: cross-functional and stakeholder interviews, exploratory user research (interviews, diary studies, field studies). Output: an experience brief that captures current challenges, objectives, and existing research insights. The experience brief is the foundation — it ensures the vision is grounded in reality, not aspirations.

Step 2 — Visioning. Goal: create a research-backed vision the team can rally around. Activities: a visioning workshop where the team reviews the experience brief, answers a focus question ("Why do we exist?" / "What's our ideal state?" / "Where do we want to be?"), clusters responses into themes, crafts vision options from themes, and dot-votes on a winner. Output: a vision statement.

Step 3 — Prioritization. Goal: make a plan for how to achieve the vision over time. Activities: a prioritization workshop where the team recaps the vision, sketches ideas for achieving it, assigns priority (must-have / should-have / could-have), and fills out a skeleton roadmap. Output: incremental steps mapped and ranked by importance, connected to objectives and key results.

Vision Board Technique

Use when: you need a shareable artifact that keeps the vision visible and actionable.

A vision board is a one-page artifact that captures: the vision statement, the target group, the needs being addressed, the product direction, and the business goals. It serves as a reference point for daily decisions — when evaluating any feature, initiative, or design direction, ask: "Is this moving us closer or farther away from the vision?" Post it where the team can see it. A vision that lives in a slide deck nobody opens is not a shared vision.

Make Your Work Visible Practice

Use when: the organization doesn't understand what UX does or why it matters.

Visibility creates understanding, and understanding creates support. Three tactics: Bring people into your research. Invite PMs, engineers, and executives to observe usability tests. Nothing evangelizes UX faster than watching a real user struggle with something the team assumed was intuitive. Hold company-wide meetings to share insights. Not formal presentations — informal show-and-tell sessions where you share what you learned, what surprised you, and what it means for the product. Set aside recurring time for video clips. A weekly or bi-weekly "highlight reel" slot where the team watches 5 minutes of real user sessions. Over time, this builds an organizational habit of caring about user experience.

Share the Ownership of UX Practice

Use when: UX is treated as one team's responsibility rather than a shared organizational value.

Don't limit UX participation to the C-suite. Involve people across the organization in design work: design studios and workshops, critiques and artifact discussions, usability testing observation, and ethnographic research. When a product manager helps analyze usability test results, they become an advocate for the next round of testing. When an engineer observes a user struggling with a feature they built, they care more about the fix. Shared ownership means shared advocacy.

UX Community of Practice Core Method

Use when: you want to create ongoing organizational momentum for UX beyond individual projects.

A UX community of practice is a regular, informal gathering where UX practitioners and interested colleagues share projects, discuss issues, and ask questions. It serves multiple purposes: skill-sharing across projects, pattern recognition across the product portfolio, consistent advocacy for UX standards, and a support network for practitioners who may be the only UX person on their team. Meet regularly — biweekly or monthly — in an informal setting. The community of practice is the engine of UX culture; it sustains momentum between the big wins.

Transactional vs. Transformational UX Leadership Framework

Use when: evaluating your leadership approach and deciding how to grow your impact.

Transactional UX leadership focuses on managing and supervising: monitoring individual work against expected standards, promoting success through rewards and punishments contingent on performance, and working within existing structures to shape work according to the current culture. This keeps the lights on but doesn't change anything.

Transformational UX leadership focuses on growth and change: paying individualized attention to meeting the needs of the team, stimulating ideas and creativity through a safe environment where people can challenge the status quo, providing a vision that inspires and motivates others to achieve important goals, and role-modeling behaviors that help others identify with a shared vision. Transformational leaders create UX culture; transactional leaders maintain it. Both are necessary — but if your organization's UX maturity is low, transformational leadership is what moves the needle.

UX Leader Self-Evaluation Self-Assessment

Use when: you want to identify habits that are holding you back from being an effective UX leader.

Bad habits that undermine UX leadership: Being out of touch with your work, projects, achievements, and failures.

• Managing up over managing across — gravitating toward high-visibility projects and executive attention rather than investing in your team's success. Dismissing people or always having to offer your answer, assuming it's the right one.
• Believing you have to do it yourself — not trusting your team to get the job done.
• Requiring excessive reporting — your team produces artifacts primarily to quench your thirst for details, not to advance the work.
• Shifting priorities constantly — regularly redirecting people's work day-to-day without stable direction.

The antidote: become a thought partner, not a gatekeeper. Nurture and share new ideas. Let peers tell you how you're doing. Make sure everyone has the same information you have. Actively remove obstacles instead of creating them.

Personal Action Plan Technique

Use when: translating self-awareness into deliberate growth as a UX leader.

Ask yourself eight questions: What kind of work do I want to be doing? What kind of team do I want to work with? What kinds of products or experiences do I want to create? What do I want my success stories to be? Who do I want my allies and friends to be? What kind of education do I want to have? How do I want to work? What kind of culture do I want to be part of? Then assess your organization against the six pillars of great UX. Color in each pillar based on your honest assessment. Where the gaps are is where UX leadership — your leadership — can make the biggest difference. Make a plan for this week, this month, and this year.

UX Charisma Practices Practice

Use when: you want to become someone people naturally follow and trust.

Charisma in a UX context isn't about personality — it's about behavior. Six practices: Listen more than you talk. Charismatic people listen closely to everyone and make others feel like they have something in common with them. Don't practice selective hearing. Maintain eye contact, respond non-verbally (smile, frown, nod), and show you're engaged even when you disagree. Choose your attitude and your words. The words you use affect others' attitudes — speak with intention. Don't discuss the failings of others, but admit your own. If you criticize others, people wonder if you also criticize them behind their back. Admitting your own mistakes builds trust. Ask questions. Questions are a key driver of effective leadership — they create clarity, promote honesty, construct better relationships, attract evidence, and allow for uncertainty before discovery. Cultivate curiosity. Innovation is the result of thoughtfulness, not inspiration. Practice asking the right questions upfront. There's power in asking "What if?"