SkillsStakeholders

Stakeholder Landscape Mapper

Read where they stand. Detect what is not spoken. Decide what to do next.

The problem

Six weeks into a global SAP S/4HANA rollout across 14 countries. Three executive sponsors. Two works councils with legal consultation rights. And two stakeholders who are nodding in steering meetings while quietly working against the program.

This is exactly the kind of high-stakes, time-pressured scenario that Stakeholder Landscape Mapper was built for. Not a generic prompt. A specialist tool with the methodology, the frameworks, and the professional judgment encoded into every output.

What makes this different

Hidden Resistance Detection™

Scans your input data against the Six Resistance Tells: the Disengagement Drop, the Compliance Pivot, the Delegation Shift, the Workaround Sign, the Vague Endorsement, and the Conditional Yes. When two or more fire on the same stakeholder, they're designated with a dashed line on the map. The dashed line shows exactly where silent risk lives.

Signal-to-Map Translation™

Converts direct quotes from interview notes and survey responses into mappable insight plus named, time-bound interventions. Seven translation categories covering historical signals, influencer signals, capacity, conflict, trust, workload, and identity. Every stakeholder gets at least one.

Three Operating Modes

Mode A processes data you already have. Mode B generates the stakeholder survey when you need to send one out. Mode C generates discussion questions for working sessions and 1:1s. One Skill, three workflows that match how change managers actually work.

Confidentiality Architecture

Built-in three-tier output system with explicit distribution warnings. Tier 1 confidential map for CM, sponsor, and key project leads. Tier 2 sanitized summary for steering committees. Tier 3 departmental engagement note for individual leaders.

See it in action

Global ERP Implementation

Six weeks into a global SAP S/4HANA rollout across 14 countries. Three executive sponsors. Two works councils with legal consultation rights. And two stakeholders who are nodding in steering meetings while quietly working against the program.

Example prompt

Map the full stakeholder landscape for our SAP S/4HANA rollout. 1,200 employees across 14 countries. Six stakeholder groups: (1) Senior Leadership Team (12 people, 2 suspected covert resistors), (2) Works Councils (2 bodies, Germany + France), (3) Corporate Functions (80 people), (4) Middle Managers (45 people), (5) Operations Staff (400 people), (6) Customer-Facing Teams (300 people). The organization went through redundancies 18 months ago that were handled poorly. Workforce optimization review running concurrently. Audience: me, CHRO, program director. Tier 1 confidential.

Keep SatisfiedManage CloselyMonitorKeep InformedPOWERHighLowINTERESTLowHighWCSLT2CFMMOPSCX

Legend

WCWorks Councils (2 bodies, legal rights)
SLTSenior Leadership (12 people)
CFCorporate Functions (80 people)
MMMiddle Managers (45 people)
OPSOperations Staff (400 people)
CXCustomer-Facing (300 people)

Dashed-Line Designations

SLT (2 of 12 members)

Hidden Resistance Detection fired. Three Tells on the same two members. Designated covert resistors.

Customer-Facing (full group)

Disengagement Drop firing with extreme intensity. 4 weeks of complete silence from 300 people.

Change Essentials AI | Stakeholder Landscape Mapper v2.0Section A · Grid

What standard Claude produces

Group assessments

Senior Leadership Team, 12 people

Your most urgent problem. Two sponsors performing alignment in meetings while actively undermining the program outside them is a governance failure. The rest of the SLT is watching what happens to them. Name the behavior directly in private conversation, offer a genuine off-ramp, and give it two weeks. If nothing changes, escalate formally; their continued dual role is a program-level risk.

Middle Managers, 45 people.

The most underestimated group. They translate every executive message into what 700+ people actually believe. Many survived the last redundancy round and are now pattern-matching for who's next. Flight risk is real and silent. Brief this group before all-staff, with more candor. Identify 5-7 informal leaders within the cohort and engage them separately.

Operations Staff, 400 people.

Hardest hit by the prior round, longest institutional memory. Expect deep distrust of formal channels and heavy reliance on informal networks. Don't let all-staff communications be their primary channel; they'll discount it. Design listening sessions, not briefings. Acknowledge the prior redundancy handling explicitly before they raise it.

Corporate Functions, 80 people.

Watchful rather than resistant. The risk is passive blockage, slow sign-offs and quiet non-participation framed as capacity constraints. HR is under particular pressure, acting simultaneously as change agents, process owners, and personally affected employees.

Customer-Facing Teams, 300 people.

Internal uncertainty travels directly into customer interactions. If this group disengages, service quality degrades visibly and measurably. Treat silence as withdrawal, not acceptance. Monitor service metrics as your leading indicator of engagement health.

What's running beneath the surface.

The 18-month shadow. This workforce remembers who found out informally, which managers protected their people, and what promises weren't kept. Any communication pattern that echoes those failures will be decoded as confirmation history is repeating. Name the prior handling explicitly, and name what will be different this time.

The works councils. Two councils with legal consultation rights are a governance asset most programs under-use. Engage chairs before any broader communication. If they're onside, they become credibility assets. If they feel bypassed, they have the mandate and mechanism to slow or block.

The informal network. Six weeks in, speculation is already filling the vacuum. Around 8-15 people across your organization shape what others believe, rarely the most senior. Map them, brief them early with more candor than the all-staff message, and they'll carry that credibility into conversations you'll never be in.

