Design Principle
Collaborative interfaces need to show who is present, who is editing, and how conflicts resolve.
Principle
Collaborative interfaces need to show who is present, who is editing, and how conflicts resolve.
Design action
Show member avatars, cursors/selections, edit locks or conflict hints; use save state and history to explain collaboration outcomes.
Examples
Positive example: Docs, whiteboards, design systems, project planning, and multi-person review flows. Counterexample: Multiple people edit with no presence or conflict signals.
Apply when
Docs, whiteboards, design systems, project planning, and multi-person review flows. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from Apple HIG, Material Design, GOV.UK/Polaris/Atlassian component practices, and interaction accessibility principles. Apple HIG Motion: https://developer.apple.com/design/human-interface-guidelines/motion Material Design Motion: https://m3.material.io/styles/motion/overview/how-it-works GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Shopify Polaris Patterns: https://polaris-react.shopify.com/patterns Atlassian Empty State: https://atlassian.design/components/empty-state
Agent Directive
Show member avatars, cursors/selections, edit locks or conflict hints; use save state and history to explain collaboration outcomes.