# Air for Wandering, Density for Doing Should menus be concise? The honest answer is that concision is not the variable, mode is. A page has one of two jobs: it hosts wandering or it hosts doing, and white space is the signal that tells the reader which room they are standing in. Generous air around prose says slow down, there is nothing to chase here; psychology backs the intuition, since visual breathing room lowers cognitive load and leaves the mind space to free-associate. The same air on a configuration surface is a small betrayal. Somebody arrived with intent, and every centimeter of decorative emptiness is another centimeter of scroll between them and the checkbox they came for. The canon has names for the doing side. Hick's law prices every added option in decision time, which argues for concise menus. Information foraging argues the opposite way: people follow scent, and a label they can see beats a submenu they must guess into, which is why broad and shallow beats narrow and deep in most findability testing. The resolution is that concision applies to choices, not to visibility. Show few decisions at a time, hide none of the map. My [[UX - Progressive Disclosure and the All-Purpose Prompt|progressive disclosure]] piece is the same argument wearing an AI costume, and [[UX - Controls Near the Consequence|controls near the consequence]] is its spatial twin. The purest version in my own build log is [[The Product Diary#2026-02-09: Zero-Tap Definitions|Vibe Reader's zero-tap definitions]]: the best doing-surface turned out to be one interaction, then none, with friction kept only where a misheard quote makes verification worth its tap. Scrolling is where the two modes collide hardest. Readers scroll happily; the fold has been a myth for years. Configurers do not. And the [[08.11.26 - The Anti-Feed - Apps Without the Scroll|anti-feed thesis]] names the third scroll, the engineered one, where air and endlessness conspire to keep you wandering long past intent. A settings page longer than a viewport without a way to refine is a maze with no map, and users leak out of it. The modern escape hatches are all the same move in different clothes: the settings search box, the command palette, filter-as-you-type. Every one of them converts a geography problem into a naming problem, which is a trade users win. The principle I would carve over the door: any surface longer than a screen owes its user a way to skip the geography. I have been living this split all week without naming it. The reading side of this site just got its air budgeted down deliberately, tighter rhythm, dividers reduced to three quiet dots, because prose here is for wandering but not for wading. And the one configuration surface the site ever had, the field's tuning dials, got removed entirely rather than made scrollable. The doing moved into the workshop; the wandering kept the meadow. **Takeaways:** * **White space is a mode signal.** Air invites roaming; density invites action. Match the budget to the job, and never let one page claim both. * **Concise decisions, visible maps.** Hick governs how much you ask at once; scent governs how much you show. They are different budgets. * **Scroll is for reading, search is for finding.** Past one viewport, a doing-surface owes the user an escape hatch from geography.