Private and public places tolerate different behaviour; the same function must be designed per setting
Aliases: setting-dependent UX · public-private split · place-varying tolerance · frontstage interaction
What it is
Pinching the air in your own kitchen and pinning a recipe to the stove is almost nobody’s business; take the same motion and the same panel to the door of a restaurant open kitchen and tolerance drops at once. Contextual acceptability says the same function has different allowed borders in private and public places, and behaviour has to switch by setting rather than ship one “works everywhere” default.
This is not how conspicuous the device is, and not how large the gestures are — those two push the same way in every public place. Here the type of place itself rewrites what counts as too much.
Why it happens
Goffman’s frontstage and backstage: home and a cubicle are backstage, where actions not aimed at an audience are allowed; street, shop floor, reception are frontstage, where actions are treated as visible to everyone present. Headset functions (pin a note, record a clip, call out a command, operate on air) are tools backstage and social events frontstage. Bring the backstage default through the door and bystanders judge it on frontstage manners, while the wearer, on backstage habit, thinks “I didn’t bother anyone.” The clash is the same function crossing a place border the product did not follow.
Per-setting is not a reskin. Whether capture may save, gesture amplitude, speaker volume, whether overlays stay resident — any of these may need a step-down at the doorway. People cannot be trusted to remember “don’t record at the office.” When the place changes, the default should change.
Studying it
Repeated measures across settings: the same functions, the same people, at home, in an open office, in a shop, on the street. Log which functions are voluntarily enabled, which bystanders interrupt, how wearers change their motion. Acceptability scales should be split by setting, not collapsed to one total.
Setting factors: private–public axis, whether others are acquaintances, whether there is a service relation (staff/customer). Scores: enablement rate, voluntary suppression, interruptions, later regret at having used it there.
A lab “pretend you are on the subway” is weaker than a real subway. At least one real public point.
Where it stops holding
“Private” is not four walls: a desk in an open office is still semi-public, and a backstage move into the aisle will still be judged too much. An event of only wearers who already agreed they are doing the same thing (workshop, rehearsal) is a temporary backstage and tolerance rises. Cultures draw the private/public line differently; a default from one city’s street will not copy. A consent procedure settles “is capture allowed”; it does not automatically raise tolerance for large moves or loud voice — permitted to shoot, still maybe not permitted to sweep in the shop. Safety-critical functions (navigating a crossing) cannot be user-killed for “this is public, socially awkward” with no substitute; a less conspicuous equivalent channel has to exist.
Applying it
- Give functions place tiers: home / work zone / semi-public / public. Crossing a tier changes defaults: public kills save, shrinks gestures, ducks voice, makes overlays on-demand.
- Switch tiers with a geofence or an arrival confirm, and show the wearer the current tier. Do not carry last night’s home settings into the public tier.
- Keep a path that can finish the task in every tier; change how conspicuous it is. Do not delete the function in public until it cannot be finished.
- How to check: the same “pin a recipe and cook from it” task in a home kitchen and at the door of a restaurant kitchen. Home should allow loud, resident, recordable; the door should drop to no-save, small motion, short cues. Identical behaviour in both places means the setting tier is not hooked up.
Related
- Same group:N5.11.1 Without an externally visible recording indicator, bystanders cannot tell if they are being captured · N5.11.2 How conspicuous the device looks directly affects willingness to wear it in public · N5.11.3 Large gestures in public cause social embarrassment and suppress use · N5.11.4 Bystander notice and consent have no unified protocol and depend on venue self-regulation
- Nearby:N5.06 Bystanders · N2.13 Physical Safety of Input (Collisions and Bystanders)
- Search terms:
contextual acceptability·frontstage backstage·setting-dependent interaction
Cards in the same group
- N5.11.1Without an externally visible recording indicator, bystanders cannot tell if they are being captured
- N5.11.2How conspicuous the device looks directly affects willingness to wear it in public
- N5.11.3Large gestures in public cause social embarrassment and suppress use
- N5.11.4Bystander notice and consent have no unified protocol and depend on venue self-regulation