Problem
Twenty panels, one screen, and no two of them want the same dimensions. A latency chart needs width to be readable, a status tile needs almost nothing, and a table needs height. Left to itself this becomes a ransom note.
Solution
Impose a coordinate system. A fixed column count, a row unit, and panels that snap to multiples of both. Everything aligns because nothing is allowed not to.
The grid is the reason dashboards look like dashboards. It also carries most of the meaning a viewer picks up before reading anything: things the same size read as equally important, things on the same row read as related, and the top-left panel reads as the answer. That last one is unavoidable, so the only question is whether the panel that lands there deserves it.
A grid is a compromise with two edges. Too few columns and every panel is either too wide or too narrow. Too many and the alignment stops being visible, at which point you have absolute positioning with extra steps. Twelve is the near-universal answer because it divides by 2, 3, 4 and 6, which covers halves, thirds, quarters and sixths without fractions.
The part that separates a grid that helps from one that merely tidies: whether panel size is allowed to mean something. If every panel is the same size, the layout says nothing about priority and the viewer has to read all twenty titles. A grid that lets one panel be four times the size of its neighbours can say “start here” without a word of copy.
Use when
More than a handful of panels share a page and viewers scan rather than read. Which is nearly every dashboard.
Don’t use when
The page has a reading order. A narrative that walks someone through an argument wants a single column, because a grid invites the eye to jump and a narrative depends on it not doing that.
Trade-offs
Grids reward panels that fit the grid, so the layout starts to shape the content: people pick a visualisation because it tiles well rather than because it answers the question. Everything looking equally considered makes it hard to tell a load-bearing panel from one somebody added in 2023 and forgot. Responsive behaviour is where grids fail, because a twelve-column layout reflowing to one column produces an order nobody designed and rarely the priority order. And drag-and-drop editing makes it trivial to create a layout that works on the author’s monitor and nowhere else.
Checklist
- How many columns, and does the count support the fractions this page needs?
- Does the top-left panel deserve to be the first thing read?
- Does panel size encode importance, or is everything the same size by default?
- Do panels on a row belong together, or did they land there by packing?
- What order do panels take when the grid collapses to one column?
- What is the shortest viewport this page is used at, and what falls below the fold there?
- Is there a minimum size below which a given panel type stops being readable?
- Do gaps and alignment survive panels with different title lengths?
- Can an author create a layout that only works at their window size?
- Is the arrangement stable, or does it reflow differently for different viewers?
Compare
Grafana uses a 24-unit horizontal grid with drag-and-drop sizing and a packing behaviour that pulls panels upward into gaps, which makes editing fast and means moving one panel can rearrange several others. Datadog offers both a fixed grid and a free-form canvas, so a team can choose between consistency and expressive layout, and most eventually regret whichever they picked. Kibana treats panels as cards on a resizable grid with each panel carrying its own query, which pushes coherence entirely onto whoever assembles the page. Honeycomb barely has this pattern: the primary surface is a query and its result, so composition happens in boards that collect saved queries rather than in a canvas of independent tiles.
Related
Collapsible row is how a grid survives past one screen. Dense small-multiple layout is the grid pushed to its limit deliberately. Header KPI strip is the grid’s top row doing a specific job. Resizable card grid is what happens when the viewer, not the author, controls the arrangement. Semantic grouping is the principle that should decide adjacency.