stakeholder-alignment
owl-listener/designer-skills
Build responsibility matrices, decision rights, and communication plans to unblock stakeholder alignment.
What is stakeholder-alignment?
Creates alignment artifacts—stakeholder maps, RACI matrices, decision frameworks, and communication plans—to clarify ownership and resolve decision deadlocks. Use when unclear roles or conflicting priorities stall progress.
- Generate stakeholder maps identifying influence, interest, and role categories
- Build RACI matrices defining Responsible, Accountable, Consulted, and Informed roles per decision
- Create decision frameworks specifying what needs input, who decides, and conflict resolution
- Design communication plans with cadence, channels, and feedback timelines
- Establish feedback protocols for format, timing, prioritization, and conflict handling
How to install stakeholder-alignment
npx skills add https://github.com/owl-listener/designer-skills --skill stakeholder-alignmentHow to use stakeholder-alignment
- 1.Map all stakeholders and categorize by influence (high/low) and interest (high/low)
- 2.Define decision points and create a RACI matrix for each major decision
- 3.Establish who has final say, who must be consulted, and who needs notification
- 4.Design a communication plan specifying frequency, channels, and feedback deadlines
- 5.Document the framework and share with all stakeholders at project kickoff
Use cases
- Kickoff alignment when stakeholder roles are unclear or overlapping
- Resolve decision deadlocks by establishing explicit decision rights upfront
- Create communication cadence for multi-stakeholder design reviews
- Document feedback expectations and conflict-handling procedures before scope changes occur
- Map influence and interest to tailor engagement strategy for each stakeholder group
- Design leads and product managers navigating multi-stakeholder projects
- Teams experiencing scope creep or late-stage stakeholder objections
- Organizations with unclear decision authority or competing priorities
- Cross-functional teams needing explicit feedback and approval workflows
stakeholder-alignment FAQ
At project kickoff, before decisions are made. Establishing roles and communication proactively prevents conflicts later.
RACI defines roles for specific decisions. A decision framework defines the process—what needs input, who decides, and how to resolve disagreements across all decisions.
Review at major project milestones or when scope, team composition, or priorities change significantly.
Use the decision framework to establish explicit criteria (e.g., budget authority, domain expertise) before conflict arises, then apply consistently.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: stakeholder-alignment
description: Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).
Stakeholder Alignment
You are an expert in navigating stakeholder landscapes and creating alignment around design decisions.
What You Do
You create artifacts helping teams align with stakeholders on roles, decisions, communication, and feedback.
Alignment Artifacts
- Stakeholder Map — Identify all stakeholders, map influence vs interest, categorize roles
- RACI Matrix — Responsible, Accountable, Consulted, Informed per decision
- Decision Framework — What needs input, who decides, how to resolve disagreements
- Communication Plan — Who/what/when, cadence, channels, feedback timelines
- Feedback Protocol — Format, timing, prioritization, conflict handling
Common Challenges
Stakeholders designing solutions, conflicting priorities, late-stage scope changes, missing stakeholders.
Best Practices
- Map stakeholders at kickoff
- Establish decision rights before conflict
- Communicate proactively
- Document decisions and rationale
- Revisit as projects evolve
Related skills
More from owl-listener/designer-skills and the wider catalog.
state-machine
Model UI behavior as explicit states, events, and transitions to eliminate impossible states.
summarize-interview
Turn interview transcripts into structured themes, quotes, and action items for immediate research insights.
survey-design
Design unbiased surveys to measure attitudes and prevalence at scale with sound methodology.
team-workflow
Design your team's operating rhythm—task management, rituals, and collaboration tooling.
test-scenario
Write realistic usability test scenarios with success criteria and observation guides.
theming-system
Design multi-brand and multi-mode theming architectures using token layers.