Understanding Stakeholders and Their Needs

Introduction

In our last lesson, we established that effective UX strategy is the bridge connecting user needs with business goals. We saw how your design work fits into the bigger picture of a company's objectives. Now, we'll get practical about navigating that bigger picture. To build that bridge, you first need to know who is on the "business" side of the chasm.

This lesson focuses on answering the question: Who are the key people involved in a project, and what do they need? This is the focus of today's learning outcome: to identify key stakeholders and their needs in a UX project.

We will cover:

• What defines a "stakeholder" in a UX context.
• How to brainstorm and identify the different people and groups who have a stake in your project.
• How to use strategic frameworks, called stakeholder maps, to prioritize them.
• Why understanding their individual needs, goals, and concerns is crucial for success.

This process of identification and analysis is a foundational skill that separates senior designers from junior ones. It’s the first step in gathering the business requirements that will shape your entire design process.

Who is a Stakeholder?

First, let's establish a clear definition. A stakeholder is not just your boss or the client. It's much broader than that.

A stakeholder is any person, group, or individual who can affect or is affected by your design project. They might have power over the project (like a project sponsor), or they might simply be impacted by its outcome (like a customer support agent who will have to field calls about the new feature you're designing).

To begin identifying them, it's helpful to read a clear definition and see a list of common examples.

As the article suggests, brainstorming is a crucial first step. You cast a wide net to ensure no one is overlooked. Your list could include internal stakeholders (like product managers, engineers, marketers, and C-suite executives) and external ones (like end-users, partners, or even regulators).

Prioritizing Stakeholders with Mapping

Once you have a long list of potential stakeholders, you'll quickly realize that you can't engage with all of them equally. Your time and energy are finite. The next step is to prioritize. This is where stakeholder mapping comes in. A stakeholder map is a visual tool used to categorize stakeholders and plan how to engage with them.

The Power/Interest Matrix

One of the most common and effective frameworks is the Power/Interest Matrix. It plots stakeholders on two axes:

• Power/Influence: How much control or influence do they have over the project's success? Can they stop the project, approve budgets, or make key decisions?
• Interest: How much are they invested in or affected by the project's outcome?

This creates four quadrants, each with a specific engagement strategy.

To see how this works in practice, let's watch a short video that walks through the matrix.

To summarize the strategies:

• Manage Closely (High Power, High Interest): These are your key players (e.g., project sponsor, your direct manager). You need to collaborate with them closely and keep them fully engaged.
• Keep Satisfied (High Power, Low Interest): These stakeholders have significant influence but may not be involved in the day-to-day details (e.g., a CEO or head of a department). Your goal is to keep them satisfied with the project's progress without overwhelming them with information.
• Keep Informed (Low Power, High Interest): This group is passionate about the project but lacks decision-making power (e.g., end-users who champion the product, designers from other teams). Keep them in the loop about what's happening; they can be valuable allies and sources of feedback.
• Monitor (Low Power, Low Interest): These stakeholders are on the periphery. Keep an eye on them in case their interest or influence changes, but don't overload them with communication.

A Simpler Model: Core, Direct, Indirect

Another useful, and often faster, way to categorize stakeholders is by their proximity to the project. This model uses three concentric circles.

This model provides a clear hierarchy for communication:

• Core: The small group of people for whom this project is their primary focus (e.g., your direct team: product manager, tech lead). They require high-frequency, high-touch communication.
• Direct: People who are involved regularly, but the project isn't their sole focus (e.g., an engineering manager, a product marketing manager). They have a direct relationship with the project and need frequent updates.
• Indirect: People who need to be kept informed but are not involved in day-to-day decisions (e.g., a CTO, a company founder). They require low-frequency, low-touch communication, like a monthly demo or an email update.

Choosing between these two models depends on your project's context. The Power/Interest matrix is excellent for politically complex environments, while the Core/Direct/Indirect model is great for quickly clarifying communication lines within a team and organization.

Understanding Stakeholder Needs

Identifying and prioritizing stakeholders is only half the battle. To truly align with the business, you must understand their needs. What does "success" look like to the head of marketing versus the head of engineering? What are their hopes and fears for this project?

This moves beyond just identifying who they are to understanding what they care about. The Nielsen Norman Group provides excellent guidance on this.

As the article outlines, understanding a stakeholder's needs involves uncovering their:

• Goals and Motivations: What do they want to achieve with this project?
• Key Concerns: What are they worried about? What do they see as potential risks?
• Success Metrics: How will they judge whether the project is a success?
• Communication Preferences: Do they prefer a weekly email, a bi-weekly meeting, or a quick Slack message?

Documenting this information in a stakeholder profile or an engagement plan turns your analysis into an actionable strategy that your whole team can use. This document ensures that your communication is tailored, effective, and builds strong working relationships.

Conclusion

In this lesson, we demystified the process of stakeholder management. You learned that it's a systematic process of identifying, prioritizing, and understanding the key people involved in your project.

Key Takeaways:

• Stakeholders are anyone with an interest in or influence over your project, both internal and external.
• Stakeholder mapping is a critical tool for prioritizing your engagement efforts. The Power/Interest matrix and the Core/Direct/Indirect model are two powerful frameworks for this.
• Prioritization allows you to focus your energy on the people who matter most to the project's success.
• It's not enough to know who your stakeholders are; you must also understand their unique needs, goals, and concerns to effectively align your design work with business objectives.

You now have the frameworks to map out the human landscape of any project. In our next lesson, we will put this knowledge into action. We'll learn how to conduct a stakeholder interview to effectively gather those needs, requirements, and constraints that will form the foundation of your UX strategy.