Who Needs to Be Heard? A Facilitator’s Guide to Stakeholder Discovery Before Designing the Work

Every experienced consultant has walked into an engagement where the sponsor’s brief and the organization’s reality live in different worlds.

The sponsor requests a workshop to “accelerate digital adoption.” Frontline teams are exhausted from three failed rollouts in eighteen months.

The sponsor asks for “strategic alignment on priorities.” The operations team knows the legacy architecture cannot reliably support the proposed targets.

The sponsor wants a culture or communication intervention. People closer to the work know that unclear decision rights, understaffing, or unresolved cross-team dependencies are the more immediate problems.

When you design an engagement solely from the sponsor’s narrative, you can inherit the structural blind spots built into that narrative.

A stakeholder is any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by an outcome. That definition is broad by design. It prevents discovery from beginning and ending with the executive who signed the contract.

The stakeholder map is therefore not just a map of the organization chart. It is a map of the wider system of relationships, dependencies, knowledge, authority, and consequences surrounding the work.

The challenge is not simply listing names. It is deciding whose experience, practical knowledge, and exposure to consequences should shape the intervention before you design a single session.

A stakeholder is more than a decision-maker

In corporate environments, “stakeholder” can quietly become shorthand for senior leaders with budget and approval rights. Those voices are essential. They often control resources, define boundaries, establish priorities, and determine whether recommendations survive beyond the workshop.

They are not, however, the only people with a stake.

A more complete inquiry includes people who:

• Carry implementation responsibility: The teams tasked with translating executive concepts into daily workflows, systems, services, and handoffs.
• Possess historical and technical memory: Long-tenured staff and specialists who understand informal workarounds, legacy dependencies, previous attempts, and why earlier initiatives stalled.
• Absorb downstream consequences: Frontline employees, customer-facing staff, adjacent teams, users, or partners who bear the friction of a decision without holding formal power.
• Hold informal network influence: Trusted peers, local leaders, coordinators, and people whose support or skepticism shapes whether an initiative becomes real in practice.
• See the work from a different position: People whose role, location, employment status, professional background, or relationship to the organization gives them visibility into issues the sponsor cannot readily see.

Stakeholder identification is not merely an exercise in political risk mitigation. It is a diagnostic discipline:

Who sees a part of this situation that leadership, sponsors, or the planning group cannot see from where they sit?

That question changes the purpose of discovery. The goal is not to collect as many opinions as possible. It is to build a sufficiently rich and responsible account of the situation to decide what kind of work is actually needed.

Five lenses for mapping the system

No stakeholder framework can determine, by itself, who needs to be heard. Each reveals something important and introduces its own blind spots.

Use the following five lenses together. They are not competing theories. They are ways of widening the initial map before choosing who to involve, how to listen, and what their input can meaningfully influence.

1. The affected and affecting lens

Begin with the broadest question:

Who is affected by this situation or proposed intervention, and who can affect what happens next?

This initial scan helps ensure that the stakeholder map does not merely reproduce the formal organization chart.

This lens produces a deliberately broad list. It is a starting point, not yet an interview schedule or workshop invitation list.

Its value is that it surfaces people who may be missing from the sponsor’s first account: people who will do the implementation, experience the consequences, or possess information that is not visible at senior levels.

2. The power–interest grid, with guardrails

The power–interest grid is a familiar way to map political and governance dynamics. It asks:

1. How much influence does this person or group have over the work?
2. How much interest do they have in its outcome?

That can be useful for understanding how decisions will be made, where sponsorship is needed, and what may constrain the work.

The power–interest lens has a major limitation: it explains governance authority, but it should never decide whose perspective matters.

Low-power, high-interest groups often experience the consequences most directly. They may hold practical knowledge that senior decision-makers do not have: workarounds, failed handoffs, customer tensions, staffing constraints, or the effects of previous change efforts.

Use the power–interest grid to understand decision dynamics. Do not use it as an excuse to exclude people whose experience is less powerful but highly relevant.

3. Stakeholder salience: power, legitimacy, and urgency

The stakeholder-salience framework associated with Mitchell, Agle, and Wood considers the attributes that influence how decision-makers prioritize stakeholder claims:

• Power: The ability to direct resources, influence decisions, or enforce compliance.
• Legitimacy: Whether a stakeholder has a valid and appropriate claim to be considered.
• Urgency: Whether a concern is time-sensitive, critical, or difficult to defer.

For facilitators and consultants, its value is not that it tells us who “matters most.” Its value is that it makes a difficult question visible:

Whose concern is legitimate and urgent for the people living it, but easy for leadership to overlook because those people lack structural power?

A frontline team may have limited formal authority but face immediate workload, safety, service-quality, or customer-impact consequences. A customer group may have a legitimate claim but little access to internal decision-making. A compliance or security concern may be urgent even before it has become visible to senior leaders.

