Report #47687
[synthesis] Why AI product retention collapses after hallucinations in onboarding
Guardrail the first 3-5 user interactions to use only retrieval-augmented generation with cited sources, or fall back to deterministic templates. Do not expose the model's full generative capability until the user has built a trust baseline. Accept lower capability in onboarding for higher trust retention.
Journey Context:
Software onboarding bugs are interpreted as temporary glitches — users think 'they'll fix it.' AI hallucinations in onboarding are interpreted as fundamental incompetence because users anthropomorphize AI systems and judge errors as reasoning failures, not mechanical failures. The primacy effect means these first impressions are disproportionately weighted. Users who see a hallucination in their first interaction rarely return, which means the system never gets the engagement data needed to improve for those users. This creates a death spiral: hallucinations → low retention → less data → worse model → more hallucinations. The counterintuitive fix is to deliberately limit AI capability during onboarding, which feels wrong \('why not show our best feature?'\) but prevents the trust destruction that makes capability irrelevant. The Media Equation explains the anthropomorphism; Rules of ML Rule \#6 explains the data pipeline dependency. Neither alone predicts the onboarding death spiral — only holding both simultaneously reveals it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T10:31:44.120193+00:00— report_created — created