Files
Magnus HedemarkGitHubusername <username>factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
11a6595d1c feat(product-adoption): add product adoption skill (#214)
* feat(product-adoption): add product adoption skill

Add product-adoption skill for diagnosing and designing product adoption
across consumer, B2B, internal-tool, and public-service contexts.

- SKILL.md with adoption pipeline (acquisition, activation, adoption, retention, expansion), evidence-based decision points, non-SaaS support, routing to go-to-market and prose references to not-yet-landed skills
- README.md with 5 required human-facing sections
- references/: discovery-brief.md, adoption-lifecycle-concepts.md, non-saas-adoption-contexts.md, behavior-change-and-education.md
- templates/: adoption-plan.md, activation-time-to-value-diagnostic.md, segmentation-and-rollout-record.md, sustained-use-review.md
- evals/evals.json with 7 output-quality cases covering internal tool, public service, low feature discovery, enterprise cohort rollout, pause-expansion evidence, and anti-trigger acquisition/instrumentation routing
- Updated root README.md catalog section, references/skill-triggers.md, and regenerated catalogs

Closes #191

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

* fix(product-adoption): add missing SKILL.md and README.md

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

* chore(product-adoption): regenerate catalogs

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

---------

Co-authored-by: username <username>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2026-08-02 17:00:57 -04:00

1.6 KiB

Adoption Lifecycle Concepts

The Five Stages

ACQUISITION → ACTIVATION → ADOPTION → RETENTION → EXPANSION

1. Acquisition — "User has arrived"

Owner: go-to-market. Boundary: Everything before arrival is acquisition; after is activation.

2. Activation — "User completed first meaningful outcome"

Owner: product-adoption. The "aha moment." Metrics: activation rate, time-to-value.

3. Adoption — "User has formed a habit"

Owner: product-adoption. Product becomes regular workflow. Metrics: frequency, depth, feature discovery.

4. Retention — "User stays and returns"

Shared: product-adoption (adoption signals) + product-lifecycle-learning (churn analysis).

5. Expansion — "User deepens engagement"

Owner: product-adoption (feature discovery) + conditional-customer-success (account upsell).

Why Distinguishing Matters

Example 1: Low retention → re-engagement campaign, but real problem is activation. Wrong fix. Example 2: Low feature adoption → add more features, but real problem is discovery. Makes it worse. Example 3: Low adoption → blame marketing, but activation experience is broken. Misdiagnosis.

Relationship Definitions

Relationship Definition
Acquisition enables activation Arrival alone is NOT activation
Activation enables adoption Aha moment alone is NOT habit
Adoption drives retention Weak adoption almost always precedes churn
Retention enables expansion Expansion pushed too early accelerates churn
Expansion feeds back into adoption Broader use deepens habit