Structure type and organization scheme are independent dimensions

What it is

Structure type is how objects connect: tree, matrix, hypertext, sequence. Organization scheme is what attribute the cut uses: letter, time, topic, task, audience. The two are orthogonal and freely combinable. A topic tree, a chronological sequence, an audience matrix, a task wizard are different cells, not four mutually exclusive “architectures.” Treating “we’ll do hierarchy” as if the scheme were already chosen, or “we’ll organize by task” as if the structure type were already chosen, skips a decision.

Combination is a design choice, not an automatic event. The same collection can be topic × tree or task × sequence. Write the two decisions separately.

Why it happens

Connection style decides how one walks (up a level, a cell, an associative edge, next). The cutting attribute decides which labels one sees while walking. A tree is not born topical; a tree ordered by time is still a tree. A sequence is not born task-based; a slideshow forced by time is still sequential. When the two are fused, changing labels is taken as changing structure, and changing structure is taken as swapping content types. Disputes miss the layer: one party is arguing about whether “up” should exist, the other about whether the word should be “Finance,” and both think it is the same argument.

Independence means an experiment can move one dimension. Changing a topic tree into a task tree leaves structure type hierarchical; changing a topic tree into a topic matrix leaves the scheme topical. What can be changed separately can be attributed separately.

Studying it

Use a two-factor design to show the dimensions split; do not bind them with a single case story.

• Paradigms: on one collection, cross structure type × scheme: topic tree vs task tree vs topic matrix vs task wizard. Scripts supply “known topic,” “known task,” or “known place in a sequence.”
• Independent variables: structure type and organization scheme, crossed.
• Dependent variables: success when the clue matches the scheme, translation cost when they mismatch, whether people can afterwards describe “how one walks” and “what the cut is on” separately.
• Methodological note: live products almost always occupy one cell, so observational studies treat the dimensions as born bound. Deliberately change one and hold the other. Card sorts mainly move scheme; tree tests mainly move walkability of structure. Do not let one method conclude for both dimensions.

Where it stops holding

Some domains look welded (a statutory catalogue that is both hierarchical and officially topical): an external authority specified both dimensions, which is not a logical inability to split them. Personalized recommendation is neither structure type nor scheme; it is a third axis (who sees it) and must not be stuffed into this two-way table to pad combinations. A small product may occupy only one cell and should still name the cell, so successors do not hear “we are hierarchical” as “we can only cut by department.”

Applying it

• Write the architecture as a table: rows are structure types, columns are schemes, which cell the current system occupies, which cells are alternatives.
• When revising a nav sketch, declare whether this pass changes connection style or cutting attribute. One meeting, one dimension.
• Different tasks may occupy different cells (settings as tree × function, onboarding as sequence × task), but each entrance represents one cell. Do not mix cells in one menu.
• Verify by stripping visuals and leaving only a walk diagram and a label table of the cut. Someone uninvolved should retell them separately. If they fuse the two into one story, the dimensions have not yet been designed as independent.

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.5 Most systems keep hierarchy as the backbone and add hypertext laterals · G1.09.7 A matrix demands complete metadata; missing fields block location
• Adjacent: G1.02 Organization systems · G1.03 Taxonomy and hierarchy · G2.01 Hierarchical navigation
• Search terms: structure type · organization scheme · information architecture dimensions