communication-value-delivery

name	communication-value-delivery
description	Use this skill to help teams communicate benefits, create clear demos and use cases, explain ROI and value, gather feedback, and drive adoption and trust. Trigger when the user asks for demo plans, use cases, ROI narratives, value propositions, adoption messaging, stakeholder feedback loops, or iteration plans. Do not use it for deceptive persuasion, fabricated metrics, or unrelated sales copy.

Communication Value Delivery

Purpose

Help an agent turn a capability, feature, automation, product, service, or internal initiative into clear value communication that stakeholders can understand, test, trust, and adopt.

This skill focuses on four connected outcomes:

• Communicate benefits in audience-specific language.
• Create demos and use cases that make value concrete.
• Explain ROI, assumptions, risks, and confidence clearly.
• Gather feedback, iterate, and drive adoption through trust-building actions.

When to use

Use this skill when the user asks to:

• Explain the value of a product, automation, feature, process change, service, or internal initiative.
• Create demo scripts, demo agendas, proof-of-value plans, use cases, pilot plans, stakeholder walkthroughs, or launch narratives.
• Translate technical capabilities into business benefits, user outcomes, executive summaries, enablement content, or adoption messaging.
• Build an ROI story, value model, assumption register, benefits tracker, or impact summary.
• Gather stakeholder feedback, synthesize feedback themes, prioritize improvements, and plan iterations.
• Improve adoption, trust, credibility, buy-in, change readiness, or user engagement.

Do not use

Do not use this skill when:

• The user asks for deceptive, manipulative, or pressure-based persuasion.
• The output would require fabricated metrics, false customer claims, fake testimonials, or unsupported ROI claims.
• The user needs final financial, legal, compliance, procurement, or regulatory approval instead of a communication or planning aid.
• The task is unrelated to value communication, demos, feedback, adoption, or stakeholder trust.
• The task requires exposing private customer data, confidential metrics, or personal data without authorization.

Required inputs

Use the information already available. Ask for missing details only when essential; otherwise make reasonable assumptions and label them.

Recommended inputs:

• Initiative, capability, product, feature, process, or automation being communicated.
• Target audience, stakeholder group, or buyer/user persona.
• Desired behavior change or adoption goal.
• Current pain point, baseline workflow, or status quo.
• Benefits, evidence, metrics, user quotes, pilot findings, or expected outcomes.
• Costs, effort, constraints, risks, dependencies, or change impacts.
• Demo environment, available data, and any limitations that must be disclosed.
• Feedback channels, review cadence, launch timeline, and success measures.
• Required output format, such as demo script, use-case library, ROI narrative, launch plan, FAQ, or feedback synthesis.

Workflow

1. Confirm the communication goal and adoption objective.

   • Identify what the audience should understand, believe, decide, try, approve, or adopt.
   • Name the decision stage: awareness, evaluation, pilot, approval, rollout, renewal, or expansion.

2. Segment the audience.

   • List stakeholder groups, their priorities, likely objections, trust concerns, and preferred proof.
   • Translate one generic benefit into audience-specific outcomes.

3. Build the value message.

   • Use this structure: for the audience, who has the pain, the initiative helps achieve the outcome by the mechanism, supported by the proof, with these guardrails.
   • Separate benefits into user value, business value, operational value, risk reduction, and strategic value.
   • Avoid claims that are not supported by evidence or clearly labeled assumptions.

4. Create use cases.

   • For each use case, capture user, trigger, current pain, new workflow, before/after contrast, value, proof, limitations, and next step.
   • Prioritize use cases by impact, feasibility, urgency, visibility, and fit with adoption goals.

5. Design a clear demo.

   • Start with the audience's problem, not the feature list.
   • Show a realistic before state, the changed workflow, and the aha moment.
   • Include one trust-building moment that explains what the demo does not prove, what data was used, and what must be validated next.
   • End with a specific call to action: approve a pilot, test a workflow, review assumptions, nominate users, or provide feedback.

6. Explain ROI and value.

   • Define baseline, expected change, adoption volume, time saved, cost avoided, revenue enabled, risk reduced, quality improved, and confidence level.
   • Show formulas and assumptions before conclusions.
   • Use ranges when inputs are uncertain.
   • Include qualitative value when direct financial conversion would be misleading.

7. Plan adoption and trust-building.

   • Identify champions, skeptics, enablement needs, change impacts, training moments, governance, and support channels.
   • Create transparent messaging for risks, limitations, data privacy, model or process reliability, and human oversight.
   • Provide a rollout sequence: pilot, learn, refine, enable, scale, measure.

8. Gather feedback.

   • Choose feedback methods: interviews, survey, office hours, in-product prompts, usage data, support tickets, stakeholder reviews, or retrospective workshops.
   • Ask about clarity, credibility, usefulness, usability, objections, missing use cases, blockers, and desired proof.
   • Separate signal from noise by grouping feedback into themes and ranking by adoption impact and effort.

9. Iterate.

   • Convert feedback into changes to the demo, value story, use cases, ROI assumptions, enablement materials, or product/process design.
   • Track decisions, open questions, and next validation steps.

10. Package the output.

    • Provide the requested deliverable with assumptions, evidence gaps, recommended next step, and feedback loop.
    • Make the output usable by the stated audience without extra explanation.

Output format

Return the requested artifact. Common formats include:

• Value proposition and benefit map.
• Use-case library or prioritized use-case table.
• Demo agenda, script, talk track, or storyboard.
• ROI narrative, assumptions table, formula, and sensitivity notes.
• Adoption plan, champion plan, stakeholder FAQ, objection handling, or enablement checklist.
• Feedback survey, interview guide, synthesis, prioritization, and iteration plan.

When presenting ROI, always include:

• Inputs and assumptions.
• Calculation method or formula.
• Confidence level.
• Non-financial benefits and risks.
• What must be validated next.

Quality checklist

Before finalizing:

• The output starts from audience pain and desired outcome, not only features.
• Benefits are concrete, specific, and relevant to the target audience.
• Demos show a realistic scenario, clear aha moment, and next step.
• Use cases include before/after contrast and proof or validation needs.
• ROI claims are traceable to assumptions, formulas, or evidence.
• Unsupported claims are labeled as assumptions or removed.
• Feedback questions can produce actionable iteration decisions.
• Adoption plan addresses trust, objections, enablement, and measurement.
• Sensitive data, confidential metrics, and private user information are not exposed.

Safety and privacy

• Do not fabricate results, customer references, usage data, savings, revenue, or endorsements.
• Do not pressure, shame, or manipulate stakeholders into adoption.
• Do not hide limitations, material risks, conflicts of interest, or unresolved validation needs.
• Do not expose confidential data, private customer information, personal data, or proprietary metrics unless explicitly authorized.
• Do not present estimates as audited financial results.
• Do not replace expert review for financial, legal, compliance, medical, safety, security, or regulatory decisions.