Most systems keep hierarchy as the backbone and add hypertext laterals

What it is

Most products are neither a pure tree nor a pure graph. They are a hierarchy backbone plus hypertext laterals: classification and nav answer “which class am I in,” and on-page related links answer “tied to this, but not on this branch.” The backbone keeps predictable up-and-down and a sense of place; laterals cover cross-branch tasks the tree cannot express. Stacking both in one system does not mean the tree can be removed, or that laterals may casually become the main entrance.

“Related articles,” “accessories,” and “see also” belong to this supplement. Promoting them to first-layer global navigation is the supplement usurping a second backbone.

Why it happens

Trees answer belonging and not crossing. After someone finds an object in the tree, the next question is often already relational. If the only offers are “up / sibling,” a cross-branch task must climb out and down again. A few high-scent laterals on the node borrow hypertext’s one hop without giving up path memory.

The hybrid works only if people can tell which link set is backbone and which is supplement. Mixed visually and spatially, laterals are read as new children and the belonging model is polluted; or the backbone is treated as skippable chrome and place collapses to the current page title. The supplement must be skippable; the backbone must be walkable on its own.

Studying it

Make “backbone only” and “backbone plus laterals” separable conditions, and split tasks into belonging versus cross-branch.

• Paradigms: two task classes (find an object under a class vs go from a found object to a cross-class relative); conditions pure tree, pure graph, tree plus laterals. Record whether cross-branch tasks stop returning to the root, and whether laterals disturb place on belonging tasks.
• Independent variables: number of laterals, whether anchor text names the relation, whether laterals are spatially separate from local nav.
• Dependent variables: cross-branch steps, rate of mistaking a lateral for a child class, ability to sketch “which branch I am on.”
• Methodological note: measuring only cross-branch tasks yields “more links win”; measuring only belonging yields “laterals are noise.” The hybrid’s value is the sum of both task classes, not a champion of one.

Where it stops holding

Casual laterals on a strongly sequential flow pull people out of steps whose preconditions are unmet; the hybrid becomes a hole. When a matrix already handles crossing on a second axis, extra laterals duplicate without coordinates. On a tiny collection, backbone plus laterals makes every page look equally “related,” and the supplement loses distinctiveness. Experts who search straight to a node barely walk the backbone, so lateral quality becomes the main structure—yet the node must still answer “which branch am I on,” not only recommend.

Applying it

• First make the tree complete belonging lookup on its own, then add a few laterals on leaves or key nodes, with the relation named.
• Separate local nav from “related” in space: one side this branch, the other side cross-branch. Do not render them as one set of equal links.
• If a lateral target also lives in the tree, still show branch position on arrival, so people do not think they were sent into another site.
• Verify: belonging tasks still complete with laterals off; cross-branch tasks with laterals off must return to the root. If belonging fails with laterals off, the backbone is not standing. If cross-branch still requires the root, the laterals have not yet supplemented.

Related

• Within the group: G1.09.1 Hierarchy organizes content by parent–child links and is the usual default · 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.6 Structure type and organization scheme are independent dimensions · G1.09.7 A matrix demands complete metadata; missing fields block location
• Adjacent: G2.03 Network and associative navigation · G2.01 Hierarchical navigation · G2.06 Global and local navigation
• Search terms: hierarchy plus hypertext · lateral links · hybrid information architecture