There is also an important caution. Legitimacy and urgency are often judged by people who already hold power. An organization may treat an inconvenient claim as less legitimate precisely because it challenges established priorities.

Use this lens to notice whose concerns may be institutionally discounted—not to ratify the organization’s existing hierarchy of attention.

4. The whole-system view: ARE IN

In the Future Search approach developed by Marvin Weisbord and Sandra Janoff, a “whole system” is represented through people with Authority, Resources, Expertise, Information, and Need—often remembered as ARE IN.

ARE IN is not a complete stakeholder-analysis model. It is a practical whole-system representation principle: a way to check whether the perspectives needed to understand and act on an issue are present.

A group may represent more than one dimension. A team lead may have authority, expertise, and information. A technical owner may hold authority over a system, expertise in its constraints, and control over resources. A customer may bring both need and information.

The point is not to place people into a single box. The point is to ask:

Which of these forms of perspective are absent from the current account of the situation?

A sponsor group may represent authority and resources well while lacking direct information about everyday work or exposure to the consequences of a change. ARE IN makes that imbalance easier to see.

5. The listening-gap lens

Every framework produces omissions. The listening-gap lens is how you test the map after applying the other four.

Ask:

• What would we fail to understand if this perspective were absent?
• Who experiences the work daily rather than discussing it from a distance?
• Who knows the informal workarounds, exceptions, history, or dependencies?
• Who bears the consequences of decisions without holding much power over them?
• Whose account might challenge the sponsor’s initial explanation?
• Which groups are being treated as homogeneous despite having different interests or experiences?
• Who may be absent because of language, location, shift patterns, disability, technology access, employment status, confidence, or fear of repercussions?
• Who else would the people already identified say needs to be heard?

This final question is particularly valuable:

“Whose perspective is important to understanding this situation and may not yet be represented?”

Include it in stakeholder interviews, sponsor conversations, and any early survey. It makes stakeholder discovery iterative rather than fixed by the sponsor’s first list.

Comparing the frameworks

Each lens has a different purpose. Using them together gives a more balanced inquiry map.

The result should not be a perfect or exhaustive map. That is rarely possible.

The goal is a proportionate and defensible listening plan: one that makes clear why certain perspectives are being sought, what they may reveal, what participation conditions they require, and what their input can influence.

From stakeholder map to listening plan

A stakeholder map identifies possible perspectives. A listening plan makes deliberate choices about what to do next.

For each stakeholder group or perspective, record:

This avoids two common errors:

• Treating every stakeholder in exactly the same way.
• Restricting discovery to whoever is most senior, easiest to schedule, or already close to the sponsor.

Not every relevant group needs the same method. Some perspectives need a confidential conversation. Some require a process walkthrough or observation. Some can be heard effectively through a short written inquiry. Some need to participate directly in the workshop or in a later decision process.

The method should follow the question, the context, the power dynamics, and the conditions required for people to participate meaningfully.

Choosing a listening method

A survey can help you hear broadly across a stakeholder map, but it is not always the most appropriate first or only method.

The aim is not to treat surveys, interviews, observation, and dialogue as interchangeable. Each produces a different kind of knowledge. A responsible discovery process combines methods where the situation requires it.

Example: before an “alignment” workshop

A sponsor asks for a workshop because product and customer-success teams are “misaligned.”

The initial participant list includes senior leaders, product managers, and customer-success managers. That list contains meaningful authority and expertise. But applying the other lenses reveals important gaps:

A short written inquiry invites input from a broader cross-section. The responses suggest that the central issue is not simply alignment. Customer-facing teams are making commitments without a reliable escalation path, while product teams lack visibility into account risk and technical dependencies.

The workshop is redesigned. Instead of a broad discussion about alignment, it focuses on decision rights, escalation criteria, customer commitments, and cross-functional routines.

The written inquiry did not replace the workshop. It made the workshop more honest about the conditions it needed to address.

The ARE IN question bank

When collecting qualitative accounts, adapt questions to the kind of perspective a participant can bring. Do not ask people to self-identify as one ARE IN category; most participants represent more than one.

For authority and resources

• What non-negotiable business constraints—such as budget, timeline, regulatory obligations, or strategic commitments—must this engagement respect?
• What decision are you hoping this process will clarify that you cannot unilaterally make today?
• What capacity, resource, or governance constraint could prevent a good idea from being implemented?
• Which decisions are genuinely open, and which have already been made?

For expertise

• Where is the organization building plans on technical, operational, or professional assumptions that have failed in past iterations?
• What structural dependencies are being treated as simple details when they are actually core risks?
• What would a well-intentioned outsider be most likely to misunderstand about this work?
• What knowledge is essential to a responsible intervention but is not yet present in the planning group?

