domains / business / stakeholder-alignment / stakeholder-alignment

stakeholder-alignment

Skill card

combined

The two skills share the name and the broad goal of aligning stakeholders, but they prescribe different procedures. The first copy is an artifact-focused playbook (stakeholder maps, RACI, decision frameworks, communication plans) aimed at clarifying ownership and decision rights. The second copy is a relationship and influence playbook (incentive mapping, conflict neutralization, co-creation, canonical sources) grounded in specific podcast-derived principles and templates. Neither copy contains the other's core steps, so crowning one would hide a real alternative approach.

Repositories

Other copies

Combined skill

---
name: stakeholder-alignment
description: Build alignment through both structural artifacts and relational influence techniques. Use when ownership is unclear or when cross-functional momentum is stalled.
---
# Stakeholder Alignment

Drive alignment by combining structural clarity with relational influence.

## 1. Structural Alignment (Artifacts)
Use these to clarify roles and decision rights:
- **Stakeholder Map**: Identify stakeholders, map influence vs. interest, and categorize roles.
- **RACI Matrix**: Define Responsible, Accountable, Consulted, and Informed parties for key decisions.
- **Decision Framework**: Specify what needs input, who decides, and how disagreements are resolved.
- **Communication Plan**: Define who/what/when, cadence, channels, and feedback timelines.
- **Feedback Protocol**: Establish format, timing, prioritization, and conflict handling rules.

## 2. Relational Alignment (Influence)
Use these to build buy-in and neutralize conflict:
- **Incentive Mapping**: Identify the goals, fears, and OKRs of key stakeholders to tailor messaging.
- **Conflict Neutralization**: Use 'Yes, and' improv techniques to validate perspectives before adding constraints. Assume information gaps to turn defense into discovery.
- **Co-creation Strategy**: Involve partners early in design/prototyping so they feel like authors, not reviewers.
- **Canonical Source**: Establish a single source of truth document to prevent information drift.
- **PM-Engineering Triad**: Maintain high-trust alignment with engineering to ensure feasibility and a unified front.

## Best Practices
- Map stakeholders and incentives at kickoff.
- Establish decision rights (RACI) before conflict arises.
- Communicate proactively and document decisions with rationale.
- Revisit alignment as the project evolves.

## Conflicts
- **Owl-Listener/designer-skills** focuses on formal artifacts (RACI, Maps) as the primary solution.
- **RefoundAI/lenny-skills** focuses on behavioral influence (Incentives, Co-creation) as the primary solution.
- **Resolution**: Apply structural artifacts to define the 'rules of the game' and relational techniques to manage the 'human dynamics' within those rules.