Personalized ranking belongs on secondary entrances, not on primary-task nav

What it is

“Sorted for you” may live in More, overflow, a recommended module, or a content stream. It should not live on the primary nav that carries main tasks. Primary nav is the shared road for core work: place an order, open the timetable, file a repair. Once that road is ordered by personal history, new users, occasional users, and veterans who just switched tasks lose the shared coordinates. Personalization on a secondary entrance saves a little scanning after someone has already reached More. Personalization on the main road spends the whole task’s predictability to buy that saving.

Main tasks are the few the product promises everyone can complete, not whichever items currently have the most clicks. The highest-click items are usually what personalization wants to promote; using them to define “main” is circular.

Why it happens

Main-task nav is shared across people and situations: a support script that says “click the third one,” a training screenshot, an accessible user’s memory, the same hands after an account switch. Personalized order voids those shared descriptions and moves the cost of guidance from the product into every conversation. Secondary entrances do not carry that shared duty; a personal misclick is cheap, and people who have entered a secondary zone are already exploring, so their expectation model allows change.

Personalization on the main road also fights permission visibility: one person lacks an item, the next person’s “personal sort” fills the hole, and even slot counts differ across accounts. Main tasks cannot be described in an external manual.

Studying it

Put personalization on primary versus only on secondary, and compare how guidable main tasks are across user profiles.

• Paradigms: core tasks (checkout entrance, timetable) on a fixed primary versus a personally frequency-sorted primary; participants include new users, returners, and a third person giving spoken directions from a script. A secondary condition runs the same algorithm only on overflow.
• Independent variables: scope of the algorithm (primary / secondary only), whether order differs across accounts.
• Dependent variables: success of spoken directions, first-completion time for new users, skilled misclicks, whether support copy still works without looking at the screen.
• Methodological note: heavy-user completion time alone will support primary personalization. Count “can someone else say how to walk it.” Spoken direction in the lab is a proxy for support and training, not a side question.

Where it stops holding

Single-user professional tools (a personal IDE, a private reader) have little shared spoken-direction road, so the external cost of primary personalization is much lower—though “where it was yesterday for me” still needs to be stable. If primary membership already differs before and after login, that is permission, not personalized ranking; do not stack a personal sort on top of permission differences. A recommended content feed is not primary nav; personalization is its job, and that fact cannot defend ranking the nav.

Applying it

• List main tasks; their entrances go only in a fixed-order primary. The personalization algorithm’s scope must say “primary excluded.”
• Overflow, recommended modules, and in-account Recent may rank personally, labelled as recent or recommended so they are not read as structure.
• Verify by having someone who has not seen the UI complete a main task from one spoken direction (“third from the left in the top bar”). The sentence fails if personalization is on primary; it should still work if personalization is only on secondary. Walk the main task on a fresh account; the primary path should match the veteran’s primary.

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.5 People need an explicit way to turn personalization off and restore a fixed order
• Adjacent: G2.06 Global and local navigation · E5.16 Shortcuts and pinned items · G2.08 Predictability of navigation items
• Search terms: primary navigation · personalized ranking · task-critical nav