Guidance must be skippable
Aliases: skip tour · dismissible guidance · skip intro
What it is
Automatic teaching in first use—a welcome page, a stepped tour, copy that blocks the work area—must offer a skip that ends teaching immediately and opens an operable UI. Skip is refusal of the whole guidance, not “next page.” Without skip, teaching is a gate; with skip, teaching is a proposal that can be declined. This entry only requires that the right of refusal exists and means the right thing. It is not about where to find the lesson later, and not about how forced tours feel like obstacles—those sit on top of refusal already working.
Why it happens
People arrive with their own task and prior knowledge; the teaching layer cannot know whether this sentence is useful now. Skip returns the decision of “does this enter working memory” to the user: do not encode it, continue the job. The right of refusal also decides legitimacy: an interruption that can be refused is a proposal; one that cannot is a checkpoint. Checkpoints change strategy from reading to hunting an exit; if none exists, people tap at random and the lesson dies in the noise. The skip control must be readable as “end teaching.” Labeling it “next,” or treating a tap on the mask as advance, makes people think they are closing while the gate lengthens. Skip must also exist on every screen, not as a gift on the last: refusal is usually decided on screen one; no exit there means later screens were already forced.
Studying it
Build the same first-run tour as “explicit skip on every screen,” “close only on the last screen,” and “no skip, must tap through.” The job is to make the first thing as soon as possible.
Independent variables: whether skip exists, whether the label means end rather than continue, whether skip ends the set or turns one page. Dependent variables: time to an operable UI, skip rate, whether skippers still complete the first task, frantic taps while blocked.
Lab instructions to “learn the product” suppress skipping. In live install funnels skip is the default; look at activation after skip instead of treating skip as failure. If the unskippable arm counts tour completion as success, it credits people the gate coerced.
Where it stops holding
Legal consent, age gates, and safety notices are not guidance and must not be skippable; keep them off the teaching layer so “skip intro” cannot be mistaken for skipping consent. Pairing or key generation that would leave a half-built state should exit as “cancel and roll back,” not “skip teaching and proceed broken.” After someone has asked to “start the tutorial,” skip is leaving the class and must still exist, perhaps labeled “end tutorial.” A pointerless kiosk with one path needs a physical button or a timeout for skip; it cannot pretend it is not a gate.
Applying it
- Give every automatic teaching segment an explicit skip whose copy is “skip intro / enter the app” and whose action tears down the layer and lands on an operable UI.
- Show skip on the first screen and apply it to the whole set; do not implement it as “next” or as a mask tap that advances.
- After skip, do not immediately block with “are you sure.”
- Verify by skipping on screen one and timing until a clickable main-task entry appears. Any remaining teaching layer, confirm, or slogan screen means skip did not finish.