onboarding never completed: activation milestone stuck at 40%
Fixes onboarding stuck at 40 percent by finding the milestone where accounts stall and removing that specific blocker. Use when many accounts plateau at the same completion point. Not for one account with a unique internal delay.
TL;DR
A plateau at the same percentage across accounts is a wall with a name: the milestone at that percentage is blocked by something structural (SSO approval, data migration effort, a step owned by a team that never gets scheduled). Convert the percentage back into the milestone list and the wall stops being abstract.
onboarding never completed: activation milestone stuck at 40%Use this when
- Many accounts sit at the same onboarding completion percentage
- Time at that milestone far exceeds other milestones
- The stalled step often involves the customer's IT or data team
Not for this skill when
- Accounts stall at varied points, suggesting capacity rather than a wall
- The percentage is a reporting artifact and milestones actually complete
Steps
- Translate the plateau percentage into the exact milestone sequence for your onboarding plan. Verify: the milestone at the plateau is named
- Measure median days per milestone across the last 20 onboardings. Verify: the wall milestone's delay is quantified against the rest
- Interview three stalled customers and their onboarding leads about that milestone specifically. Verify: the blocker is described concretely (approval, effort, confusion, or dependency)
- Remove or resequence the blocker: pre-built guides for their IT team, a done-for-you option, or moving the step after first value. Verify: the fix targets the named blocker, not onboarding in general
- Track stall rate at that milestone for the next cohort and alert on any account passing the median days. Verify: the wall's return would be caught in data within one cohort
Variant phrasings
onboarding stuck at same percentage
A related phrasing for the same underlying problem.
milestone where accounts stall
A related phrasing for the same underlying problem.
onboarding wall at SSO or data step
A related phrasing for the same underlying problem.
Compatibility: Compatibility: onboarding milestone tracking in CRM, CS platforms, or project tools, current versions.
Why it happens
Percentages hide sequence. Forty percent is not a state, it is a step, and steps have owners and blockers. Per-milestone timing turns a demoralising plateau into a single fixable step, and cohort stall rates prove whether the fix worked.
Edge cases / pitfalls
- If the wall needs the customer's IT team, the fix includes assets for that team (security docs, setup guides), not more CSM follow-ups.
- Rescheduling the wall step after first value is often better than removing it: value first builds the goodwill the hard step needs.
- Some stalls are the customer's budget or staffing freeze. Mark those honestly instead of counting them as product walls.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_KKARNif5Y3OpE53i7qtDGA