Onboarding pattern
Just-in-time onboarding pattern
Just-in-time onboarding shows help, tooltips, or guidance only when the user reaches the relevant feature for the first time. There is no upfront walkthrough — instruction happens at the moment of use. Often the most user-respectful onboarding pattern.
Verified · editorial policy
How the pattern works
The user is dropped into the product on first login with no walkthrough. As they explore and reach new features, contextual tooltips appear explaining the feature. After first use, the tooltips do not show again.
Best for
Products experienced users return to (CRMs, project management, design tools). Products with many features but most users only use a subset. Multi-persona products where the upfront walkthrough cannot cover all paths.
Worst for
Products with non-obvious core flow. Products where the first 60 seconds determine activation. Products where the user has no context for what they should do first.
Activation metric
Feature-first-use rate. Track which features users discover via just-in-time prompts vs which they never find. Hidden features are the redesign target.
Implementation considerations
- Map the features in the product. For each, decide whether the first-use experience needs explanation or can be self-evident.
- Write contextual tooltips for the features that need them. Keep each tooltip to 1-2 sentences.
- Track first-use events. Features users never reach without a tooltip are candidates for promotion into a more proactive onboarding pattern.
- Make tooltips dismissable and never auto-repeat. The user controls the pace.
Common mistakes
- Tooltips that auto-repeat after dismissal. Users feel patronized.
- Just-in-time onboarding for products where the first-action is non-obvious. The user freezes in front of the empty state.
- Skipping any onboarding entirely and calling it just-in-time. Just-in-time still requires designed tooltips at first-use moments.
Variations
- Spotlight just-in-time — single-element highlight pulse when user reaches a relevant area.
- Inline just-in-time — explanations baked into the feature's UI itself, fading over multiple uses.
- Conditional just-in-time — tooltips appear only when the user appears stuck (e.g. hovering without clicking).
Frequently asked
- Should just-in-time onboarding have any upfront component?
- Usually a minimal welcome screen explaining the product's core value, then drop into product. Some products do well with literally zero upfront onboarding; depends on whether the first action is self-evident.
Other onboarding patterns
Test the pattern, do not commit blindly
The right onboarding pattern is product-specific. Test the activation rate before fully committing.