🧯
Reactive onboarding is a method of educating users about your product, by explaining what, and why something happened.
Featured in 8 UX Bites
Similar psychology:
If someone presses a shortcut that means something different in your product, you could show a tooltip explaining what it does here, so they learn the difference.

Try reactively prompting the step that finishes a task when someone pauses partway and then waits, so they don't assume it's already done.

An empty search could become reactive onboarding: when it returns no results, explain what the search can and can't do, so people know how to ask next time.

Consider offering onboarding for a better approach once someone has sent several unhappy prompts in a row, rather than waiting for them to find it.

When something is slow to load, it may help to use the wait to explain ways to speed it up, so users learn the faster method while they're feeling the delay.

Reactive onboarding could increase feature usage, by introducing a feature at the moment users hit the problem it solves, rather than in an upfront tour.
Suggesting a shortcut or faster method right as users do something the slow way might help them get tasks done more quickly from then on.
Tips shown only when they relate to what users are doing right then may hold their attention better than upfront tours, which they're likely to skip.
Explaining what just happened and why, straight after a user triggers it, could help users understand a complex product more easily without a lengthy tutorial.