Four Organizational Structures
Hierarchy, matrix, linear, and organic—different content suits different organizations.
The relationships within the content decide the structure. First see clearly whether your content is tree-like, table-like, chain-like, or web-like, then decide how to organize the interface. This step belongs to information architecture: get the structure right and users can answer "where am I, where can I go, how do I get back." ia-wiki
What you'll run into:
- No matter how you divide the categories, something doesn't fit—or fits into two of them
- To find something, users have to guess which category you filed it under
- The hierarchy keeps getting deeper, and by level four nobody visits anymore
How to choose
| Structure | Use it when | The cost |
|---|---|---|
| Hierarchy | Content has natural parent-child relations; one thing belongs to one category | Painful when category boundaries blur; users have to guess your classification |
| Matrix | One thing has several attributes, and users find it from different angles | Needs solid filtering and sorting, or you're passing the hard problem to users |
| Linear | Steps have a strict order; the next step is meaningless before the previous one | Must allow going back and saving, or users who break off lose everything |
| Organic | Associations matter more than belonging; exploration itself is the value | New users get lost; you need a landing page or recommendations |
Matrix and hierarchy are the easiest to confuse. The test: can one item belong to two categories at once? If yes, it's a matrix, and forcing it into a hierarchy leaves things perpetually unplaceable. Categories full of "Miscellaneous" and "Other," or the same item filed under two categories that drift out of sync—both symptoms say the same thing: this content was a matrix, forced into a hierarchy.
Once the structure is settled, draw it as a site map: one page per category, one line per entry point. If you can't draw it, the structure probably isn't thought through—a clear structure is always drawable. The map is also what you hand developers to align the navigation.
They're usually mixed
Real products rarely use just one. A common combination: an overall hierarchy, matrices inside one level, and a linear path for critical tasks.
Three structures in one e-commerce product:
- Hierarchy: home → category → subcategory, users browse by classification
- Matrix: within a subcategory, cross-filter by price, brand, and rating
- Linear: the checkout flow—address → payment → complete, no skipping
- Organic: the "people also viewed" section at the bottom of a detail page, reached through associations
Mixing is fine, but don't suggest two structures in the same screen. A category tree plus a tag cloud makes users unsure which logic to search by.
What getting it wrong looks like
- Used hierarchy where matrix was needed. Symptoms: "Miscellaneous" or "Other" categories appear, or one item sits in multiple categories that don't stay in sync.
- Used organic where hierarchy was needed. Symptoms: new users don't know where to start and rely on search alone.
- Made it free-form where linear was needed. Symptoms: users jump around, then discover at submit time that required fields earlier were skipped.
- Forced categories onto organic content. Symptoms: the content is obviously related, but the interface shows none of it, and users navigate from memory.
A simple way to check whether the structure is right: ask a new user to name something they'd look for, then watch how many steps it takes and whether they hesitate. More than one hesitation usually means a structural problem, not an interaction one.