Forced tours are treated as obstacles
Aliases: blocking tour · unskippable tutorial · onboarding dark pattern
What it is
Forced guidance means people must watch or tap through teaching before they can reach an operable UI: no skip, skip plus a confirm, or a reskin that returns the moment it is closed. They will not encode this as help. They will encode it as an obstacle in the path—the same class as a popup ad or a forced update. This entry is about that qualitative shift and its aftermath once force is in play. It is not how to build the skip control, and not the special case of migrants stuffed into a newbie class.
Why it happens
When a goal is blocked, affect and strategy switch together. The goal was “make the first item”; after the obstacle it becomes “remove this plate.” Teaching sentences are not read under that strategy; buttons are hit by reach, not by meaning. A layer down, attribution lands on the product: even if first success comes later, it carries the memory of being checkpointed, so trust opens at a loss. Force also trains a lasting counter-rule—“always dismiss this kind of layer”—and later, genuinely useful just-in-time copy is swept away by the same rule. Force is therefore not a few extra sentences; it spends the first impression to buy failure of all later teaching. Fake skip (close yields another card; skip costs a fifteen-second ad) reads as fraud more than no skip, because the control promised refusal and did not pay.
Studying it
Compare a skippable tour, an unskippable tap-through, and a fake skip that actually advances. Time-limit the main task.
Independent variables: whether teaching can truly end, whether ending is delayed (countdown, second confirm). Dependent variables: reading time during the block (below readable duration or not), attitude after completion, later voluntary use of help, speed of dismissing the next automatic explanation.
Polite lab participants will endure; attitude still moves. In live funnels the forced arm leaves at the gate; do not compare “who remembered more after being taught” only among those who stayed.
Where it stops holding
Forced dwell for safety, irreversible money, or legal consent is not teaching and should use a different surface and voice so it is not classed as a tour. Enterprise training accounts under contract may require a course; that is a class, not a product gate, and daily work login must not reuse the path. Games and creative tools that treat a short demo as part of play get lighter attribution; moved onto a tools SaaS, attribution returns to obstacle. For assistive-tech users who must walk every layer linearly, the cost is focus trapped in teaching; escape must actually leave, not merely look closable.
Applying it
- Do not default first use to “tap through / wait out a timer to enter the app”; the teaching layer must be tear-downable at any moment.
- Do not fake skip: one click must open an operable UI; no extra confirm, no “one last thing.”
- Reserve true force for legal or safety blocks, on a surface that does not look like a tour, so the “explanation” category stays unpolluted.
- Verify with someone uninvolved in the design walking install. Cursing the plate, hammering taps, or asking “how do I turn this off” means it is an obstacle. Make it skippable and compare activation, not tour completion.