Nudgeminder

Every map distorts the territory it represents — not by accident, but necessarily. The cartographer's projection that makes navigation easy in one region creates grotesque distortions somewhere else. Alfred Korzybski built his entire philosophy of language around this observation: the map is not the territory, and the more useful a map becomes, the more invisibly it shapes what its users think is possible to reach. Product roadmaps work exactly this way. The moment a roadmap becomes the shared mental model of a team, it stops being a tool for navigating toward an outcome and starts functioning as the outcome itself. Features that fall off the roadmap don't get killed — they quietly become unthinkable. The danger isn't that teams execute their roadmaps poorly. It's that they execute them too well, never noticing which questions can no longer be asked from inside the map's coordinate system. Korzybski's remedy was to periodically return to first-order observations — raw contact with actual phenomena before they've been categorized. For a product team, that means deliberately setting the roadmap aside and asking what the product's users are actually doing, not what the roadmap predicts they should need. The map can resume its authority afterward. But it needs to earn it again each time.

When did your team last make a consequential decision that the roadmap didn't already predict — and what had to happen to make that space available?

Drawing from General Semantics — Alfred Korzybski (Science and Sanity, 1933)

This nugget was crafted for someone else's interests.

Imagine one written just for you, waiting in your inbox every morning.

Get your own daily nudge — free

No account needed. One email a day. Unsubscribe anytime.

Crafted by Nudgeminder