People need an explicit way to turn personalization off and restore a fixed order
Aliases: restore default order · disable adaptive nav · freeze slots
What it is
As long as the system still reorders nav personally, people must be able to turn it off explicitly and return to a fixed order. Off is not hoping a cookie-clear works, nor an implicit exit that dies when the browser changes. It is a findable, nameable switch: after it is off, slots return to the site default (or to an order the user pinned) and stay that way across sessions. Without a switch, people whose spatial memory was broken can only endure or leave. A switch buried in an experiment flag equals none.
What is restored is the order contract, not the deletion of the recommended module—the module may stay in its partition and simply stop twitching core slots.
Why it happens
Gains from personalized order concentrate on the users the algorithm matches. Costs sit on the unmatched (shared computers, assistive tech, a new role, support following a manual). Those people cannot adapt by “using it more,” because their usage is not the distribution the algorithm assumed. An exit changes the cost from forced adaptation into an option. The switch must change actual order, not only recommended content: if slots still jitter after off, the sense of control is fake and settings will not be sought next time.
Findability decides whether the exit is real. Buried in an unrelated privacy deep page, it demands a successful settings lookup—the very capacity the nav is already harming.
Studying it
Measure whether the switch can be found, whether order actually freezes after off, and whether that freeze holds across sessions.
- Paradigms: after misclicks caused by reordering, find the off switch; compare a switch near the nav versus one in deep privacy settings. After off, feed new frequency and watch whether slots still move. Return the next day.
- Independent variables: location and name of the switch, whether the recommended module remains after off, whether a re-login is required before it takes effect.
- Dependent variables: time and success finding the switch, whether misclicks fall after off, whether next-day order is still fixed, whether off is understood as “sign out.”
- Methodological note: telling the lab “there is a setting” overestimates findability. Start from the misclick with no hint. If off is implemented as “reset learning” rather than “fixed from now on,” the algorithm starts ranking again in a few days and people conclude the switch is broken.
Where it stops holding
A product with no personalized reorder does not need this switch; inventing one implies a ranking people cannot turn off. An A/B flag is not a user switch. Legally or safety-fixed orders (items on a trade confirmation) should never have been personalized, so there is nothing to turn off. “Off for this device” and “off for this account” are different scopes; default should be account-level, with a note that device-level will not follow the account.
Applying it
- In settings, offer “use a fixed nav order / use my ranking,” with fixed as the default or at least equally findable. After off, core slots immediately return to the default table and persist on the account.
- Avoid names like “smart” or “optimized” that have no checkable opposite. Use “fixed order,” which can be verified after off.
- Verify: turn personal ranking on until “it moved” happens, then find off with no hint. After it is off, artificially boost another item’s frequency; core order should not move. The next day, the same account still shows the fixed table. Unfindable, still jittering after off, or understood as sign-out means the switch does not exist.
Related
- Within the group: G2.10.1 Reordering nav items by frequency unfixes their positions and hurts predictability · G2.10.2 Personalized recommended items appearing and disappearing interrupt spatial memory · G2.10.3 Stable core nav and personalized modules must be partitioned · G2.10.4 Personalized ranking belongs on secondary entrances, not on primary-task nav
- Adjacent: G2.07 Navigation consistency · E5.16 Shortcuts and pinned items · G2.06 Global and local navigation
- Search terms:
opt out personalization·restore default nav order·adaptive navigation
Cards in the same group
- G2.10.1Reordering nav items by frequency unfixes their positions and hurts predictability
- G2.10.2Personalized recommended items appearing and disappearing interrupt spatial memory
- G2.10.3Stable core nav and personalized modules must be partitioned and must not invade each other
- G2.10.4Personalized ranking belongs on secondary entrances, not on primary-task nav