C3.20.2First-run coaching does not sustain discoverabilitydesignresearch

First-run coaching cannot carry long-term discoverability

Aliases: onboarding overlay · first-launch tutorial · coach mark

What it is

Launch overlays, slideshows, and “try swiping” squeeze teaching into a moment with no real task. First-run coaching cannot carry discoverability over time: watching is not learning, and learning is not retrieval weeks later. The gesture still has no shape; when the tutorial vanishes, the discovery channel vanishes with it. Outsourcing discoverability to first open mistakes a memory problem for a one-shot notice.

Why it happens

Episodic memory decays fast for instructions unbound to a goal. Someone mimics a swipe in coaching; the mail that actually needs archiving arrives three days later, when the overlay will never return. Launch chores—skip, grant, fill forms—already consume attention. Even a correctly stored stroke lacks retrieval cues, because everyday chrome does not look like the tutorial card. First-run coaching buys one exposure, not a repeatable recognition condition.

Studying it

Separate coaching from delayed probes: after the tutorial, give a real task at 1 and 7 days and count spontaneous gesture use versus hunting for a button. Factors include coaching form (overlay, video, forced practice) and whether skip is allowed. Measures include spontaneous use, wrong strokes, and switches to visible entries. Tutorial completion is not discoverability—it only shows that Next was tapped.

Where it stops holding

Forced practice followed immediately by a real task (the first message after install needs archiving) retains better; that is already closer to in-context teaching. An expert tool’s empty state can demonstrate once, but not every later feature. A system update that mentions a new gesture once in release notes fails the same way. This leaf does not pick the beat inside a task on which to hint—that is teaching timing.

Applying it

  • Do not bet primary-path discovery on a launch overlay; overlays close, everyday chrome must still reveal the action.
  • Allow skipping, and make “show me later” retrievable instead of one-shot.
  • Track spontaneous gesture rate on real tasks, stratified by days since install; near-zero on day seven means coaching never became a discovery channel.

Related

  • Same group: C3.20.1 Gestures take no screen area, and are therefore invisible · C3.20.3 Local visual previews beat centralized teaching · C3.20.4 A gesture cannot be the only path to a function
  • Adjacent: C3.32 When to teach gestures · C3.21 Gesture memory load
  • Search: onboarding overlay · first-run coaching · gesture retention

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/C3.20.2