Stakeholder Priority Analyzer

Pro v1.0.0 1 view

Navigate competing stakeholder priorities in product management using prioritization frameworks, underlying need analysis, and empathetic communication templates.

What You Get

Transforms conflicting requests from engineering, sales, leadership, and customers into structured analysis with clear rationale, stakeholder-specific communications that maintain trust, and practical alternatives that preserve relationships while making difficult tradeoff decisions.

The Problem

Product managers constantly face competing stakeholder requests with limited team capacity. Saying 'no' damages relationships. Saying 'yes' to everything leads to burnout and missed strategic goals. Stakeholders often propose solutions without explaining underlying needs, leading to wasted effort building the wrong things. When priorities shift due to crises, maintaining trust while breaking commitments is extremely difficult. PMs need frameworks to make defensible prioritization decisions, communication templates that preserve relationships when delivering bad news, and techniques to redirect solution requests into productive problem discovery conversations.

The Solution

This skill provides a complete stakeholder priority analysis workflow. It applies impact/effort/strategic alignment frameworks to competing requests, identifying force multipliers, quick wins, and low-priority items. When stakeholders propose solutions instead of problems, it generates discovery questions and hypotheses about underlying needs, then suggests better alternatives. For each stakeholder, it drafts customized communications that acknowledge their request, explain decisions with transparent rationale, offer alternatives or compromises, and provide specific timelines. It prepares responses for common pushback scenarios and provides guidance for crisis reprioritization when security issues or other urgent matters disrupt committed roadmaps. The skill emphasizes relationship preservation through empathy, transparency, and collaborative problem-solving.

How It Works

1 Gather stakeholder requests with who/what/why/effort/urgency context and current team constraints
2 Apply impact/effort/risk prioritization framework to score and rank all competing requests
3 Identify underlying needs when stakeholders bring solutions, generate discovery questions and alternative solutions
4 Create recommended priority ranking with clear rationale, tradeoffs, timeline, and confidence level
5 Draft stakeholder-specific communications that acknowledge requests, explain decisions, offer alternatives, and maintain relationships
6 Prepare pushback response templates for common objections and difficult conversations

What You'll Need

List of competing stakeholder requests with basic context about who is requesting and why
Rough effort estimates for each request (hours, days, weeks, or complexity level)
Current team constraints (capacity, timeline, strategic goals, existing commitments)
Understanding of urgency drivers (what happens if delayed, external deadlines)

Get This Skill

Requires Pro subscription ($9/month)

Have Feedback?

Help us improve this skill by sharing your ideas and suggestions.

Request Improvements

Examples

Crisis Reprioritization with Multiple Urgent Items

Security vulnerability, marketing campaign launch, and CEO customer promise all converge with conflicting deadlines. Demonstrates crisis prioritization framework balancing existential risk (security), external commitments (CEO promise), and internal flexibility (marketing). Includes emergency response timeline, stakeholder communications for breaking commitments, and alternative solutions for each scenario.

View example

Redirecting Solution Request to Problem Discovery

VP Engineering proposes AI chatbot citing competitor parity without explaining user need. Demonstrates underlying need analysis with hypothesis generation, discovery questions to uncover real problems (likely onboarding friction), alternative solutions for different scenarios, and conversation guide for redirecting from premature solution to productive problem exploration.

View example

Three Competing Quarterly Requests with Time Constraints

Classic multi-stakeholder scenario with CEO dashboard (4 weeks), Sales export button (3 days), and Support bug fixes (1 week). Demonstrates impact/effort/strategic alignment framework identifying quick wins and force multipliers, with week-by-week Q2 execution timeline and customized stakeholder communications for each request.

View example

View all examples