agentleFS
mahirautela2020-designmahirautela2020-design/claude-skills-ux/collab-stakeholder-communication/SKILL.md

collab-stakeholder-communication

Skill1 starsChanged 8 months agoMITView on GitHub

Improves stakeholder management and communication. Use when the user needs help crafting clear stories in reviews, documenting rationale, managing feedback loops, and adapting communication for PMs, engineers, executives, and non-design stakeholders, grounded in product strategy, evidence, and metrics.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when preparing design reviews, sharing research or design decisions, or working through feedback with cross-functional …

    line 22
  2. Distinctive:

    Before preparing any communication, clarify who you’re speaking to and what you need from them.[web:390]

    line 30
  3. Distinctive:

    Use a simple storytelling structure instead of jumping straight into screens.[web:377][web:384][web:388]

    line 44
  4. Distinctive:

    Treat feedback as a structured loop, not ad-hoc chaos.[web:383][web:386]

    line 89
  5. Distinctive:

    Use conclusion‑first logic:

    line 138
  6. Distinctive:

    Use lightweight frameworks to structure design presentations.[web:377][web:388]

    line 153
  7. Distinctive:

    Keep stakeholders aligned over time, not just in big reviews.[web:383][web:390]

    line 192
  8. Distinctive:

    Follow through on commitments and close loops on feedback.

    line 218
  9. Distinctive:

    Start with recommendation and impact (activation up, support tickets down).

    line 244
  10. Distinctive:

    Ask: “What user or business evidence would help us decide between these options?”

    line 258
  11. Distinctive:

    Use structured frameworks (PAS, Options & Analysis) to focus discussion.[web:377][web:388]

    line 259
  12. Distinctive:

    Ask more specific prompts:

    line 270
  13. Distinctive:

    Use this skill with:

    line 279

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stakeholder Management & Communication

Purpose

This skill helps designers communicate their work clearly, build trust with stakeholders, and reduce rework by using structured storytelling, documented rationale, and intentional feedback loops.[web:377][web:383][web:390] It also guides how to adapt communication for different audiences such as PMs, engineers, executives, and non-design stakeholders, while tying stories back to strategy, opportunities, and metrics from product-ux-strategy-alignment, product-discovery-opportunity, and ux-product-design-metrics.[web:378][web:384][web:382]

Use this skill when preparing design reviews, sharing research or design decisions, or working through feedback with cross-functional partners.


Instructions

Step 1: Clarify audience and objective

Before preparing any communication, clarify who you’re speaking to and what you need from them.[web:390]

Ask:

  • "Who will be in the room (PMs, engineers, execs, marketing, support)?"
  • "What is the main objective (inform, decide, align, get approval, gather feedback)?"
  • "What decisions or actions do I need from this group by the end of the meeting or message?"[web:377][web:382]

Summarize this in 1–2 lines; use it to focus your story, slides, or document and to scope which metrics, journeys, or opportunities you reference.


Step 2: Structure the story: context → evidence → insight → recommendation

Use a simple storytelling structure instead of jumping straight into screens.[web:377][web:384][web:388]

A practical pattern:

  1. Context – What problem, opportunity, or outcome is this work addressing (tie to strategy/metrics if possible)?
  2. Evidence – What research, data, or stakeholder input informed your thinking?
  3. Insight – What did you learn that matters for decisions?
  4. Recommendation / Design – What are you proposing and why?
  5. Ask – What decision or feedback do you need now?[web:380][web:382]

Example mini-script for each section you present:

  • “Here’s the problem or outcome we’re focused on.”
  • “Here’s what we heard or saw (evidence).”
  • “This tells us [insight] about user needs or constraints.”
  • “Here’s the design/change that responds to that insight.”
  • “Feedback: I’d like input on X and Y, not colours or minor copy today.”[web:377][web:388]

This keeps stakeholders focused on user and business needs instead of personal preferences and makes it easy to plug into opportunity maps, OSTs, and metrics briefs from related skills.[web:384][web:390]


Step 3: Document design rationale

Capture why decisions were made so you can explain and revisit them.[web:383][web:389]

For key decisions, note:

  • Problem or constraint being solved.
  • Options considered (including those not chosen).
  • Evidence or principles used (research, heuristics, technical constraints, strategy).
  • Final decision and reasoning.

You can keep this in:

  • A rationale section in your design doc.
  • Comments or notes in your design tool.
  • A short “Decision log” for larger projects.

This reduces repeated debates, supports handover, and helps new stakeholders catch up quickly.[web:383][web:389]


Step 4: Plan and manage feedback loops

Treat feedback as a structured loop, not ad-hoc chaos.[web:383][web:386]

Before reviews:

  • Set expectations:
    • Purpose of the review (exploratory, directional, final sign‑off).
    • What kind of feedback is useful now (e.g., problem framing vs micro‑visual details).
  • Share pre‑reads when helpful so stakeholders can arrive prepared.

During reviews:

  • Anchor feedback in evidence and goals:
    • “Does this concept solve the problem we defined?” vs “Do you like this colour?”
  • Capture:
    • Feedback items.
    • Decisions made.
    • Open questions and owners.[web:383]

After reviews:

  • Summarize decisions and next steps in writing and share with attendees.[web:383][web:389]
  • Close the loop by showing how you addressed feedback in the next iteration (or why you did not).

Step 5: Adapt communication by stakeholder type

Tailor depth and framing to different audiences.[web:378][web:390]

