§ 04 / Field note · 2026-03-11

Maps over lists

A pattern that has shown up independently in two of the lab's projects.

Two of the lab's projects independently arrived at the same move: throw out the ranked list and replace it with a spatial map.

Synapse does it most literally. The instrument's 13 questions don't return a top-five careers list. They place you on a map of 460 occupations (from BLS and O*NET), with adjacent careers sitting near each other. You don't "get a result." You get a neighborhood.

DartWorld does the same thing one layer deeper. Instead of letting students scroll through occupations on a screen, it lets them walk through them. The 3D environment is, structurally, a map. The lab's choice to make career exploration navigable (something you move through, not something you read) is the same design move Synapse makes, just rendered as space rather than diagram.

Why does this pattern keep showing up?

The ranked list has a specific failure mode: nobody reads past the first three results. The format itself teaches you that the top is the answer and the rest is noise. That works fine when there is an actual answer to find (groceries, flights, hotels). It works badly when the task is exploration, when not yet knowing what you want is the whole point.

A spatial layout breaks the first-result attention attractor. Everything is equally visible. The user has to wander to figure out what they're looking at. The wandering is the work.

What spatial layouts don't do: they don't tell you what to pick. That can feel like a bug if you are used to assessments that produce a recommendation. It is, in the lab's frame, the feature. The animating questions (especially RQ 1 and RQ 2) treat reflection as the developmental goal, not selection. A map fits that frame; a list works against it.

Open thread. The ethic may generalize beyond careers. A map of archetypes, or past projects, or values would each be worth building once. The harder question is the reverse: where do lists still do work a map can't? Triage problems, probably. Time-ordered decisions. Anywhere the user already knows what they're looking for. The lab hasn't drawn that boundary yet.

← All field notes