Sequencing: non-negotiable.

Works councils → SLT → Middle managers → All staff.

Anyone who learns from an all-staff message before their manager has briefed them has already lost trust in the process. The sequence is the message.

Standard engagement advice. Nothing about which specific SLT members are silently undermining the program, or that the Customer-Facing silence is a Disengagement Drop pattern, not consent.

What Stakeholder Landscape Mapper produces

Hidden Blocker: SLT Covert Resistors (2 of 12 members).

Surface behavior: Suddenly green in steering meetings starting Week 4. Verbal support in every meeting. Both have started sending direct reports to working sessions instead of attending themselves.

Tells firing: Compliance Pivot + Vague Endorsement + Delegation Shift. Three Tells on the same two members. Designated with a dashed line on the map.

Risk vector: They will not block publicly. They will quietly remove resources from the program, slow-walk decisions in their function, and shape the steering narrative away from accountability. Coalition risk with Middle Managers reporting to them.

Hidden Risk: Customer-Facing Teams (300 people, full group).

Surface behavior: Zero questions submitted in the anonymous channel for four consecutive weeks. Zero requested attendance at optional briefings. Silent.

Tells firing: Disengagement Drop, firing with extreme intensity and duration. Override clause applies for single-Tell designation when severity is extreme.

Risk vector: Silence in a high-impact change is not adoption. It is withdrawal. If this group is silent at go-live, service quality degrades visibly and measurably to customers in the first 48 hours. HR is under particular pressure, acting simultaneously as change agents, process owners, and personally affected employees.

Customer-Facing Teams, 300 people.

Internal uncertainty travels directly into customer interactions. If this group disengages, service quality degrades visibly and measurably. Treat silence as withdrawal, not acceptance. Monitor service metrics as your leading indicator of engagement health.

What's running beneath the surface.

The 18-month memory. This workforce remembers who found out informally, which managers protected their people, and what promises weren't kept. Any communication pattern that echoes those failures will be decoded as confirmation history is repeating. Name the prior handling explicitly, and name what will be different this time.

The works councils. Two councils with legal consultation rights are a governance asset most programs under-use. Engage chairs before any broader communication. If they're onside, they become credibility assets. If they feel bypassed, they have the mandate and mechanism to slow or block.

The informal network. Six weeks in, speculation is already filling the vacuum. Around 8-15 people across your organization shape what others believe, rarely the most senior. Map them, brief them early with more candor than the all-staff message, and they'll carry that credibility into conversations you'll never be in.

Sequencing: non-negotiable.

Works councils → SLT → Middle managers → All staff.

Anyone who learns from an all-staff message before their manager has briefed them has already lost trust in the process. The sequence is the message.

Power-Interest grid generated with dashed-line designations on Hidden Blockers. Signal-to-Map Translation surfaces what each stakeholder is protecting, not just that they are resistant. Legal risk flagged before it becomes a go-live injunction. Three-tier Confidentiality Architecture applied. 15-slide deck with named, time-bound interventions.

Notice how Hidden Resistance Detection catches what a standard grid misses: two SLT members are nodding in steering while three Resistance Tells fire on each of them (Compliance Pivot, Vague Endorsement, Delegation Shift). And 300 Customer-Facing employees have asked zero questions in four weeks about a system that changes how they work. Two dashed-line designations. Two completely different patterns of silent risk. Both invisible on the standard grid.

The difference specialist methodology makes

Same scenario. Same prompt context. Different results.

Standard Claude
Stakeholder Landscape Mapper
Stakeholder identification
Surface-level org chart mapping. Named groups in quadrants.
Power-Interest Grid with Adapter Style designation. Hidden Blockers surfaced via Hidden Resistance Detection.
Resistance detection
Flags obvious resistors. 'High resistance noted.'
Scans against the Six Resistance Tells. Dashed-line designation on the map shows exactly where silent risk lives.
Signal interpretation
Repeats what stakeholders said back to you.
Signal-to-Map Translation converts direct quotes into named, time-bound interventions across seven translation categories.
Output confidentiality
No confidentiality model. One map for everyone.
Three-tier Confidentiality Architecture. Tier 1 confidential map, Tier 2 sanitized sponsor summary, Tier 3 departmental engagement note.
Lifecycle use
One-time analysis. Map goes stale within weeks.
Reassessment Triggers with Movement Tracking. Re-run as phase milestones, personnel events, or signal collapses occur.

Who benefits from access to this skill

For in-house corporate change teams

1

Change manager

Build the confidential stakeholder map. Detect hidden resistance. Translate every interview signal into named, time-bound interventions. Re-run as the change progresses.

2

Project lead

Use Mode C in working sessions to extract stakeholder intel from your project team. See exactly where stakeholders sit relative to project milestones.

For consulting firms

This skill supports consulting firm practitioners working on change management, post-merger integration (PMI), technology and ERP implementations, and AI adoption programs.

Global Ready

80+ languages.
Zero extra cost.

80+

Languages

100%

Cultural context

$0

Extra cost

This skill works in over 80 languages out of the box. Prompt in English, get output in Japanese. Prompt in Portuguese, get output in Arabic.

Cultural context is maintained, not just word translation. The skill adjusts its frameworks, its tone, and its output for the culture you’re working in, not just the language.

No add-ons. No language packs. It just works.