Index of every page on this site: llms.txt
All skills
deanpeters avatar

/activation-design

@476ae12
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/activation-design

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample.md

≈563 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Activation Design Example: SaaS

Product: Route Optimizer add-on (Fieldlight) · Customer: dispatchers at 50-300 technician companies Why this example exists: the team counted "tour finished" as activated. The redefinition changed the onboarding from a tour to a short path.


## The moment
**Customer's goal:** fix the day without hours of rework when it breaks.
**Activation (hypothesis):** a dispatcher optimizes a real day and keeps the result (does not
revert it) within 7 days.
**Evidence:** Prior add-on: accounts reaching its first real use retained at 82% vs 51%
(`[NEEDS SOURCE]` for this product; to confirm after 90 days).

## The path today (March trials, N = 212)
| Step | Owner | Median | Stopped here |
|---|---|---|---|
| Invite dispatcher | Customer | 1 day | 47 |
| Load a day | Customer | 2 days | 48 |
| Optimize first route | Customer | 1 day | 68 |
**Time to value:** median 4 days; the slowest quarter never arrive.

## Blockers
| Blocker | Evidence | Fix |
|---|---|---|
| Depot address not set | 31 of 68 stalled accounts | Pre-fill from the account (remove) |
| Day has no jobs in trial | Interviews (3) | Offer sample day data (do-for-them) |
| Large accounts need a skills mapping | 28 of 40 large trials stalled | Specialist call at day 2 |

## Designed path
| Checkpoint | Action | Owner | Stall handling |
|---|---|---|---|
| 1 | Confirm depot (pre-filled) | Product | none needed |
| 2 | Load today or the sample day | Product/customer | Day 2 nudge: offer sample day |
| 3 | Optimize and keep | Customer | Day 3: email; Day 5: specialist call if account > 100 techs |
**Handoff:** sales records the dispatcher's name, current process, and biggest rework pain in the CRM; onboarding opens the first call with it.

## Metric
**Reached activation within 7 days:** 49 of 212 (23%) March baseline · target `[NEEDS SOURCE]`.
**Median time to activate:** 4 days · **Guardrail:** support contacts per new account.

What to learn from this

  • "Tour finished" was removed from the metric. It rose while real use stayed flat.
  • The top blocker was a missing default, fixed by pre-filling, not by teaching.
  • The activation moment is labeled a hypothesis, with the check named.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    The skill is a set of documentation templates and instructional guidelines for product management. It contains no executable code, network operations, or sensitive data access.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: LOW · No issues

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the product, the customer, and what 'first real value' looks like]
type
component
theme
pm-artifacts
Other metadata
intent
Name the activation moment (the first time a customer gets the value they bought for), measure the time to reach it, find what stands between sign-up or delivery and that moment, and design the onboarding path, owner handoffs, and checkpoints around it. Works for self-serve software, assisted onboarding, and hardware commissioning, and ends with an activation metric the team can track.
best_for
[
  "Defining what 'activated' means so the team stops counting sign-ups",
  "Shortening the time from purchase or delivery to first real value",
  "Designing onboarding around the customer's outcome instead of a feature tour",
  "Handing a new customer between sales, onboarding, and support without a gap"
]
scenarios
[
  "Trials start but few reach a first optimized route. What should 'activated' mean?",
  "Commissioned units sit idle for weeks. How do we design the first 30 days?",
  "Our onboarding is a 20-step checklist nobody finishes. What do we cut?",
  "Define the activation metric for a connected-service launch"
]
estimated_time
30-45 min

README badge

README badge for deanpeters/product-manager-skills/activation-design