用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/fabioc-aloha/ChessCoach --skill stakeholder-management命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
Detect, create, and manage the AI-Memory fleet communication channel. Fires on bootstrap, session start (announcements), and feedback writes.
Generate on-brand Alex — ACT Edition SVG banners for documents (READMEs, plans, notes, release artifacts)
基于 SOC 职业分类
正在显示 SKILL.md
| type | skill |
| lifecycle | stable |
| inheritance | inheritable |
| name | stakeholder-management |
| description | Influence mapping, communication strategies, and expectation management for complex organizations |
| tier | standard |
| applyTo | **/*stakeholder*,**/*influence*,**/*expectation* |
| currency | 2026-04-22T00:00:00.000Z |
Influence mapping, communication strategies, and expectation management for complex organizations.
| Field | Value |
|---|---|
| Skill ID | stakeholder-management |
| Version | 1.0.0 |
| Category | Leadership |
| Difficulty | Advanced |
| Prerequisites | None |
| Related Skills | executive-storytelling, coaching-techniques, frustration-recognition |
Stakeholder management is the art of achieving outcomes through others—especially when you lack direct authority. For directors, this means influencing executives, aligning peers, and enabling teams.
Stakeholders aren't obstacles—they're levers. The question is: what do they need to move your direction?
| Low Interest | High Interest | |
|---|---|---|
| High Power | Keep Satisfied | Manage Closely |
| Low Power | Monitor | Keep Informed |
For each key stakeholder, document:
| Field | Purpose |
|---|---|
| Name/Role | Who they are |
| Power Level | Decision authority |
| Interest Level | Engagement level |
| Current Position | Support, oppose, neutral |
| Desired Position | Where you need them |
| Key Concerns | What they worry about |
| Motivators | What they care about |
| Communication Preference | How to reach them |
## Stakeholder: VP of Engineering
- **Power**: High (controls development resources)
- **Interest**: Medium (not primary sponsor)
- **Current**: Neutral-skeptical
- **Desired**: Active supporter
- **Concerns**: Timeline risk, team bandwidth
- **Motivators**: Technical excellence, team morale
- **Preference**: Data-driven, short meetings
- **Strategy**: Show technical feasibility, minimize scope creep
| Strategy | When to Use | Tactics |
|---|---|---|
| Reciprocity | Building long-term allies | Do favors first, bank goodwill |
| Coalition | Facing resistance | Build supporter network |
| Evidence | Skeptical stakeholders | Data, pilots, proof points |
| Authority | Borrowed credibility | Executive sponsor, expert endorsement |
| Scarcity | Creating urgency | Limited window, competitive pressure |
| Social proof | Risk-averse stakeholders | Industry examples, peer adoption |
Move stakeholders progressively:
Opponent → Skeptic → Neutral → Supporter → Champion
Small wins at each stage build momentum.
| Resistance Type | Root Cause | Counter |
|---|---|---|
| Fear of unknown | Uncertainty | Education, pilots |
| Loss of power | Territory threat | Involvement, shared credit |
| Resource concern | Budget/time | Clear scope, trade-offs |
| Past failure | Burned before | Different approach, risk mitigation |
| Not invented here | Pride | Co-creation, acknowledgment |
| Stakeholder Type | Frequency | Medium |
|---|---|---|
| Executive sponsor | Weekly | 1:1, brief updates |
| Manage closely | 2x/week | Meetings, direct calls |
| Keep satisfied | Bi-weekly | Email summaries |
| Keep informed | Monthly | Newsletters, dashboards |
| Monitor | As needed | Include in broadcasts |
| Audience | Focus On | Avoid |
|---|---|---|
| Executives | Outcomes, ROI, decisions | Technical details |
| Technical leads | Feasibility, architecture | Business jargon |
| Finance | Costs, savings, ROI | Feature details |
| Legal | Risks, compliance | Jargon, assumptions |
| End users | Benefits, ease, timeline | Complexity |
| Stage | Purpose | Example Questions |
|---|---|---|
| Situation | Understand context | "What's your current process?" |
| Problem | Surface pain points | "What challenges do you face?" |
| Implication | Deepen urgency | "What happens if this continues?" |
| Need-payoff | Co-create solution | "How would X help you?" |
| Principle | Implementation |
|---|---|
| Under-promise, over-deliver | Commit to achievable, stretch for more |
| Early warning | Surface problems before they escalate |
| No surprises | Executives hate learning bad news publicly |
| Clear trade-offs | "We can do X or Y, not both" |
[Scope]
/ \
/ \
[Time]---[Resources]
Rule: You can only fix two. If scope increases, either time extends or resources grow.
Framework: SBI-I (Situation-Behavior-Impact-Intent)
| Challenge | Approach |
|---|---|
| Unclear priorities | Ask for explicit ranking |
| Micromanagement | Proactive updates, build trust |
| Unavailable sponsor | Brief async updates, clear asks |
| Changing requirements | Document trade-offs, get sign-off |
| Unrealistic timelines | Data-driven pushback, alternatives |
| Mode | When Appropriate |
|---|---|
| Competing | Urgent, right matters |
| Collaborating | Time available, relationship matters |
| Compromising | Moderate importance, both must move |
| Avoiding | Trivial issue, cooling off needed |
| Accommodating | Relationship > issue |
When stakeholders disagree with each other:
| Role | Definition |
|---|---|
| Responsible | Does the work |
| Accountable | Owns the decision (one per task) |
| Consulted | Input before decision |
| Informed | Told after decision |
| Forum | Frequency | Purpose | Attendees |
|---|---|---|---|
| Steering Committee | Monthly | Decisions, escalations | Sponsors, leads |
| Working Group | Weekly | Progress, blockers | Doers, SMEs |
| Stakeholder Update | Bi-weekly | Status, alignment | All interested |
| 1:1 with Sponsor | Weekly | Issues, guidance | You + sponsor |
| Stakeholder Says | They Mean | Your Move |
|---|---|---|
| "Keep me informed" | Don't surprise me | Regular brief updates |
| "I need to think about it" | Not convinced | Address concerns |
| "Sounds good" | Neutral, not committed | Get explicit commitment |
| "Let's discuss offline" | Issue is sensitive | Private meeting |
| "I have concerns" | Resistance building | Dig deeper immediately |
| Signal | Meaning | Action |
|---|---|---|
| Sponsor stops attending | Losing interest | Re-engage urgently |
| New stakeholder appears | Power shift | Quick mapping, engagement |
| Silence from key player | Brewing resistance | Reach out proactively |
| Scope creep from exec | Expectations mismatch | Clarify trade-offs |
| Trigger | Response |
|---|---|
| "stakeholder", "influence", "politics" | Full skill activation |
| "resistance", "pushback", "blocking" | Module 2 + 5 |
| "RACI", "governance", "who decides" | Module 6 |
| "manage expectations", "scope creep" | Module 4 |
| "stakeholder map", "power interest" | Module 1 |