Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-deliver/skills/activation-design

activation-design

Verified

Define the moment a new customer first gets real value, then design the shortest path to it. Use when trials stall, installs sit idle, or onboarding is a checklist nobody finishes.

FileKindSize
SKILL.mdskill md12.0 KB
examples/sample-industrial.mdmarkdown2.4 KB
examples/sample.mdmarkdown2.2 KB
template.mdmarkdown1.5 KB

template.md

View on GitHub
# Activation Design Template

Figures come from supplied data or are `[NEEDS SOURCE]`. Quality checks at the bottom.

---

## 1. The moment
**Customer's goal:** · **"It worked" looks like (their terms):**
**Activation moment (one behavior or result):** · **Status:** evidenced / hypothesis
**Evidence:** [activated customers retain X vs Y, counts] or `[NEEDS SOURCE]`

## 2. The path today
| Step | Owner | Median time | Customers who stop here (count) | Necessary? |
|---|---|---|---|---|

**Time to value:** median ___ · slow tail (slowest 25%) ___

## 3. Blockers (ranked by customers lost)
| Blocker | Evidence | Cost (customers) | Fix (remove / pre-fill / default / do-for-them) |
|---|---|---|---|

## 4. The designed path
| Checkpoint | One action | Owner (product / specialist / partner / customer) | Stall handling (nudge, call, day) |
|---|---|---|---|

**Sales-to-onboarding handoff (captured and passed on):**

## 5. Metric
**Activation rate within N days:** [numerator / denominator, with counts] · **Median time to activate:**
**Guardrail:** [support contacts per new customer] · **Owner:** · **Reviewed:**

---

## Quality checks
- [ ] Activation is a customer outcome, not activity
- [ ] Evidenced or labeled a hypothesis
- [ ] Time to value measured, including the slow tail
- [ ] Blockers are evidenced, not assumed
- [ ] One action and one owner per checkpoint
- [ ] Stall handling defined with days
- [ ] The handoff from sales is explicit
- [ ] The metric shows counts and has a guardrail
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall