Anatomy
┌──────────────────────────────────────────────────────────────┐
│ All ● My overdue Dana's chase list* Team: unassigned + │
│ ↑ shared ↑ edited │
├──────────────────────────────────────────────────────────────┤
│ Status ▾ Owner ▾ ● Overdue ✕ ● Owner: Dana ✕ │
└──────────────────────────────────────────────────────────────┘
Three properties do the work:
- It captures the whole view, not only the filters — sort and columns too. A view that restores the rows but not the ordering has not restored the view.
- The filter bar stays visible and live. A saved view is a starting point, not a lock. Editing from a view is the most common thing people do.
- Personal and shared are distinguishable. They are different objects socially: one is a shortcut, the other is an agreement.
Why it works
It converts a repeated act of memory into a click, which is the highest-value friction removal available on a list — because it is paid every single day by the same people.
The team effect is the larger one, and it is easy to miss. A shared view named "Needs chasing" is a definition. Before it exists, six people have six private definitions and their numbers never quite agree; afterwards there is one list, and disagreements about it become explicit rather than invisible.
That is also why editing a shared view deserves a warning. Quietly changing what a name means is more disruptive than deleting it, because everyone keeps using the name and the meaning has moved.
Getting it wrong
- Saving only filters. The sort was part of what made it useful.
- No unsaved-changes state. People edit a view, expect it to stick, and lose the change — or worse, expect it not to stick and overwrite a shared one.
- No pruning. Twenty stale views is a worse menu than none, and nobody deletes other people's.
- Views instead of good defaults. If everyone's first act is to switch away from the default view, fix the default.
- Building views before filters work. The layer underneath has to be solid, or every view inherits the same gaps.
Exemplars
Linear's views show the personal-versus-shared distinction handled explicitly, and the "unsaved changes" state done well: you can always tell whether you are looking at the view or at your own edit of it.
Airtable's saved views go furthest — each view carries its own fields, sort, grouping and even type of display — and demonstrate the cost too: a base with forty views needs someone to curate them.
Gmail's search-backed labels are the same idea with a different surface, and make the point that a saved view is really a named query.
The extractable rule: a shared saved view is a definition, not a shortcut. Treat renaming and editing it as a change to a shared agreement, because that is what people will experience.