Users cannot give each other directions; shared screenshots no longer match anyone else’s interface

What it is

“Look at the third row on home,” “under the red button in the screenshot” — those sentences assume both people see the same picture. After personalization, row three is not the same title, and the red button may not be on the other person’s home at all. A non-shareable personalized UI is the shared visual reference that teaching, support, and word of mouth rely on, taken apart. Screenshots and relative positions are no longer a public language.

Not finding yesterday’s item is time. Here the reference between people collapses.

Why it happens

Collaboration and support depend on an alignable display: same entry, same object, same relative position. Personalization makes a display per person; alignment fails. Support reads a script: “scroll to Sport”; Sport may have been dropped from this user’s home. A friend’s screenshot does not map onto one’s own device, so they have to send a deep link or a title instead. If the deep link still opens For You rather than the object, sharing fails a second time.

Teaching cost moves from “point” to “describe the object itself.” Streams with no stable title or ID (wordless short video) are almost impossible to pass by mouth. The more a product leans on visual-spatial memory, the more personalization hurts the public language.

Studying it

Paired tasks: one person directs from their own screen, the other executes on their own personalised home (find a function, find a title). Measure: success, times they switch to title/link, frustration on both sides. Independent variables: whether a deep link is allowed, whether the deep link bypasses personalization, whether structure is shared between the two. Dependent variables: failure rate of pointing language, rate of switching to object identifiers.

In support, replace “teacher” with a script. Where the script fails on a personalised home is where the public language broke.

Where it stops holding

Toolbars and system settings are usually still shared, so pointing still works. One-to-one screen share (cast, remote assist) temporarily restores alignment; it is not the product default. Public creator pages and title pages address by object and are not affected by home personalization. This entry is interpersonal reference. It does not require structure to be stable, and it does not restate a search fallback — though people will flee toward those channels when this fails.

Applying it

• Sharing should carry an object deep link that opens on that object, not on a relative seat in For You.
• Support and help copy should use object names and fixed entries (search, history). Ban “row three,” “the red bit.”
• Check: two people, neither seeing the other’s screen; one directs the other to a home item by relative position. After failure, allow only title or link. If only the second attempt works, the public language is already only the object layer, and the product should make that layer first-class sharing.

Related

• Same group: L6.12.1 Personalization makes the same entry show different content, so location memory fails · L6.12.2 Content that changes over time makes previously seen items hard to find again · L6.12.4 Stable structure with variable content is easier to master than a structure that also moves · L6.12.5 Search and history that are not personalized must exist as a fallback
• Nearby: L6.06 Inferred Preferences and Their Limits · L6.05 Turning Personalization Off · L4.08 Visibility of Task Progress
• Search terms: non-shareable personalized UI · unshareable screenshots · common ground