home / skills / gtmagents / gtm-agents / onboarding-blueprint

This skill helps design persona-based onboarding journeys with milestones and measurement plans to align product, CS, and marketing.

npx playbooks add skill gtmagents/gtm-agents --skill onboarding-blueprint

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: onboarding-blueprint
description: Template for designing onboarding journeys, milestones, and measurement
  plans.
---

# Onboarding Blueprint Skill

## When to Use
- Creating persona-based onboarding for new tiers or product lines.
- Refreshing onboarding journeys after major product changes.
- Aligning product, CS, and marketing on activation milestones.

## Framework
1. **Persona Canvas** – goals, motivations, blockers, success definition.
2. **Milestone Ladder** – aha moment, activation, stickiness, expansion triggers.
3. **Channel Mix** – in-app, email, docs, community, human assist with triggers.
4. **Instrumentation** – required events, metrics, and guardrails.
5. **Experiment Hooks** – backlog of tests tied to each milestone.

## Templates
- Journey table (step, trigger, message, owner, metric).
- Metric dashboard layout for activation + retention.
- Experiment backlog sheet linked to milestones.

## Tips
- Keep journeys lightweight; aim for 3-5 key milestones per persona.
- Combine qualitative inputs (surveys, interviews) with telemetry for context.
- Pair with `design-onboarding-journey` to auto-generate tailored blueprints.

---

Overview

This skill is a template-driven Onboarding Blueprint for designing persona-based onboarding journeys, milestones, and measurement plans. It bundles a practical framework, reusable templates, and experiment hooks to align product, CS, and marketing around activation and retention outcomes.

How this skill works

The skill walks teams through a five-part framework: Persona Canvas, Milestone Ladder, Channel Mix, Instrumentation, and Experiment Hooks. It produces artifact templates (journey tables, metric dashboard layouts, experiment backlogs) that map steps to triggers, messages, owners, and success metrics. Use these outputs to prioritize 3–5 key milestones per persona and define the telemetry and experiments needed to validate activation and retention.

When to use it

  • Designing persona-based onboarding for new tiers or product lines
  • Refreshing onboarding after a major product or UX change
  • Aligning product, CS, and marketing on activation milestones
  • Defining instrumentation and metrics for success
  • Creating an experiment backlog tied to onboarding milestones

Best practices

  • Limit each persona journey to 3–5 high-impact milestones to reduce complexity
  • Combine qualitative inputs (surveys, interviews) with telemetry for full context
  • Map a clear owner for every step and tie messages to explicit triggers
  • Define required events and guardrails before running experiments
  • Prioritize experiments by impact and ease of implementation

Example use cases

  • Onboarding blueprint for a new premium tier with tailored activation milestones
  • Rewriting first-7-day journey after a major UI redesign to recover activation rates
  • Creating an instrumented metric dashboard for activation and early retention
  • Assembling an experiment backlog that ties A/B tests to specific onboarding steps
  • Coordinating cross-functional playbooks for in-app, email, docs, and human assist

FAQ

How many milestones should a persona journey include?

Aim for 3–5 key milestones that represent the path to value; more steps dilute focus and make measurement harder.

What instrumentation is essential?

Capture explicit trigger events for each milestone, an activation event, and retention signals. Define metrics and guardrails before experiments.