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-industrial.md

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

Activation Design Example: Industrial

Product: NFA-500 controller with a connected-service tier (Northfield Automation) Customer: plant maintenance teams; installs by partner crews Why this example exists: in hardware, activation spans delivery, install, commissioning, and connection, owned by four parties. The weeks of delay were handoffs, not the product.


## The moment
**Customer's goal:** keep the line running and hear about faults before production does.
**Activation (hypothesis):** unit commissioned, connected to the service, and reporting for 14 days
with no service call.
**Evidence:** `[NEEDS SOURCE]`. NFA-200 data has no connected tier. Treat as hypothesis until the first cohort.

## The path today (first 14 units)
| Step | Owner | Median | Stopped here |
|---|---|---|---|
| Delivery to site | Logistics | 6 days | 0 |
| Install and wiring | Partner crew | 9 days | 2 waiting on a shutdown window |
| Commissioning | Partner crew / Service | 11 days | 3 waiting on a service visit |
| Connection to service | Customer IT | 17 days | 5 waiting on firewall approval |
**Time to value:** median 43 days; the slowest units 70+.

## Blockers
| Blocker | Evidence | Fix |
|---|---|---|
| Firewall approval | 5 of 14 units | Send IT a one-page network note with the order (pre-fill) |
| Waiting for a service visit | 3 of 14 | Partner crews certified to commission (remove) |
| Shutdown window | 2 of 14 | Book the window at quote time |

## Designed path
| Checkpoint | Action | Owner | Stall handling |
|---|---|---|---|
| 1 | Network note to customer IT at order | Sales | Day 7: partner calls IT |
| 2 | Install in a booked window | Partner | Day 14 after delivery: partner manager calls |
| 3 | Commission and connect | Certified partner | Day 21: service engineer visit |
| 4 | 14-day reporting check | Service | Day 35: call the plant |
**Handoff:** quote captures the plant IT contact, shutdown calendar, and who will operate the unit.

## Metric
**Connected and reporting within 45 days of delivery:** 4 of 14 baseline · target `[NEEDS SOURCE]`.
**Median time to activate:** 43 days · **Guardrail:** service visits per new unit.

What to learn from this

  • The longest wait was firewall approval, an IT dependency no product feature touches.
  • The fix was captured at the quote, which is a sales handoff, not an onboarding step.
  • Stall handling has days attached, so a quiet customer triggers an action.

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