Formal authority / power
Can this person approve, veto, resource or materially alter this specific decision?
Decision alignment tool
Stakeholder Map Builder
Map who matters around one product decision, distinguish formal authority from informal influence and impact, record what is known versus assumed, then turn the map into concrete engagement actions and commitments.
Decision Influence Map
Power–Interest, Influence–Impact and direct onion proximity without mixing the models.
Stakeholder Alignment Audit
Find missing authority, untested assumptions, engagement gaps, unresolved concerns and action hygiene.
Action + review loop
Capture asks, evidence, owners, due dates, relationships and bounded snapshots as the landscape changes.
No login. Autosaves in your browser. Internal share links contain compressed map data and are not encrypted; use the external-safe mode when you need a sanitized artifact.
1. Decision context
Assess every stakeholder relative to one concrete decision or initiative.
Internal working map. The share link contains the stakeholder-map data. Anyone with the link can inspect it. It is not encrypted. Use external-safe mode when internal judgments should not leave the working team.
Load illustrative example:Examples use fictional names/data and demonstrate judgment, not target stakeholder counts.
Stakeholder Alignment Audit
What is missing or fragile in this decision-alignment strategy? No overall score.
- fail · decision, Decision context is missing. Name the initiative and the specific decision before treating stakeholder assessments as meaningful.
Decision Influence Map
Power–Interest stays recognizable; decision role, support, informal influence and impact live in the assessment, not extra axes.
Keep informed
Manage closely
Monitor
Keep satisfied
Relationships and dependencies
Map who influences whom or where approval, trust, work and unresolved tension flow. These notes stay out of external-safe sharing.
Review loop and history
Save bounded snapshots without recursively copying previous history. Use notes to record what changed, not to invent why it changed.
From contact list to decision alignment
- Define the initiative and the decision. Add the people or groups who can approve, influence, implement, constrain or be materially affected.
- Assess formal authority, interest, informal influence, impact, decision role, current support and the evidence behind those judgments. Keep unknowns explicitly unknown.
- Use the Stakeholder Alignment Audit, relationship map and current-versus-required engagement gaps to choose the next conversation, ask, owner and due date. Review the map as the decision changes.
Separate the dimensions that teams usually blur together
Informal influence
Whose judgment do other stakeholders follow, regardless of title?
Impact on the stakeholder
How strongly will the decision affect this person or group? Low authority does not mean low importance.
Decision role + evidence basis
Record who drives, approves, contributes, implements or is affected, and whether the assessment comes from authority, observation, conversation, second-hand evidence or assumption.
Current involvement is not the same as required involvement
The tool compares current and required engagement for each stakeholder. An approver who is only informed has an approval gap; an affected group that should be consulted has a consultation gap; a stakeholder already at the required level does not need a manufactured action.
Map influence and dependency paths
Stakeholder decisions often move through other people. Add directional relationships such as influences, depends on, trusted by, works closely with, provides approval/input or unresolved tension. This makes the map useful when a champion, expert or gatekeeper is the real path to a decision.
Internal working map vs external-safe brief
Internal
May contain support judgments, concerns, evidence, rationale, private notes and relationship information. A full share link contains this data and is not encrypted.
External-safe
Uses an explicit allowlist and strips internal support, concerns, evidence, rationale, notes, relationships and history before export or share.
Practical stakeholder mapping rules
- Write the decision first. Authority, influence and interest only make sense relative to a specific initiative or decision.
- Separate formal authority from informal influence. A low-title expert may shape the approver more than a senior manager does.
- Keep unknowns unknown. Record the assessment basis instead of turning team assumptions into facts.
- Use current vs required involvement to find the engagement gap; not every stakeholder needs maximum involvement.
- Treat concerns as decision inputs, not personality labels. The goal may be approval, constraint discovery, informed dissent or implementation readiness.
- Map influence and dependency paths when an important decision cannot be reached directly through one stakeholder.
- Give every high-priority engagement a concrete ask, one owner, a next action and a due date.
- Revisit the map after scope, org, review or milestone changes. Stakeholder assessments are time-bound.
- Use the external-safe brief for sharing outside the working team; the internal link contains map data and is not encrypted.
Failure modes the audit is designed to catch
The map looks complete but nobody knows who can approve the decision.
Why: Power scores replaced explicit decision rights.
Fix: Identify the final approver and driver; clarify multiple apparent approvers.
A low-power group disappears from the engagement plan.
Why: Formal authority was treated as the same thing as impact.
Fix: Assess impact-on-stakeholder separately and create consultation actions for heavily affected groups.
A person is described as opposed without direct evidence.
Why: A team inference was recorded as objective truth.
Fix: Mark the basis as assumption or unknown and validate it before acting on it.
The matrix and engagement plan contradict each other after dragging.
Why: Visual position changed without changing the underlying assessment.
Fix: Use score-driven placement so movement updates the scores that power the logic.
The onion view is just the power-interest grid in circles.
Why: Proximity was inferred from power + interest.
Fix: Assign Core, Direct/adjacent or External/ecosystem directly based on relationship to the initiative.
The engagement plan sounds generic.
Why: The decision, goals, concerns, ask or required role are missing.
Fix: Capture the missing context; the tool should say unknown rather than invent a persuasive message.
A shared artifact leaks internal judgments.
Why: A full working map was treated as a share-safe version.
Fix: Use the external-safe export/share mode and preview the allowlisted fields before sharing.
History grows rapidly or restores confusing nested snapshots.
Why: Snapshots copied previous history recursively.
Fix: Snapshots store the decision, stakeholders, relationships and view only; history itself is excluded.
FAQ
What is this stakeholder map for?
It is for one product decision, launch, migration or change. Define the decision, assess who can approve, influence, implement or be affected, record what is known versus assumed, then turn the map into specific engagement actions and review it as the situation changes.
What is the difference between power, influence and impact?
Power means formal ability to approve, veto, resource or materially alter this decision. Influence is informal: whose judgment other people follow. Impact means how strongly the decision affects the stakeholder. They are separate dimensions; a heavily affected user group can have low formal power.
How does Power–Interest classification work?
Scores 4–5 are the high band and 1–3 are the lower band. High power/high interest maps to Manage closely; high power/lower interest to Keep satisfied; lower power/high interest to Keep informed; lower/lower to Monitor. Unassessed values stay explicitly unassessed.
Do I need to identify a blocker?
No. The tool never requires opposition. Record the current position toward this specific decision as supportive, conditional, undecided, concerned, opposed or unknown. If everyone is genuinely supportive, that is valid; if support has not been assessed, keep it unknown.
What does the Stakeholder Alignment Audit check?
It flags fragile decision strategy: missing decision context or approver, unassessed or assumption-heavy judgments, current-versus-required involvement gaps, unresolved concerns, invalid relationship paths, missing action owners or dates, stale assessments and privacy risks. It does not produce an arbitrary overall score.
How does relationship mapping work?
Create a directional edge between two stakeholders: influences, depends on, trusted by, works closely with, provides approval/input to, or unresolved tension. Relationships help expose influence paths and dependencies without reducing the organization to friend/enemy labels.
What is external-safe sharing?
External-safe mode creates a sanitized payload and export that keeps only decision context plus basic stakeholder identity, role, required involvement and agreed action fields. It excludes internal support judgments, concerns, evidence, assessment rationale, notes and relationship data by default.
Is an internal share link private?
No. The internal share URL contains compressed map data; compression is not encryption. Anyone with the link can inspect the payload. Use it only when that is appropriate, or switch to the external-safe share for a sanitized artifact.
Why compare current and required engagement?
The gap tells you where action is actually needed. An approver who is only informed has an approval gap; an affected user group that should be consulted has a consultation gap. A stakeholder already at the required level does not need a manufactured engagement action.
Use the next tool for the gap you found
Product Strategy owns what strategic choice to make. Release Checklist owns whether readiness gates actually passed. This tool owns who matters around the decision and what engagement closes the alignment gap.
Learn the underlying product judgment
Turn the map into the next decision action
Use the audit to identify the approval, concern, evidence or commitment that is still missing, then route to strategy, release readiness or the relevant learning path instead of treating stakeholder mapping as a one-off diagram.
Freshness
Last updated: 2026-09-17
- 2026-09-17: Rebuilt the tool around a specific decision, explicit decision roles, formal authority vs informal influence vs impact, and current vs required engagement.
- 2026-09-17: Added Stakeholder Alignment Audit, evidence/assumption basis, relationship workflow, score-driven matrix movement, direct onion layers and non-recursive history.
- 2026-09-17: Added real external-safe export/share redaction and explicit privacy warnings for full internal share links.
- 2026-03-06: Initial Stakeholder Map Builder launch.