Customer Onboarding and Adoption
Domain focus
Customer Onboarding and Adoption tests how a new customer moves from contract to first value and then to durable use. Questions focus on the sales-to-success handoff, kickoff, onboarding milestones, time-to-value, adoption measurement, entitlement versus consumption, and removing adoption barriers.
Core rules
- The internal handoff comes before customer kickoff. Capture contract terms, entitlements, sold use cases, commitments, stakeholders, support history, and known risks. A missing handoff creates rework and credibility loss.
- Kickoff confirms the business outcomes, scope, roles, governance, onboarding milestones, and success plan. The customer should leave with owners and dates, not a product tour.
- Define a first-value event: the earliest observable proof that the solution works for the customer's use case. Shorten time-to-value by sequencing prerequisites such as access, integration, SSO, data, and training.
- Adoption has breadth, depth, and consistency. Breadth is active users or sites; depth is feature/use-case maturity; consistency is repeatable use over time. License count is entitlement, not adoption.
- Adoption barriers are usually technical (integration, security), process (workflow fit), people (skills, change resistance), or commercial (licensing confusion). Diagnose the category before prescribing training.
- Cisco success motions often use Success Tracks and telemetry to align adoption activities to the purchased use cases; the CSM should use evidence, not assumptions.
- Onboarding plans typically run 30/60/90 days with exit criteria: access complete, first value achieved, adoption baseline set, governance live.
Worked example
A customer buys 500 collaboration licenses; the handoff says 'company-wide rollout.' At kickoff the CSM learns only 200 users are in the initial department and SSO is not ready. The CSM resets the onboarding plan: first-value event is 50 active hosts in 30 days; prerequisites are SSO, room setup, and admin training; adoption is tracked weekly by active hosts and meeting minutes, not licenses. Reasoning: entitlement is 500, but the achievable initial population is 200. Measuring licenses would overstate adoption; a first-value event creates an early evidence point and exposes the SSO dependency.
Traps
- Skipping the internal handoff and asking the customer for information already sold.
- Treating kickoff as a product demonstration.
- Reporting license consumption as adoption.
- Launching training before access, integration, or workflow blockers are removed.
- No first-value milestone, so onboarding drifts.