Symptom: Decisions stall or surprise blockers appear.
Cause: Blockers were not identified or had no mitigation.
Fix: Mark at least one blocker, document concerns, and add a next action (e.g. 1:1, escalation) with due date.
Technical SEO
Title, meta description, canonical, OG, Twitter, BreadcrumbList, FAQPage, WebApplication schema.
Stakeholder Map Builder (Free)
This tool is for mapping project and product stakeholders (power–interest and engagement), not org charts. Build a decision-grade stakeholder map plus an engagement plan: who to talk to, how, how often, what to ask, and what risks exist.
- Power–Interest matrix (or Influence–Impact / onion). Auto placement; drag to override. Quadrant strategies drive engagement suggestions.
- Deterministic engagement plan per stakeholder: goal, key message, ask, channel and cadence, risk if unmanaged, next action. Internal vs external view for safe sharing.
- Export CSV/MD/JSON/SVG/PNG; share URL; version history (snapshots); quality lint. No login.
No login. Autosave in browser. Shareable URL. Clear data when you want.
Template:
Load example:
Quality / lint
- warn: Fewer than 8 stakeholders (0). Consider adding more for medium/large projects. → Add more stakeholders or lower "Min stakeholders for coverage" in settings.
Keep informed
Manage closely
Monitor
Keep satisfied
Stakeholder details
Select a stakeholder from the matrix or table.
How it works
- Choose a template (Power–Interest, Influence–Impact, or Stakeholder onion) and add stakeholders with name, role, power, interest, stance, and goals.
- Place stakeholders on the matrix (auto from scores; drag to override). Use the right panel to edit details and see the deterministic engagement plan (goal, message, ask, channel, risk, next action).
- Toggle internal vs external view for safe sharing. Run the quality panel (coverage, critical hygiene, blockers). Export CSV/MD/JSON/SVG/PNG, share URL, save history snapshots. No login.
Power–interest vs influence–impact (when to use which)
Power–interest is the classic grid: map stakeholders by how much power they have over the initiative and how much interest they have. Use it for most product and project work—launches, features, migrations. Influence–impact is better for change management: you care who can influence adoption and who is impacted by the change. The stakeholder onion (core / adjacent / external) is a lite view for showing who is at the center vs the periphery. This tool supports all three; the engagement plan generator uses quadrant and stance in each case.
How to identify stakeholders fast (internal and external)
Start with decision makers and gatekeepers: who can say yes or no, and who controls access to resources or people? Then add influencers (who shape opinion) and implementers (who do the work). For external stakeholders, think buyers, champions, detractors, compliance, and end users. Tag each as internal or external so you can switch to external view before sharing with customers or partners. List goals and concerns so the engagement plan is specific, not generic.
How to create an engagement plan (cadence, channel, ask)
For each stakeholder, set a preferred channel (meeting, Slack, email, async doc) and cadence (weekly, biweekly, monthly, ad hoc). The tool suggests an engagement goal, key message, and ask based on quadrant and stance. Critical stakeholders (Manage closely, Keep satisfied) must have an owner, next action, and due date—the lint panel enforces this. Copy the engagement calendar (next 10 actions with due dates and owners) into your task list so nothing slips.
Common pitfalls (ignoring blockers, too many criticals, no owner)
Ignoring blockers leads to surprises: always identify at least one and document concerns and mitigation. Having too many “critical” stakeholders makes the map unusable—narrow to true decision makers and gatekeepers. Leaving critical stakeholders without an owner or next action means no one is accountable; the quality panel fails until you set owner, next_action, and due_date for Manage closely and Keep satisfied.
Pro tips
- Start with decision makers and gatekeepers; then add influencers and implementers so you don’t miss power.
- For every “Manage closely” and “Keep satisfied” stakeholder, set an owner, next action, and due date.
- Identify at least one blocker and document concerns; unrealistic maps have no blockers.
- Use the external view before sharing with customers or partners; it hides sensitive notes and concerns.
- Match channel to preference: don’t force async_doc for someone who prefers meetings.
- Cadence should reflect power and interest: weekly for critical, monthly for keep informed.
- Link stakeholders (ally/conflict/dependency) to spot risks like a high-power blocker connected to a decision maker.
- Revisit the map when scope or org changes; one snapshot per initiative or phase.
- Export the engagement calendar and sync with your task list so next actions don’t slip.
- Keep goals and “what they care about” short and concrete; vague goals make engagement plans generic.
Common mistakes (symptom, cause, fix)
Symptom: Too many “critical” stakeholders; map is overwhelming.
Cause: Everyone is Manage closely or Keep satisfied.
Fix: Narrow to true decision makers and gatekeepers; move others to Keep informed or Monitor.
Symptom: No one owns key stakeholders.
Cause: Owner field empty for high-power/high-interest stakeholders.
Fix: Assign an owner and next_action + due_date for every Manage closely and Keep satisfied stakeholder.
Symptom: Engagement plan feels generic.
Cause: Goals and concerns are empty or vague.
Fix: Fill goals (what they care about) and, for blockers, concerns; the engagement plan generator uses these.
Symptom: Wrong channel or cadence; stakeholders disengage.
Cause: Using one-size-fits-all (e.g. all email, all monthly).
Fix: Set preferred channel and cadence per stakeholder; respect meeting vs async preferences.
Symptom: External share leaks sensitive info.
Cause: Sharing internal view with customers or partners.
Fix: Use External view before sharing; it hides concerns and internal notes.
Symptom: Map is out of date.
Cause: No refresh when scope or team changes.
Fix: Save version snapshots with a note; restore when needed. Re-run placement after score changes.
Symptom: Stakeholders with no goals or role.
Cause: Placeholder entries or incomplete import.
Fix: Require name, role, and goals for every stakeholder; lint flags orphans.
FAQ
Is this for org charts or project stakeholder mapping?
This tool is for mapping project and product stakeholders (power–interest and engagement), not org charts. You place people by power and interest (or influence/impact), assign owners and next actions, and generate an engagement plan—who to talk to, how, how often, and what risks exist. It is decision-grade stakeholder mapping for initiatives, not hierarchy diagrams.
What templates are available?
You can choose Power vs Interest (default), Influence vs Impact (for change management), or Stakeholder onion (core vs adjacent vs external). The template changes how the matrix is labeled and how quadrants are named; engagement plans still use power, interest, stance, and influence type. Use Power–Interest for most product and project work; use Influence–Impact when you focus on change adoption.
What is the difference between internal and external view?
Internal view shows full details: concerns, risks, internal notes, and all fields. External view hides sensitive fields (concerns, internal notes) so you can share a safe version with customers or partners. Toggle the view before exporting or sharing; the lint panel also reminds you to use external view for safe share.
How does the engagement plan generator work?
For each stakeholder the tool generates an engagement goal, key message, ask, channel and cadence suggestion, risk if unmanaged, and next action suggestion. It uses deterministic rules based on quadrant (Manage closely, Keep satisfied, etc.), stance (supporter, neutral, blocker), and influence type. No AI; you can edit the suggested next action and set due date and owner.
Why do I need owner, next action, and due date for critical stakeholders?
Critical stakeholders (Manage closely, Keep satisfied, or Core) can block or unblock the initiative. If no one owns them and there is no next action with a due date, they often get missed until it is too late. The lint panel fails when these fields are missing for critical stakeholders so you fix it before sharing or exporting.
Can I import stakeholders from CSV?
Yes. Use the Import CSV action and upload or paste CSV with headers: name, role, org, stakeholder_type, influence_type, power, interest, stance, goals, concerns, channel, cadence, owner, next_action, due_date, last_contacted, notes_link. The tool parses rows and creates stakeholders; you can then adjust placement and engagement plans.
What exports are available?
You can export CSV (stakeholder table), Markdown (stakeholder-ready report with summary, engagement overview, risks, calendar), JSON (full state and lint results), and SVG snapshot of the matrix. Print/PDF uses the browser print dialog. Summary and engagement calendar are also copyable as text for pasting into docs or slides.
What is version history (lite)?
You can save snapshots of the current map with a timestamp and note, and restore a previous snapshot. This keeps a simple version history so you can revert after big changes or compare. Snapshots are stored in state and included in share URL and JSON export; they are not stored on a server.
Does it require login?
No. The tool runs fully client-side: autosave to localStorage, explicit Clear data, and a shareable URL that reconstructs the full state (including stakeholders, relationships, and history). You can use it from any device; your data stays in your browser until you clear it or share the link. No account or login is required.
How do I use the relationship mapping?
You can link two stakeholders as ally, conflict, or dependency. The relationship list and conflict warnings (e.g. high-power blocker connected to a decision maker) help you spot risks. This is optional but recommended for complex initiatives with many interdependent stakeholders.
Learn more with CraftUp
Courses, blog, and glossary for product teams.
Map stakeholders, then ship with alignment
Use CraftUp tools and courses to align stakeholders, plan engagement, and ship with fewer surprises.
Freshness
Last updated: 2026-03-06
- 2026-03-06: Launched Stakeholder Map Builder: power–interest, influence–impact, onion templates; matrix placement and drag-override.
- 2026-03-06: Deterministic engagement plan per stakeholder; internal vs external view; lint (coverage, critical hygiene, stance, too many criticals, orphan).
- 2026-03-06: Exports: CSV, Markdown, JSON, SVG; summary and engagement calendar; version history (snapshots); 3 loadable examples.