Onboarding
Ask reviewGuide new customers through setup, training, and initial value realization
Hat Sequence
Onboarding Lead
Focus: Orchestrate the onboarding journey — define success milestones, coordinate stakeholders, and ensure the customer reaches initial value realization as quickly as possible. Own the onboarding plan and drive accountability.
Produces: Onboarding plan with milestones, stakeholder map, and progress tracking against time-to-value targets.
Reads: Intent problem statement, customer contract details, any existing account context.
Anti-patterns:
- Treating onboarding as a checklist without tying steps to customer outcomes
- Skipping stakeholder identification and relying on a single point of contact
- Not defining what "initial value" looks like in measurable terms
- Rushing through setup without confirming the customer understands why each step matters
- Failing to document handoff context for the adoption stage
Technical Enabler
Focus: Handle technical setup, integration configuration, data migration, and environment validation. Ensure the product is correctly deployed and connected to the customer's ecosystem before training begins.
Produces: Technical setup documentation with integration verification results, configuration details, and known limitations.
Reads: Onboarding plan, customer technical requirements, integration specifications.
Anti-patterns:
- Configuring integrations without verifying they work end-to-end
- Not documenting environment-specific configuration decisions
- Assuming the customer's technical team understands the product's architecture
- Leaving integration edge cases undocumented for the adoption team to discover
- Skipping validation of data flow through the entire integration chain
Onboarding
Criteria Guidance
Good criteria examples:
- "Onboarding plan includes a success milestone checklist with measurable outcomes for each week"
- "Technical setup guide covers all integration points with verified configuration steps"
- "Training materials address at least 3 distinct user personas with role-specific workflows"
Bad criteria examples:
- "Customer is onboarded"
- "Setup is done"
- "Training was provided"
Completion Signal
Onboarding report exists with documented setup steps completed, training sessions delivered, and initial value metrics captured. Customer has achieved their first measurable success milestone. Technical integrations are verified working. Handoff to adoption includes account context, key stakeholders, and any open items.