Rolling back up to a coarser level deserves as clear a path as drilling down into detail does
Aliases: roll-up · drill up · ascending aggregation
What it is
Roll-up is drill-down's inverse: ascending the hierarchy into coarser aggregation — days back to months, stores back to regions. It is not an alias for the "back" button but a genuine aggregation operation; the two get conflated in interfaces all the same, with roll-up entrances either missing (browser back as the only way out) or semantically muddled (does "back" undo the level or the filters?). Roll-up's entry deserves the same explicitness and predictability as drill-down's.
Why it happens
The roll-up entrance goes missing because implementations often reduce "aggregate upward" to "undo the drill" — yet once the user has touched filters or switched views mid-descent, undo and roll-up part ways: undo returns to the previous state, roll-up keeps every other state and changes only the level. The distinction is critical in deep analysis: three drills, two filters, one chart type later, the user wants to ascend one level — undo on the history chain would drag the filters back too. Explicit roll-up preserves analytical state and touches only the level; that is the correct primitive in the grammar of analysis. Roll-up must also travel the same hierarchy path it descended — drill along one path, roll up along that same path, so the "retrace your steps" expectation holds.
Where it stops holding
Roll-up is not a clear-out: one level up still sits mid-hierarchy, and the interface must allow further rolling up to the top. Mixed-path returns (drill by time, roll up by region) produce results no user can predict — forbid them or warn explicitly. Breadcrumbs are roll-up's best vehicle — every level clickable, a click rolls up to it; the path is the control. Roll-up and "clear everything" must also stay apart: the former moves the level, the latter resets the analysis, and conflating them destroys the user's exploration state.
Applying it
- Show hierarchy breadcrumbs persistently, every level clickable, each click rolling up to that level.
- Keep roll-up's hands off filters and view settings — level only — and keep it strictly separate from "clear filters" and "reset view."
- Verification: have users drill three levels, add a filter, then roll up two; the filter must survive and the level must be right — a lost filter means the roll-up implementation absorbed undo semantics.
Related
- Same group: U6.05.1 Drill-down descends a predefined hierarchy from summary to detail · U6.05.3 The current level position must stay visible · U6.05.4 With multiple drillable dimensions, let users choose which to expand · U6.05.5 Existing filters must be inherited and stay visible through drill-down
- Nearby: U6.04.3 Zooming must keep an exit back to the global view · U6.11.1 The analysis process must be undoable and replayable
- Search terms:
roll-up·drill up·breadcrumb hierarchy
Cards in the same group
- U6.05.1Drill-down only descends a hierarchy that was already defined, from year to quarter to month, say
- U6.05.3Without a visible breadcrumb, two drills deep just looks like a pile of numbers with no context
- U6.05.4When sales data can drill by time, region, or product, the user needs to choose which axis to follow
- U6.05.5A filter applied before drilling down should still apply, and still be visible, at every level below