C3.32.1First-launch teaching lacks motivedesignresearch

First-launch teaching happens before motive, so little is retained

Aliases: just-in-case coaching · launch tutorial · unmotivated lesson

What it is

Packing every gesture into a launch slideshow happens before anyone has a goal such as “archive this message.” Teaching without motive retains poorly: having watched and tapped Next is not retrieving the stroke under a later goal. The timing error is “no operation yet,” not the artwork of the slides. Discoverability is about gestures having no shape; this leaf is about teaching parked before the goal appears.

Why it happens

Procedural memory wants practice bound to a goal. At launch the goal is “get into the app”; gesture copy is bypassed information while working memory holds permissions, sign-in, and empty states. Ebbinghaus-like decay is faster without retrieval cues: days later, at a real archive, the demo hand from the slideshow is not in the room. Teaching before need writes memory in the wrong encoding context; the retrieval context does not match.

Studying it

One group watches the gesture lesson at launch, one skips; two days later give a real archive task and compare spontaneous gesture use. Do not probe the same day—that is short-term memory. Log whether the lesson forced a follow-along. Forced practice raises same-day scores; it may not raise delayed scores.

Where it stops holding

An expert tool that forces one practice on an empty canvas and then drops into a real brief still has a chance to bind. Classroom-style teaching in a children’s app is a different setting. A “new gesture” after an OS update that appears only at launch fails the same way as first launch. Bad timing does not prove a help page should never exist.

Applying it

  • Do not make launch slides the only teaching of a primary-path gesture; launch must be skippable.
  • Move the demo to the first moment the action is truly needed.
  • Score spontaneous use on a real task 48 hours after install; launch completion is not learning.

Related

  • Same group: C3.32.2 Contextual hints should appear at the moment of need · C3.32.3 After one successful gesture, do not repeat the same hint · C3.32.4 Teaching should be re-triggerable by the user
  • Adjacent: C3.20 Gesture discoverability · C3.21 Gesture memory load
  • Search: just-in-time instruction · onboarding · encoding specificity

Cards in the same group

Quick Actions

Share

Share this page

ios_share

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