32 lines
1.2 KiB
Markdown
32 lines
1.2 KiB
Markdown
---
|
||
name: storytelling
|
||
description: Use to craft compelling narratives and assets from customer advocacy
|
||
programs.
|
||
---
|
||
|
||
# Advocacy Storytelling Skill
|
||
|
||
## When to Use
|
||
- Producing case studies, videos, webinars, or social proof assets.
|
||
- Training PMM, CS, or agencies on customer narrative structure.
|
||
- Auditing existing stories for consistency and freshness.
|
||
|
||
## Framework
|
||
1. **Hero Definition** – capture persona, industry, and stakes to establish relevance.
|
||
2. **Challenge & Stakes** – quantify pain points and consequences of inaction.
|
||
3. **Solution Narrative** – highlight product capabilities, implementation journey, and partner collaboration.
|
||
4. **Outcomes & Proof** – provide metrics, quotes, and qualitative wins.
|
||
5. **Call-to-Action** – tailor next steps for target audience (demo, trial, community join).
|
||
|
||
## Templates
|
||
- Story outline (hero, challenge, solution, outcomes, CTA).
|
||
- Quote library sheet with metadata and approvals.
|
||
- Multi-format checklist (PDF, blog, video, social snippets) with owners.
|
||
|
||
## Tips
|
||
- Capture B-roll or extra quotes for future reuse.
|
||
- Align tone with persona; execs prefer strategic outcomes while practitioners need tactical details.
|
||
- Pair with `create-stories` command to keep assets and distribution in sync.
|
||
|
||
---
|