Elements enclosed within a shared boundary are perceived as belonging to the same group — regardless of proximity or similarity. The boundary itself creates the group, before any reading occurs.
The Law of Common Region, introduced by Stephen Palmer in 1992, adds a principle the other Gestalt laws miss. Where Proximity says “things close together are perceived as related” and Similarity says “things that look alike are perceived as related,” Common Region says something more fundamental: things enclosed within the same boundary are perceived as a group — before proximity, before similarity, before any reading begins.
A border, a background fill, a column boundary, a card — any visible enclosure creates a perceptual container. Whatever is inside that container is automatically grouped by the visual system in under 100 milliseconds. The user doesn't decide to group them. The boundary makes the decision for them, automatically and instantly.
This is why the Kanban board is one of the most intuitive tools in software. Strip away the column regions — present the same tasks in a flat list with status labels — and users must read every label to reconstruct the workflow state. Add the column boundaries back, and the entire state of the project is visible at a glance, before a word is read. The information is identical. The boundary is everything.
“A region of space enclosed by a boundary is perceived as a distinct group — one of the most powerful principles of perceptual organisation.”
— Stephen Palmer, Vision Science, 1999
Both versions below contain the same twelve tasks, the same status labels, the same assignees, the same due dates. The bad version presents them as a flat list with status tags on each card. The good version encloses them in three column regions. The difference in comprehension time — how long it takes to answer “what is currently in progress?” — is not a matter of seconds. It is a matter of whether the question requires reading at all.
The Kanban board is the canonical application of Common Region in product design — but notice what makes it work: the column background colour is doing most of the heavy lifting. There is no border between columns, no line separating To Do from In Progress. The shared background fill of each column is sufficient to create the perceptual region. Palmer's insight was that any enclosed surface — not just a visible border — creates a group.
Notice also that in the good version, the status tags on individual cards become redundant. The column already communicates status. The tags can now be repurposed to show the task type — Design, Docs — without creating confusion about what status means. When the boundary carries the status signal, the label is freed to carry something else.
Common Region doesn't require a visible border. Any enclosed surface creates a perceptual region — and that enclosure can be defined by spacing and hierarchy just as effectively as by a drawn line. The filter sidebar is a case where heavy card borders around each section actively hurt: they add visual weight, fragment the panel, and make it feel busier without adding any structural information that a divider and section header couldn't carry alone.
The bad version encloses each filter group in a bordered card. The good version uses only section headers, dividers between groups, and consistent internal spacing. The perceptual grouping is identical — each section is still a region — but the visual weight is far lower. The same twelve filter options feel calmer and easier to scan when the boundary is implied rather than drawn.
This is the subtler side of Common Region: knowing when not to draw a boundary. A border is a strong signal — it adds weight and closure. In a narrow filter panel that already has section headers and consistent spacing, the border is redundant. The region already exists. Drawing a box around it adds noise, not clarity. The best boundary is often the lightest one that still does the job.
Common Region's audit question is simple: can a user determine the categorical structure of this screen without reading any labels? If the answer is no — if they must read to understand grouping — the structure is being communicated by text rather than by visual boundaries. Adding a shared background, a card border, or a column fill transfers that burden from reading to perception.
The principle applies wherever you have items that belong to distinct categories: settings pages, dashboards, onboarding flows, form sections, search results with different types. The mechanism is always the same — enclose the members of each category in a shared visual boundary, and the grouping becomes perceptible before comprehension begins.
Palmer, S. E. (1992). Common region: A new principle of perceptual grouping. Cognitive Psychology, 24(3), 436–447. · Palmer, S. E. (1999). Vision science: Photons to phenomenology. MIT Press.