For information

• Think of a recent situation where getting simple work done required an unofficial workaround. What happened?
• What is the most common reason a handoff stalls between your team and adjacent departments?
• What patterns, exceptions, or recurring problems are visible in day-to-day work but absent from formal plans or reports?
• What do people in other roles tend not to see about how this work actually gets done?

For need

• If this initiative succeeds exactly as leadership envisions, what new workload, risk, or friction could it create in your day-to-day work?
• What is one thing you worry leadership may overlook while focusing on high-level goals?
• What would a responsible outcome need to protect, improve, or avoid making worse?
• What would make participation in this process feel worthwhile to you?

Cross-cutting questions

These questions work across the stakeholder map:

• What is working today that this engagement should avoid disrupting?
• What do you most want the people designing this work to understand before making decisions?
• Whose perspective would materially change how we understand this issue?
• What question have we not asked that we should?
• Is there anything you would prefer to discuss in a confidential follow-up conversation?

Cerne as a first listening layer

Consultants often face a practical constraint: a client system may contain dozens of people with relevant experience, while the engagement budget permits only a handful of interviews.

Under pressure, discovery narrows to the sponsor, a small leadership group, and the people easiest to schedule. That is understandable. It is also one of the ways an incomplete initial brief becomes embedded in the design.

A structured Cerne inquiry gives facilitators and consultants a way to listen broadly before deciding where to go deeper.

Invite a cross-section of people identified through the stakeholder map—across authority, resources, expertise, information, and need—to share short written accounts of what they experience, what constrains the work, what is already functioning, and what the process needs to understand.

The aim is not to replace interviews, observation, dialogue, co-design, or shared decision-making. It is to widen the initial field of evidence.

Hear beyond the planning group

Use Cerne to invite input from people who may not be in the workshop or available for an individual interview:

• Frontline staff and operational teams
• Technical and subject-matter specialists
• Managers responsible for implementation
• Customer-facing and service teams
• Sponsors and decision-makers
• Partners, users, or other affected groups, where appropriate

A written inquiry can give participants time to reflect. It can also create a lower-pressure way to share experiences that may be difficult to raise in front of managers, sponsors, or peers.

Before inviting people, be clear about:

• Why their perspective is being sought
• How their responses will be used
• Whether responses are confidential or anonymous
• What identifying information, if any, is being collected
• Who will have access to the responses
• What follow-up participants can expect

Do not describe an inquiry as anonymous unless it genuinely does not collect information that can identify a respondent. Confidentiality and anonymity are different commitments, with different implications for trust and follow-up.

Look for patterns, differences, and unanswered questions

Do not reduce stakeholder responses to a list of “top themes.”

Review the material for:

• Recurring experiences and constraints
• Differences between roles, teams, or relationships to the work
• Practical exceptions and informal workarounds
• Risks that the sponsor’s original brief did not name
• Questions that require an interview, group dialogue, observation, or document review
• Additional stakeholders respondents believe should be heard
• What participants say is already working and should be preserved

Where you collect contextual information—such as team, role, location, or tenure—explain why it is being collected, how it will be used, and how you will avoid making people identifiable within a small group.

The aim is not to claim that the survey has “proved” a diagnosis. It is to identify where the sponsor’s framing has been strengthened, complicated, or challenged.

Revisit the sponsor brief

A useful sponsor readout might say:

“The initial brief described an alignment problem. Across the responses, participants also described unclear decision rights, unresolved technical dependencies, and uncertainty about customer commitments. Before designing an alignment workshop, we should determine whether these operating constraints need to be addressed directly.”

This is not a claim that one group is right and another is wrong. It is an invitation to examine differences in experience, visibility, and responsibility.

The conversation can then move away from “Who is resisting change?” and toward better questions:

• What conditions are creating the friction?
• Which trade-offs have not been made explicit?
• What decision rights need clarification?
• What practical constraints must shape the intervention?
• Who needs to be involved in the next stage of inquiry or design?

Decide what needs deeper listening

The output of a Cerne inquiry is not merely a summary. It is a better next question.

The responses may show that the workshop should include different people, address a different decision, be preceded by interviews, or be replaced with another intervention altogether.

That is not a failure of the original plan. It is stakeholder discovery doing its job.

Ground your design in the system

A workshop or consulting project is only as sound as the context used to design it.

When you map stakeholders through several lenses—and listen across authority, resources, expertise, information, and need—you reduce the risk of designing from top-down assumptions alone.

You begin with a more grounded account of the terrain:

• What people experience
• Where perspectives diverge
• What is already working
• Which constraints are real
• What remains uncertain
• What the intervention must take seriously

Cerne can help you create that first layer of listening: map the perspectives you need, invite a broader inquiry, and use what you hear to design better questions for the work ahead.