For PMs:

  • Emphasize:
    • User problems, opportunities, and impact on product metrics.
    • Trade‑offs and constraints you considered.
  • Keep it collaborative:
    • Invite co‑ownership of decisions and next experiments.

For engineers:

  • Emphasize:
    • Clear requirements, edge cases, and behaviour.
    • Rationale for complexity vs simplicity.
  • Be precise and concrete:
    • Provide annotated flows, specs, and examples.

For executives / leadership:

  • Emphasize:
    • High-level narrative: problem, opportunity, impact on strategy and KPIs.[web:382][web:379]
  • Use conclusion‑first logic:
    • Recommendation → impact → evidence → next steps.

For non-design stakeholders (e.g., marketing, sales, support):

  • Emphasize:
    • How changes affect customers, messaging, and their workflows.
    • What will change in practice and when.[web:390]

Adjust detail based on time and audience; put deep detail in appendices or follow-ups.


Step 6: Use simple storytelling frameworks in design reviews

Use lightweight frameworks to structure design presentations.[web:377][web:388]

Two practical patterns:

  • Problem → Agitate → Solution (PAS):
    • Problem: Describe the user/business problem with data or stories.
    • Agitate: Show consequences or impact if not addressed.
    • Solution: Present the design that addresses it and why it works.
  • Options & Analysis:
    • Show 2–3 viable options for solving the problem.
    • Compare them along key criteria (user impact, feasibility, alignment).
    • Recommend one option and explain why, inviting discussion.[web:384][web:388]

Pick a pattern depending on whether you need buy‑in for a clear recommendation (PAS) or co‑decision on trade‑offs (Options & Analysis).


Step 7: Handle disagreements and conflicting feedback

When stakeholders disagree:

  • Return to shared goals:
    • “Which option better serves the agreed user outcome or metric?”
  • Separate:
    • Facts (data, research).
    • Assumptions (what we think is true but haven’t validated).
    • Preferences (subjective likes/dislikes).[web:383][web:389]

If conflict persists:

  • Propose:
    • A small test or research activity to get more evidence (product-experimentation-data, ux-user-research).
    • A time‑bound decision (e.g., pick option A now, revisit after learning X).
  • Clarify decision owners so debates don’t remain open indefinitely.

Step 8: Communicate progress and changes transparently

Keep stakeholders aligned over time, not just in big reviews.[web:383][web:390]

Practices:

  • Share short updates:
    • What changed since last time.
    • What you learned (from research, testing, or experiments).
    • What’s next and any decisions needed.
  • Use lightweight artefacts:
    • Before/after snapshots.
    • Journey or flow updates.
    • Lists of resolved vs open issues.

This builds trust and reduces surprises late in delivery.[web:383][web:386]


Step 9: Build long-term relationships and trust

Stakeholder management is also about relationships, not just meetings.[web:380][web:384][web:390]

Behaviours:

  • Listen actively and reflect back concerns to show understanding.
  • Be transparent about trade‑offs and constraints; don’t oversell certainty.
  • Acknowledge others’ expertise (engineering complexity, business constraints, customer knowledge).
  • Follow through on commitments and close loops on feedback.

Over time, this makes it easier to advocate for UX decisions and get support for user‑centred choices.


Examples

Example 1: Design review with PM and engineering

  • Audience & objective:
    • PM + engineering, goal is to align on direction and identify risks.
  • Story:
    • Context: onboarding drop‑off problem tied to activation metrics.
    • Evidence: analytics + usability findings.
    • Insight: users don’t understand required steps; copy and structure confuse them.
    • Recommendation: simplified 4‑step flow with clearer progress and guidance.
  • Communication:
    • Emphasized impact on activation and engineering complexity.
    • Captured decisions and follow‑ups in a shared doc and decision log.

Example 2: Executive update on UX initiative

  • Audience & objective:
    • Execs, goal is to show impact and secure support for next phase.
  • Story:
    • Start with recommendation and impact (activation up, support tickets down).
    • Show key user stories and 2–3 metrics aligned to strategy.
    • Outline next UX bets tied to strategic goals.
  • Communication:
    • High‑level visuals, minimal screens.
    • Clear ask: resources to extend the pattern to other flows.

Troubleshooting

Reviews devolve into opinion battles

  • Re-anchor on problem, evidence, and goals before discussing solutions.[web:383][web:390]
  • Ask: “What user or business evidence would help us decide between these options?”
  • Use structured frameworks (PAS, Options & Analysis) to focus discussion.[web:377][web:388]

Stakeholders feel lost or overwhelmed

  • Simplify presentations:
    • Fewer slides, clearer narrative, conclusion first.[web:382][web:390]
  • Tailor detail to audience; put deep details in appendices or follow‑ups.
  • Explicitly state: “Today, I need us to decide X; the rest is context.”

Feedback is vague or unhelpful

  • Ask more specific prompts:
    • “How well does this address the problem we defined?”
    • “Where do you see risk for your team in this approach?”
  • Encourage stakeholders to tie feedback to goals and constraints, not just taste.[web:383][web:386]

Notes for use with other skills

  • Use this skill with:
    • ux-mindset-problem-framing and product-discovery-opportunity to tell clearer stories about problems and opportunities.
    • product-ux-strategy-alignment and ux-product-design-metrics to connect narratives to strategy and metrics.
    • Research, evaluation, and experimentation skills (ux-user-research, ux-prototyping-validation, product-experimentation-data) to bring evidence into stakeholder communication.[web:384][web:387]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.