The Pill-in-the-Hot-Dog Onboarding
Bury the intimidating-but-necessary onboarding step inside familiar, exciting content instead of leading with it
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 90%
When a mandatory onboarding step is psychologically intimidating, leading with it (even as a clean 'step one') suppresses conversion. Schaffer's fix is to embed the scary step inside familiar, appealing material — like hiding a dog's pill in a hot dog — so the user consumes it without the fear response derailing them.
Origin
Laura Schaffer developed this at Twilio after a prescriptive step-by-step onboarding underperformed because 'step one: get a phone number' put telecom — alien and intimidating to developers — front and center without a human present to reassure them.
Core principles
- 01A logical, prescriptive flow can still fail if it triggers the user's psyche negatively
- 02Without a 'safe person' beside them, self-serve users hit intimidating steps alone and bail
- 03Bury the unpleasant-but-required step inside familiar, exciting content (code, their language, docs)
- 04Validate cheaply with an intentionally ugly MVP before building it properly
How to run it
- 1
Find the step that trips the user psychologically
Look for the required action that is outside the user's comfort zone — for Twilio developers it was acquiring and configuring a telecom phone number.
Pro tip If a very logical flow isn't converting, suspect you're battling the user's psyche, not their logic.
- 2
Lead with the familiar, not the scary
Open with content the user recognizes and enjoys (code samples in their language, docs) rather than the intimidating step.
- 3
Embed the scary step inside the familiar flow
Sneak the required action in mid-stream, not as the leading move — e.g. 'go get a phone number' embedded inside a docs/code experience.
- 4
Validate with a deliberately rough MVP
Build the ugliest cheap version to test the hypothesis — Schaffer kicked users out of the portal entirely into a docs page with no easy return button.
Pro tip If it's not embarrassing, you've gone too far — an ugly test yields a cheap, powerful learning either way.
- 5
Build it into onboarding properly once validated
Only after the rough test validates the hypothesis do you invest in integrating it correctly into the real flow.
In the wild
Twilio's step-by-step onboarding led with 'get a phone number' because that's how anyone teaching Twilio 1-on-1 starts. But telecom was alien to developers and, without a person to reassure them, they froze. As an MVP, Schaffer's team kicked users out of the portal into a docs page that opened with code in their language and embedded the phone-number step mid-flow, with no easy return button.
→ The embedded-step version converted better than the clean step-one version, validating that the phone number was the psychological blocker; they then built it into onboarding correctly and it converted even better.
Common mistakes
Leading with the intimidating step because that's how it's taught in person
An instructor-led sequence assumes a reassuring human is present; in self-serve the same 'step one' hits the user's fear response alone and tanks conversion.
Building the full solution before validating the hypothesis
The intimidating step could be the wrong hypothesis; Schaffer tested with an embarrassing throwaway MVP first so a failure would have been a cheap learning rather than wasted build.
Is it for you?
Best for
Self-serve onboarding for technical or complex products with a mandatory step users find intimidating or unfamiliar
Not ideal for
Flows where the required step is genuinely simple and non-threatening — there's nothing to hide
From the transcript
“killing the hot dog”
“if you shove it inside of a hot dog which like looks good and that's exciting then you can get them to consume it more…”
“guess what was step one get a phone number”
“if it's not embarrassing you've gone too far”
From the episode
Career frameworks, A/B testing mistakes, counterintuitive onboarding tips, selling to developers
Laura Schaffer (VP of Growth at Amplitude)