Drill-down only descends a hierarchy that was already defined, from year to quarter to month, say

What it is

Drill-down is descending one level along a data-native hierarchy: year → quarter → month → day, region → province → city → store, category → subcategory → SKU. The keyword is "predefined" — drill-down follows a hierarchy path fixed at modelling time, where every step has a definite answer to "what is the next level." It differs from casual "click to see details": drill-down changes the aggregation granularity; it does not pop up one record.

Why it happens

The analytical value of drill-down is that aggregation stays complete: from "nationwide, 2025" drilled to "by province, 2025," the total is unchanged and the dimension finer — every step still reconciles, which is exactly what separates it from filtering (filtering changes the total). The predefined hierarchy guarantees predictability: users know clicking "East" reveals Jiangsu, Zhejiang, and Shanghai, not some other partition; predictable paths give navigation its sense of direction. The hierarchy also defines the drill's endpoint — the detail level cannot be drilled further, and the interface should honestly stop there rather than offer "drill again" that returns the same data.

Where it stops holding

Drill-down depends on hierarchy modelling quality: missing levels (year jumping straight to day), broken chains (no city data under a region), or ambiguous dimensions (expandable by both time and region) shatter the experience. Multi-hierarchy dimensions (drillable by time or by region) need a dimension-selection mechanism (the fourth card in this group). Granularity span matters too — a drill that jumps three levels at once strips out intermediate reference points; good implementations keep every intermediate level visible. Data permissions also cut drill paths: some lower branches are unviewable for a given user, and the interface must handle those unreachable branches explicitly.

Applying it

• At modelling time, draw the complete hierarchy tree for every drillable dimension; fill missing levels and broken links in the model — never leave them for the interaction layer to paper over.
• Give drillable marks an affordance (cursor, plus sign, chevron) and keep the drill action uniform product-wide.
• Verification: have users drill from summary to a target detail level; every step should be predictable — any element where "clicking and not knowing what happens" occurs is a missing affordance.

Related

• Same group: U6.05.2 Roll-up needs a return path as explicit as drill-down · 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.2 Semantic zoom changes the content level being presented · U6.01.3 Details surface on demand, not by default
• Search terms: drill down · hierarchy navigation · OLAP analysis