Forcing a newbie tour angers people who already know the product

What it is

After a redesign, a device switch, or an account merge, dropping people who can already work into a forced tour built for novices is read as an insult: the system voids learning already paid for. Anger is not only affect. It becomes a clear-the-board strategy that closes delta copy too, so the few steps that actually changed never get taught. This is the specific harm when migrants meet a forced novice path—not the general claim that forced tours are obstacles. The audience already holds an old model; the content is a from-zero course.

Why it happens

Underestimated competence triggers pushback. Experienced people can already finish the core task with the old model; the forced class demands their time for “how to create the first item.” The goal conflict is sharper than ordinary blocking: blocking delays the current job; a forced newbie class also denies identity (“you are new”). Once pushback starts, skip, hammer-taps, and bad ratings run harder than for novices, because they know they are entitled to be angry. Worse, the forced class spends the slot that should have spoken the delta: after the whole segment is classed as “that layer,” a sandwiched “export moved” is thrown away too. Recognizing migrants is not hard—old-version activity, imported old data, “I used the previous product”—yet install counters often treat them as new installs. Device switch is the usual misfire: locally there is no seen flag; in the cloud the account is three years old.

Studying it

Split active old-version users into a forced novice tour, skippable delta copy, and no automatic teaching. The task is one they already know.

Independent variables: whether it is forced, whether content is from-zero or delta, whether the system recognized the old account. Dependent variables: anger or “treated as a novice” before completion, skip speed, later dismiss of automatic copy, whether they hunt for rollback.

Do not run this on fresh signups. A reinstall-on-new-device arm is required; misfires cluster there.

Where it stops holding

When the safety model changed and old skills will cause harm in the new version (share now public by default), a block is required—but the block should be that one delta, not a whole newbie class. A new employee on a migrated company account is a new person on an old account and needs from-zero; detect “has this person done the core task,” not account creation date. Forced courses in a contractual training environment are out of scope here.

Applying it

• For accounts with old data, old-version activity, or an explicit “I came from the previous version,” skip the novice tour by default and offer skippable delta copy only.
• Seen and mastery follow the account, not the install; a new device must not replay the newbie class.
• Put a must-block safety change on its own layer whose copy is “this one thing changed,” not in newbie skin.
• Verify by signing a long-used account in on a new device. A from-zero tour that cannot immediately yield an operable UI is a misfire. Check whether those people, after closing it, still hit unexplained deltas—if so, the forced class both angered and failed to teach.

Related

• Within the group: H2.11.1 Migrating users need the delta, not a from-zero lesson · H2.11.2 Keeping old terms and layout habits lowers migration cost · H2.11.4 A migration window needs a comparison or a way back
• Adjacent: H2.04 Skippable and replayable guidance · H2.07 Hint Restraint · H6.06 Multi-device sessions
• Search terms: forced re-onboarding · expert users · treat as novice