An editing indicator should support voluntary yielding rather than block modification
Aliases: soft coordination · editing presence cue · concurrency awareness
What it is
An edit awareness cue tells collaborators that someone is working in a location so they can wait, move, or contact them. This is soft coordination: it informs action without revoking editing rights. Unlike locking, it permits parallel and intentional co-editing. Conflicts remain possible, so preservation and merge mechanisms are still required.
Why it happens
Many collisions can be avoided through social negotiation before they occur. Seeing activity on a specific object lets users yield according to urgency, relationship, and edit scope, avoiding queues and abandoned locks. If a cue looks prohibitive, it becomes an ownerless de facto lock; if treated as a guarantee, missed activity creates false safety.
Studying it
Compare no cue, awareness cues, and hard locks in shared editing. Measure parallelism, voluntary yielding, conflict, waiting, communication, and overwrite. Ask whether participants understood the cue as information, advice, or prohibition. Include both safely parallel and mutually exclusive changes so the value of choice is observable.
Where it stops holding
Payments, publication, and irreversible configuration may need transactions or locks. Anonymous or adversarial collaboration cannot assume yielding. Pair writing may intentionally edit the same region, where an overly strong cue creates needless avoidance.
Applying it
- State the fact that someone is editing without disabled controls or prohibitive styling.
- Preserve choices to continue, contact the editor, or move elsewhere.
- Retain both operations and recoverable conflict handling despite the cue.
- Test parallel and exclusive tasks for waiting, collision, and semantic misunderstanding.
Related
- Same group: V2.06.2 Cues must appear when editing starts · V2.06.3 Cues need local scope · V2.06.4 Retention time determines accuracy · V2.06.5 False positives destroy trust
- Adjacent: V3.01 Concurrent editing · V3.03 Locking and optimistic concurrency
- Search terms:
edit awareness cue·soft coordination·concurrency awareness
Cards in the same group
- V2.06.2The indicator must appear when editing begins, not after a conflict
- V2.06.3The indicator must locate activity to a specific passage rather than the document alone
- V2.06.4How long an indicator persists after input stops determines its accuracy
- V2.06.5Frequent false editing indicators lead users to abandon the signal