Problem
Six people use this page and each of them wants a different panel at the top. Every request to reorder it is reasonable, and satisfying any one of them makes the page worse for the other five.
Solution
Let viewers arrange it themselves. Panels become cards that can be dragged, resized, added and removed, with the arrangement saved per person.
The appeal is obvious and the pattern is more often a mistake than not, so the honest version of this entry is mostly about when it goes wrong.
The first cost is that a personalised page cannot be talked about. “It’s the panel in the top right” stops meaning anything, which matters most during incidents, when a shared vocabulary is worth more than any individual’s preferred arrangement. A team looking at six different dashboards while calling it “the dashboard” is a real and specific failure.
The second is that most people never customise, so the default layout is still what almost everyone sees, and it now receives less design attention because customisation is the answer to any complaint about it. The feature quietly lowers the quality of the thing 90% of people use.
The third is that arrangements fossilise. Someone lays out a page in March, the system changes in June, and their saved layout still has the old panels in the old order with no prompt to reconsider. Nothing in the product knows their arrangement has stopped describing the system, so the staleness is invisible to everyone including them.
Where it genuinely fits is a page serving genuinely different jobs with no shared reading, and where the arrangement is the only difference. If the differences run deeper than layout—different metrics, different scope—separate dashboards or saved views serve better and keep each one designed.
Use when
The audience is genuinely heterogeneous, the panel set is stable, and no shared reading of the page is required.
Don’t use when
The page is used collaboratively, especially in incidents. Also don’t use it as a way to avoid deciding what the page is for; customisation is not a substitute for editorial judgement, and it is frequently deployed as one.
Trade-offs
Drag-and-drop layout is expensive to build well and worse than useless when built badly, since a page that reflows unexpectedly during a drag loses trust immediately. Layouts made on one screen size rarely work on another. Per-viewer state has to be stored, migrated and eventually deprecated. And an editable page invites accidental edits: dashboards get rearranged by people who meant to scroll, and the undo path is usually missing.
Checklist
- Does anyone need to talk about this page with someone else looking at it?
- What proportion of viewers actually customise, and how do you know?
- Is the default layout still receiving design attention?
- Does a customised layout survive a change to the panel set?
- Is a viewer prompted when their saved layout references something removed?
- Can a viewer reset to the default in one action?
- Does layout editing require an explicit edit mode, or can it happen by accident?
- Is there an undo?
- Does a layout made on a wide screen work on a laptop?
- Would saved views or separate dashboards serve these audiences better?
Compare
Grafana makes every dashboard editable by anyone with permission, so the arrangement is shared rather than personal and edits are changes to a common artefact, which trades personalisation for a shared vocabulary. Datadog offers both editable dashboards and personal starred views, keeping the shared page canonical while letting individuals collect what they need elsewhere. Kibana leans furthest into free arrangement of cards, each carrying its own query, which is flexible and puts all coherence on the author. Public status pages are the deliberate opposite, with no customisation at all, because a page read by strangers must look the same to everyone.
Related
Panel grid is the underlying layout system, and the entry that covers why a fixed grid encodes priority. Saved view is usually the better answer to the same need. Dashboard builder is the authoring pattern this is a subset of. Semantic grouping is the editorial work customisation is often used to avoid. Multi-page dashboard is the alternative when the audiences differ by more than arrangement.