How you know you have this problem
- Two customers who bought the same thing describe different experiences.
- Onboarding is 'done' when the calls finish, regardless of what the customer achieved.
- The account manager who onboarded a customer is the only person who knows where things stand.
- Handover to steady state is a conversation, not a checkpoint.
- Early churn is explained as fit, but the customers who left never reached first value.
Define done as an outcome
The single highest-value change: replace the activity definition of completion with an observable outcome. Not 'four sessions delivered' but 'the customer has run the process themselves once, successfully, without assistance'.
This is uncomfortable at first because it makes incomplete onboarding visible. That visibility is the point. An outcome definition also gives you a clean measure of time to value, which is the only onboarding metric that predicts retention.
Design the milestone spine
Four to six milestones, no more. Each one carries an owner, a target day relative to start, an exit condition and a defined action when it slips.
| Milestone | Exit condition | Target | On slip |
|---|---|---|---|
| Kickoff held | Scope, contacts and success measure confirmed in writing | Day 3 | Owner escalates to the sales owner who sold it |
| Access and data ready | Everything needed to deliver is in place and verified | Day 7 | Named blocker raised with the customer sponsor |
| First delivery | The customer has received the first real output | Day 14 | Delivery lead reviews capacity and sequence |
| Customer-run success | The customer performs the core task unaided | Day 30 | Health rating drops; account review triggered |
| Steady-state handover | Ownership, cadence and open items transferred explicitly | Day 45 | Handover blocked until open items are assigned |
Make slippage visible without a meeting
Put the spine in the system of record
Milestones live as dated tasks or stages on the customer record, not in a document. If tracking requires opening a spreadsheet, it will be updated after the fact.
Alert on the exception, not the status
Nobody needs a notification that onboarding is proceeding. Everybody needs one when a milestone passes its target day without an exit condition met.
Route the alert to a person with authority
An alert to the person who is already stuck changes nothing. Route it to whoever can reallocate capacity or talk to the customer sponsor.
Review the pattern monthly
Which milestone slips most often is the design defect. If access and data always slip, the fix is in the sales-to-delivery handoff, not in the onboarding team's effort.
Mistakes to avoid
- Adding steps instead of removing ambiguity. A twelve-step onboarding does not produce consistency; it produces partial completion with confidence.
- Shared ownership. 'The team owns onboarding' means the fastest-drifting account gets the least attention.
- Measuring satisfaction instead of progress. Customers are polite early. Milestone completion is the honest signal.
- Treating onboarding as a marketing asset. A branded welcome sequence does not move a customer to first value; a named owner and a due date do.
Related work
Run the customer onboarding playbook and hand the team the onboarding checklist. The wider system is described in customer success operations.
Muhammad Sameed Abid
Muhammad Sameed Abid is a business operations, automation and growth systems professional with 9+ years across operations management, workflow and CRM automation, marketing operations and customer success. He is currently Head of Customer Success at GHA Marketing and writes here about the operating layer underneath growth.