Concurrent use needs an arbitration rule

What it is

When two people issue incompatible commands to one public screen—one pages, the other pauses; two hands pull the same picture opposite ways—the system has to pick the next state by a rule that can be stated in advance. Otherwise the person who presses harder or taps faster wins. Conflict arbitration is that visible rule, and whether people present can see why this outcome happened when it is applied. It assumes inputs already have owners. Without attribution, conflict only looks like the picture jumping.

Why it happens

A public screen is one indivisible field of pixels. Desktop windows can be one per person; the main content on a wall is often singular: the map’s centre, a video’s playhead, the current menu page. Incompatible acts cannot both be true, so someone’s intent must be dropped. If dropping is implemented as last-write-wins or “whoever has more contacts,” a rule exists, it just was never announced, and people read it as a bug or as being robbed.

Visible arbitration turns the drop into a coordination resource. Turns, locks, spatial partitions, host-and-guest roles all tell a newcomer: this is not your window to change the global state. Without that layer, people arbitrate with bodies—blocking, crowding, peeling a hand away—and the social cost moves from the interface into elbows. Parallel use on deployments like CityWall often works because content splits into many objects and global conflict is localized. Once a single global object remains, arbitration stops being optional.

Studying it

Give two participants a task that must conflict: one timeline, one viewport, one draggable object. Compare no announced rule (last write wins), explicit locking, partitioning, and taking turns. Code verbal negotiation, bodily crowding, and abandonment. Tabletop CSCW on locking and optimistic concurrency is a contrast class, but public-screen users are often strangers without a shared goal, so the negotiation channel is shorter.

Independent variables: arbitration policy (overwrite / lock / partition / turns), whether the rule is visible in the UI, whether the contested object is global or a splittable local. Dependent variables: task completion, bodily intervention during conflicts, whether people can later say “why it listened to them,” abandonment.

Lab pairs yield the floor too politely, which under-measures the need. In the field, catch true simultaneous hands-on, not back-to-back solo sessions. Do not read “few conflicts” as “no rule needed”—that can mean the second person never dared to start.

Where it stops holding

When content splits by nature (a photo each, a game character each), global arbitration is almost unused and local ownership is enough. A guided tour with one lead and onlookers should resolve conflict by role, not by tap speed. Emergency copy and alert takeover must be able to override play in progress; “the current user decides” then becomes a safety problem. A remote second user on a laggy link adds stale operations; that is a consistency problem on top of the social one.

Applying it

• Before shipping a global object (full-screen paging, a single video, a single map centre), write down who wins on conflict, and draw the result: a lock, whose turn, which zone belongs to whom.
• Split content that can be split so conflict stays local; keep only the state that must be unique at the global layer.
• If last-write-wins is the chosen rule, still show the overwritten party who interrupted them, so the event is not filed as random failure.
• Verify by asking two people to attempt incompatible acts at once. Check that the outcome matches the written rule and that the losing party understands why. If they do not, or they switch to elbows, the rule has not entered the interface.

Related

• Within the group: K7.04.1 Input needs a visible owner · K7.04.3 Personal information does not belong on a shared screen
• Adjacent: V3.02 Conflict handling · V3.05 Transfer and arbitration of control · V3.03 Locking and optimistic concurrency
• Search terms: conflict arbitration · turn-taking · multi-user display · global object