The sort.
Every information architecture begins the same way: a pile of labels tipped out of a spreadsheet. Page titles, services, department names, the nouns of an organization, and a person deciding what belongs under what. This is that decision as a table you can put your hands on. Pour the pile in, drag a card onto another card to file it underneath, and the structure draws itself as you work: as the tree you would build, as a ring that shows you its balance, and as an outline you can type in directly, because the text and the table are the same object. When the sort holds, take it with you.
Paste labels into the pile, one per line. Drag a card onto another card to file it underneath, or work in the outline: indent to go a level deeper. Both lists and the table are the same object, so either hand works. Nothing you type here leaves your browser.
What the sort says
- Shape
- 1 top-level section, 3 levels deep. Widest: Services (1 child).
- The pile
- 22 labels are still unfiled. A label in the pile is a decision not yet made, which is fine on a bench and fatal in a launch.
- Crowded
- No section holds more than seven children. Every menu here is scannable at a glance.
- Depth
- Nothing sits more than three levels down.
- Repeats
- No label is filed twice. Every card has one home.
Bench notes
- Why cards
- Card sorting is the oldest method in information architecture, and it survives because of something physical: when moving a thing costs one gesture, you try arrangements you would never bother typing. A spreadsheet makes every reorganization feel like work, so the first draft quietly becomes the final one. Here a card picks up, files, and unfiles in under a second, which means the structure you end with has actually been argued with. This is the open sort you run on yourself, before you spend research budget running one on users.
- One structure, three drawings
- The tree is the builder's view: columns and depth, the drawing a site map deliverable is made of. The ring is the editor's view: every section's true weight fans out from the center, so a lopsided architecture looks lopsided from across the room, which a tree is polite enough to hide. The outline is the writer's view, and the one other tools can eat. They are not three renderings of the data. They are the same cards, flying to new seats, which is the honest way to say the same structure three times.
- The text is the table
- Both panels on the left are live in both directions. Type a pile label into the outline and its card files itself; indent a line and the card walks a level deeper; delete a line and the card returns to the pile rather than being lost, because a typo should never destroy a decision. The pile panel is the one place delete lives. That symmetry is also the accessibility story: everything the pointer can do, the two text areas can do from a keyboard.
- The pile is the point
- Most tools hide the unfiled remainder because it looks like failure. It is the most useful number on the table. A label in the pile is a decision not yet made, and the readout says so as long as one is left. Dropping a group back on the pile dissolves it into loose cards again, which is what starting over on a section should cost: one gesture, not an afternoon.
- What it flags
- The same three smells the site map tool watches for, raised live while you sort. Sections holding more than seven children, because people stop reading a menu long before they stop scrolling it. Labels four or more levels down, which is where content goes to be forgotten. And the same label filed in more than one place, which means either one page filed twice or two teams naming different things the same way. None of it is a rule. All of it is a conversation worth having while the fix is still a drag.
- The manners
- Nothing you pour in is uploaded; the sort runs and stays in your browser, saved on this device so a closed tab does not cost the work, with undo for the drag you regret. Only the cards claim a touch, so scrolling past the table on a phone always works. With reduced motion on, the cards stop gliding and simply take their seats; every drag, both panels and both drawings still work. The exported SVG carries its own inks, so it stays correct in a deck or a printout.