design-customer-onboarding

name	design-customer-onboarding
category	design
description	Design a customer onboarding plan that reaches a measurable first-value outcome with clear responsibilities, recovery paths, and instrumentation. Use when creating or repairing a product, service, migration, or implementation onboarding flow.

design-customer-onboarding

Design around the customer's outcome and starting condition, not the organization's departments. Reduce time to first value while preserving informed choice, safety, and the ability to recover.

Inputs

• Gather customer segments, desired outcomes, current workflows, product prerequisites, support records, and onboarding data.
• Map account creation, data import, configuration, integration, training, approval, and commercial dependencies.
• Identify accessibility, security, privacy, regulated-data, and human-support requirements.

Procedure

1. Define first value as an observable customer result with a baseline and target window.
2. Segment by meaningful starting conditions, complexity, risk, and goals rather than superficial attributes.
3. Map the current journey from commitment through independent repeated use.
4. Separate customer actions, system actions, internal ownership, wait states, and proof.
5. Remove tasks that do not contribute to first value; defer optional configuration.
6. Design prerequisites, progressive guidance, examples, save-and-resume, and clear completion states.
7. Add error, permission, import, integration, and handoff recovery paths that protect customer work.
8. Define responsibilities, communication cadence, escalation, and the transition to ongoing support.
9. Instrument progress, time, failure, help use, abandonment, and achieved outcome with privacy controls.
10. Pilot with representative customers, observe behavior without coaching, and revise from evidence.

Boundaries

Do not force unnecessary data collection, hide required work, weaken security, or mark onboarding complete because internal tasks closed. Obtain permission for data access and migration. Keep a human path for high-risk, accessibility, and exceptional cases.

Done

• First value, starting segments, critical path, responsibilities, and completion evidence are defined
• Error and recovery paths preserve customer data, access, and progress
• Instrumentation measures achieved outcome as well as task completion
• A representative pilot has been observed and the design revised from recorded findings