stakeholder-alignment · refoundai — Claude Code skill: what it does

---
name: stakeholder-alignment
description: Help users master the art of leading without formal authority by identifying stakeholder incentives, neutralizing conflict through connection, and using co-creation to build shared ownership.
---

# Stakeholder Alignment

Drive cross-functional momentum by mapping incentives and co-creating solutions

Help the user with stakeholder alignment using insights from 30 guests and posts across Lenny's Podcast and Newsletter.

## How to Help

1. **Incentive Mapping** - Guidance on how to identify the goals, fears, and OKRs of key stakeholders to tailor your messaging.
2. **Conflict Neutralization** - Practical scripts and mindset shifts for moving from defensive pushback to collaborative discovery.
3. **Co-creation Strategy** - Frameworks for involving partners early in the design process to ensure they feel like authors rather than reviewers.
4. **Communication Standardization** - Methods for creating a single source of truth that prevents information drift across functions.

## Core Principles

### Adopt an Improv Mindset
Adam Grenier: "If you approach it with that 'Yes, and...', it's often still true. It's like, oh, both of these things can be true at once. You could have a different goal than I have, or you have a system problem local to you that is important to you and it's not important to me."

Use the Yes and technique to validate a collaborator perspective before adding your own constraints. This allows competing priorities to coexist without stalling progress or damaging the rapport between teams.

### Assume Information Gaps
Ami Vora: "It means that every meeting you walk into, you're probably not going to get bored and I get bored a lot, but if you assume that every person there knows something that you don't know, then it's not just wait to get to the right answer, it's like, discover the thing that they know that you don't know and it becomes just a little bit of uncovering."

Approach disagreements by assuming your colleague possesses unique information that you lack. Transform potential conflict into a discovery process by responding to opposing opinions with curiosity rather than defense.

### Build a Bridge of Connection
Dr. Becky Kennedy: "He kind of joins my world where I'm embedded in my own priorities and by doing that forms a bridge, that's what connection is. So I can kind of walk back over to his world with him to do something that's a priority in his world."

Cooperation is built when you acknowledge and join another person reality before asking them to join yours. Establish this connection bridge to ensure partners feel heard before you attempt to redirect their behavior.

### Manifest the Visual Future
Mihika Kapoor: "We lean heavily into designing and prototyping even before a project gets a green light. If you and your team do your job correctly, what does the world look like?"

Secure buy-in for zero-to-one ideas by investing in high-fidelity prototypes and mocks before seeking formal resourcing. Making the vision feel real through visual evidence is more effective than abstract descriptions.

### Establish a Canonical Source
Naomi Gleit: "Of course, I'm sure there's hundreds of docs associated with the project, but there needs to be one canonical doc. Everyone should know exactly where the canonical doc is. That's the one place I can go to get all the information I need about a project and it will link to all the other docs, things on the canonical doc are."

Eliminate conflicting information by creating one central document that serves as the definitive source of truth for the project. This prevents stakeholders from working off different interpretations of the same goal.

### The PM-Engineering Triad
Tamar Yehoshua: "And then I think what's really important is that you're aligned. You understand your roles and responsibilities and where you're going to divide and conquer and where you're going to be aligned. You don't want any of this ... Like people in the organization, they ask mom, they asked dad and they got different opinions and playing one against the other."

Success depends on establishing a high-trust, aligned partnership with engineering to ensure ideas are feasible and to prevent confusion. Meet frequently and value your partners input to ensure a unified leadership front.

## Templates & Frameworks

- **Five Steps to Influence Prioritization in a Large Company** (This Week #9: Breaking into growth, leading with influence, and (not) stepping on toes 🦶) - A checklist for PMs to get their asks prioritized when they lack direct authority, especially in bureaucratic organizations
- **Stakeholder Intel-Gathering Questions** (A PM’s guide to influence) - Six questions to ask in 1:1 meetings with stakeholders (or people who know them) to understand how they make decisions and how to influence them
- **Three Strategies to Co-Create Effectively** (Getting buy-in) - A three-step approach to co-creating ideas with your team so they feel invested and produce better outcomes.
- **PM-Engineering Alignment Operating Model** (Tamar Yehoshua) - The specific meeting cadences and rituals Tamar and CTO Cal Henderson used at Slack to stay aligned and manage the product-engineering relationship.
- **Consulting vs. Collaboration vs. Consensus Decision-Making Model** (Autonomy vs. direction - Issue 35) - A framework distinguishing three modes of group decision-making, originally based on Crucial Conversations, to help managers set the right expectations for how 
- **The Silver Burrito Alignment Test** (Setting goals) - A metaphor and mental model for diagnosing whether your team is truly aligned on what success looks like for a project or initiative
- **Seven Strategies for Influence (The Frodo Framework)** (How to get better at influence) - A comprehensive framework of seven strategies PMs can use to lead through influence rather than authority, each illustrated with Lord of the Rings examples and 
- **Five Tactics of PM Influence** (A PM’s guide to influence) - A comprehensive framework of five tactics PMs can use to drive alignment on complex initiatives

See `references/artifacts.md` for the full list with details.

## Questions to Help Users

- "What are the specific OKRs and goals your stakeholders are being measured on this quarter?"
- "Is there a single source of truth document that all cross-functional partners have access to?"
- "Have you asked your stakeholders what specific data or evidence would change their mind on this project?"
- "At what stage of the process did you first involve your engineering and design partners?"
- "What is the most generous interpretation of the pushback you are receiving from other teams?"

## Common Mistakes to Flag

- **Confusing Consensus with Collaboration** - Seeking unanimous agreement for every decision often sacrifices speed and quality for a diluted outcome that satisfies no one.
- **Reflexively Protecting the Roadmap** - Failing to validate a stakeholder problem because it is not on the current plan damages rapport and misses opportunities for alignment.
- **Ignoring Individual Incentives** - Proposals often fail because they fulfill company goals but create more work or risk for the specific stakeholder who needs to approve them.
- **Presenting Finished Solutions** - Stakeholders are more likely to reject a strategy they were not involved in building because they lack a sense of authorship.

## Deep Dive

For all 50 sourced insights from 30 guests, see `references/guest-insights.md`

## Related Skills

- Product Reviews
- Executive Communication
- Managing Up
- Running Meetings