Hierarchy organizes content by parent–child links and is the usual default

What it is

A hierarchical structure hangs content from parent–child links: each object has one (or a few) parents, and children appear only after the parent is opened. Sites, file cabinets, and settings screens default to this tree. It is common not because it is always the most accurate, but because people already know “pick a class, then go down,” and it is cheap to implement and explain. Hierarchy answers “who does it belong to.” It does not answer “what else is it like” or “what must come next.”

Default is not the only legal type. Hierarchy is chosen when belonging is the strong relation, not because other structure types do not exist.

Why it happens

A parent chain recursively cuts the collection into non-overlapping pockets. Working memory handles a handful of names at one layer. Place can be remembered as a root-to-leaf path, and “up one level” has a clear meaning. The cost is that every object must first be assigned a parent: a wrong assignment poisons scent on the whole path; an object that belongs to two parents forces the tree to pick one, or quietly becomes polyhierarchical while still being explained as a single tree.

Hierarchy also implies top-down access. Someone who does not know the parent’s name cannot start, even if they already know the leaf. That is the blind spot of hierarchy as a default: it is kind to “known parent,” unkind to “known leaf, unknown belonging.”

Studying it

Test hierarchy as a structure type, not as “whether there is navigation.”

• Paradigms: tree tests (parent and child names only) versus the same known-item tasks on a matrix or a pure-link structure; plus tasks that give only the leaf, not the parent, to see whether the hierarchy cannot even start.
• Independent variables: depth, width per layer, whether multiple parents are allowed, whether the path is visible.
• Dependent variables: direct success, rate of walking an entire wrong-parent branch, rate of switching to search when the parent is unknown.
• Methodological note: staff remember the official tree and overestimate hierarchy’s default advantage. New users are the sample for whether “usual default” holds. If multiple parents are allowed in the test, it is no longer a pure hierarchy; analyse that cell separately.

Where it stops holding

When permission, law, or physical location really is containment (folders, regions, org charts), hierarchy is close to irreplaceable. When content is mainly a task flow or associative reading, forcing a tree disguises “what’s next” as “child class.” When objects naturally have several belongings (a piece that is both news and a product story), a single-parent hierarchy systematically misleads: switch to a matrix, or keep the tree and add lateral links, rather than deepening the default tree.

Applying it

• Use hierarchy as the backbone only when “belongs to whom” is the user’s main clue, and write the parent–child rule for each layer.
• Leave search or a cross-entrance for people who do not know the parent. Do not assume everyone starts at the root.
• When an object needs two parents, treat it as polyhierarchy or change structure type. Do not quietly duplicate it inside a single tree.
• Verify with half the tasks giving only parent clues and half giving only leaf clues. Mass failure on the latter means hierarchy was treated as the only path, not a true default backbone.

Related

• Within the group: G1.09.2 A matrix locates the same content by several attributes at once · G1.09.3 Hypertext organizes by associative links, not a single hierarchy · G1.09.4 Sequential structure forces a fixed order, as in tutorials and wizards · G1.09.5 Most systems keep hierarchy as the backbone and add hypertext laterals · G1.09.6 Structure type and organization scheme are independent dimensions · G1.09.7 A matrix demands complete metadata; missing fields block location
• Adjacent: G1.03 Taxonomy and hierarchy · G2.01 Hierarchical navigation · G1.02 Organization systems
• Search terms: hierarchical structure · parent-child taxonomy · tree navigation