The indicator must locate activity to a specific passage rather than the document alone
Aliases: region-level awareness · edit scope cue · local presence
What it is
Localized edit awareness binds “someone is editing” to a passage, block, object, or property. A document-level cue reveals activity in the same container but not whether a planned change overlaps, encouraging avoidance of the whole document. The appropriate granularity follows the conflict unit and is not always a paragraph.
Why it happens
Soft coordination depends on estimating overlap. A coarse cue merges unrelated edits into one risk and creates waiting; an overly fine cue misses structural dependencies such as a title affecting navigation or a component affecting instances. The system must derive direct and affected scope from its data model and distinguish uncertain downstream impact from exact cursor position.
Studying it
In long documents or structured canvases, compare document-, block-, and property-level cues on unnecessary yielding, true conflicts, localization time, and interpretation. Include independent regions and cross-region dependencies to expose both coarse and narrow failures. Interviews should verify the conflict unit users perceive.
Where it stops holding
Paragraph boundaries are unstable during split and merge; database fields and design components have different dependencies. Location can reveal sensitive object names. When affected scope cannot be computed reliably, uncertainty is safer than false precision.
Applying it
- Attach editors to the actual conflict object and let users inspect affected relationships.
- Separate exact activity from related regions that may be affected.
- When activity is off-screen, use a lightweight navigation cue rather than a global warning.
- Compare over-yielding and missed conflict on independent and cross-region tasks.
Related
- Same group: V2.06.1 Cues support yielding rather than blocking · V2.06.2 Cues must appear when editing starts · V2.06.4 Retention time determines accuracy · V2.06.5 False positives destroy trust
- Adjacent: V2.02 Workspace awareness · V3.02 Conflict handling
- Search terms:
localized edit awareness·conflict scope·workspace awareness
Cards in the same group
- V2.06.1An editing indicator should support voluntary yielding rather than block modification
- V2.06.2The indicator must appear when editing begins, not after a conflict
- 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