Gestalt & Perception in Dashboard Design
Your users' brains are doing the design work whether you plan for it or not.
The Gestalt principles aren't graphic design theory for its own sake — they're a map of how human perception actually works. Understanding them is the difference between a dashboard that guides the eye and one that makes the brain fight for every insight.
By Jonathan Doreau, Aesop Analytics•~7 min read•Dashboard Design
There is a famous experiment from 1999 in which participants were asked to watch a video of two basketball teams and count the passes made by one team. While they were counting, a person in a gorilla suit walked straight through the frame. Roughly half of all participants never saw it. Selective attention — the mechanism that lets us focus — is the same mechanism that makes us blind to things we're not looking for. This is the central problem of dashboard design. You cannot assume your reader will find what matters. You have to engineer it so they cannot miss it.
The Gestalt principles — a framework developed by German psychologists in the 1910s and 1920s — are the closest thing we have to a theory of how the brain constructs meaning from visual information. They explain why certain groupings feel natural, why some elements jump forward and others recede, and why a well-designed dashboard can convey its main finding in under two seconds. Used deliberately, they're among the most practical tools in a dashboard designer's kit.
The brain is always doing design work. The only question is whether yours agrees with it.
How the eye actually moves across a dashboard.
Start here before you place a single element
Eye-tracking research from Tableau — consistent with decades of web UX research — shows that users scan dashboards in one of two predictable patterns, depending on content density. Knowing which pattern your layout invites tells you exactly where to put your most important information.
The F-Pattern
Content-heavy dashboards. Eyes sweep the top, then scan down the left edge, darting right when something catches them.
The Z-Pattern
Lighter, less text-heavy dashboards. Eyes sweep top-left to top-right, diagonal to bottom-left, then across to bottom-right.
Both patterns have a strong implication for layout: top-left is prime real estate. Whatever the reader needs to anchor to — the headline metric, the date range, the dashboard title — belongs there. Work with the grain of natural scanning, not against it. An important number buried in the bottom-right of an F-pattern dashboard will be seen last, if at all.
Practical implication
Before finalizing your layout, trace both patterns over it with a finger. If the most important metric isn't on either path in the first few seconds, move it. The eye-scan pattern doesn't care about your chart ordering logic — it follows visual weight and spatial position.
The seven Gestalt principles that matter for dashboards.
Named for a branch of German psychology — useful for everyone who makes charts
The Gestalt psychologists observed that humans don't perceive visual scenes as collections of isolated elements — they perceive wholes. The brain actively imposes structure, grouping, and meaning on what the eye sees. The principles below are descriptions of how that automatic grouping works. As a designer, your job is to make sure your layout's groupings match the ones you actually intend.
Principle 01
Proximity
Elements that are close together are perceived as a group. A KPI card placed next to its chart reads as "this card explains that chart" — no label required. Use this to build structure without adding lines or boxes.
Principle 02
Similarity
Elements that look alike are perceived as related. If every sales metric is in navy and every cost metric is in terracotta, the reader builds a mental model of your color coding in seconds — and then uses it automatically across the rest of the dashboard.
Principle 03
Enclosure
Elements inside a shared boundary are perceived as a group. A background panel, a border, or a card container groups its contents without needing any explicit label. Use enclosure to signal sections without header text.
Principle 04
Continuity
Elements arranged on a line or curve are perceived as belonging together. A row of KPI cards reads as a series. A trend line invites the eye to follow it past the last data point. Align related elements along a common axis.
Principle 05
Closure
The brain completes incomplete shapes. A partially-drawn rectangle is perceived as a rectangle. This means you can hint at groupings without fully drawing them — a three-sided box closes itself in the reader's mind, with less visual weight than a full border.
Principle 06
Connection
Elements visually connected — by a line, a shared color, an arrow — are perceived as more related than adjacent elements that aren't connected. Use lines sparingly; they're a strong grouping signal and will override proximity.
Principle 07
Symmetry
Symmetrical arrangements feel stable and ordered. Asymmetry creates tension and draws attention. A single asymmetric element in an otherwise symmetric layout will catch the eye — use this deliberately to highlight anomalies.
Remember
These principles conflict.
Proximity and similarity pull in different directions when two elements are close but different colors. Connection overrides proximity. Being explicit about which principle you're relying on for each grouping prevents your layout from sending mixed signals.
Putting it together: a before and after.
The same data, two very different readings
The principles above only matter if they change how you build. Here is a concrete example: a simple sales dashboard, laid out first without deliberate application of Gestalt principles, then redesigned with them.
Before: proximity and similarity working against each other
Same data — grouped by chart type rather than by meaning
All three KPIs look identical — the reader has no idea which matters most. The chart placement follows column logic, not conceptual grouping. Color is uniform — every bar identical — carrying zero information.
After: proximity, similarity, hierarchy, and enclosure all working together
Same data — grouped by meaning, emphasized by importance
The primary metric commands the top-left with navy and large type. Secondary KPIs are enclosed together in a shared white card — proximity and enclosure signal they're the same category. The trend chart is large and proximate to the revenue KPI. Color in bars carries meaning: navy = peak, terracotta = miss, grey = on-track.
Four rules to apply Gestalt principles immediately.
Proximity over labels. If two elements belong together conceptually, place them close. If they don't, put space between them. You'll find you need far fewer "Section:" headers when proximity does the grouping.
One enclosure per logical group. A card or background panel should enclose exactly one kind of thing. Mixing unrelated metrics inside the same card because they fit creates false proximity.
Make color do one job. Decide whether color in a given chart means "category" (different series) or "status" (good/bad/neutral). It cannot mean both. If it does both in the same view, the reader's brain will produce the wrong grouping automatically.
Trust asymmetry to flag anomalies. If everything on your dashboard is symmetric and orderly, one deliberately asymmetric element — a larger card, an off-axis number, a break in a sequence — will draw the eye without any annotation. Let the layout point to what matters.
The moral.
Design for the brain you actually have, not the one you wish users had
The Invisible Gorilla experiment isn't a lesson about inattentive people — the participants were paying close attention, just to the wrong thing. That is exactly what happens when a dashboard is laid out without a theory of perception. Users pay attention, diligently, to whatever the visual hierarchy says is most important. If the hierarchy is an accident — if it emerged from where the charts happened to fit — then users will consciously track the wrong gorilla and never notice the one walking through the center of the frame.
The Gestalt principles give you that theory of perception. They're not about making dashboards look elegant, though the result often is elegant. They're about encoding the right answer to the question "where should I look and what does it mean?" directly into the layout — so the reader's brain arrives at your intended conclusion before they've consciously decided to look for it.
That's the point of all of it. Not prettier charts. Faster, more accurate decisions.