Skip to content

Desire Path

Version
v2 · 2026-08-30 · History
Prime #
793
Origin domain
Architecture & Urban Planning
Subdomain
revealed preference route → Architecture & Urban Planning

Core Idea

A desire path is the involuntary, cumulative trace that users wear into a substrate when they follow routes the designer did not provide — a readable record of what the design fails to accommodate. It shows revealed behaviour under real friction, posing an inverse problem (recover the unmet need) and a dual remedy: pave the benign, reshape the adversarial.

How would you explain it like I'm…

The Dirt Shortcut

Sometimes there's a sidewalk, but everybody cuts across the grass to get somewhere faster, and the grass wears down into a little dirt trail. Nobody planned that trail — people's feet made it by going where they really wanted to go. That worn trail is a secret message saying 'the sidewalk should have gone HERE.'

Trails Made by Feet

A Desire Path is what happens when the people using something keep going a way the designer never built, and the route they wear in becomes a record of what the design failed to give them. A dirt shortcut across a park is the classic example: thousands of people each made a tiny choice, and together their feet wrote down where the real path should be. It's more honest than asking people what they want, because it shows what they actually do when they're in a hurry. A trail only counts if it lasts — a one-time shortcut is just noise, but a path worn deep carries real information.

Reading the Worn Route

A Desire Path is the pattern where users of a designed system follow routes the designer didn't provide, and the unofficial routes they wear in become a readable record of what the design fails to accommodate. The trace is involuntary, cumulative, and inscribed by the users themselves, which gives it a different status than a survey — it shows revealed behavior under real friction, not reported behavior under reflection. The substrate (dirt, server logs, recurring support tickets) has already aggregated thousands of micro-decisions for free, so reading the trace is cheaper and more honest than asking people directly. Durability is the test that separates a genuine path from one-off noise: only persistent traces carry information. At root it's an inverse problem — given a substrate that records use and a gap between intended and enacted routes, recover what the design failed to support — and the fix is dual: pave the path where it's durable and harmless, or reshape incentives so a harmful path stops forming.

 

A Desire Path is the structural pattern in which the users of a designed system follow routes the designer did not provide, and the unofficial routes they wear in become a readable record of what the designed system fails to accommodate. The trace is involuntary, cumulative, and physically or digitally inscribed by the users themselves, giving it a different epistemic status from surveys or intended-use models: it reveals behavior under real friction rather than reported behavior under reflection. The substrate has already integrated thousands of micro-decisions across heterogeneous users into a small set of high-traffic deviations, so reading that integrated trace is cheaper and more honest than direct elicitation. Several commitments define the pattern: a designed routing or affordance from a prescriber; many independent users with their own goals and frictions; a substrate that inscribes traversal cumulatively (dirt that wears, logs that accumulate, tickets that recur); a divergence between prescribed and inscribed routes; an inscription cheaper to read than direct elicitation because the substrate aggregates for free; and durability as the criterion that separates a genuine path from one-off noise. At root it is an inverse problem — given a substrate that records use and a divergence between intended and enacted routes, recover what the design failed to support — and the reciprocal intervention is dual: where the path is durable and not harmful, redesign to follow it (pave the path); where it is adversarial, reshape incentives so the path stops forming.

Broad Use

  • Architecture and urban planning: the dirt track cutting the corner across a lawn, the worn campus diagonal, the cow paths of older cities.
  • Software UX: keyboard-shortcut adoption, deep-link bookmarking past navigation, screenshots used for sharing, recurring support tickets.
  • Organisational workflow: the back-channel that routes around the approval chain, the shadow spreadsheet living outside the system of record.
  • Public policy: the workaround, the informal economy, read as evidence of where the policy mismatches lived constraint.
  • Knowledge work: the pages people actually link, search queries that bottom out in zero results, bookmark folders used in lieu of the taxonomy.
  • Ecology: game trails — durable marks worn by repeated low-friction passage, where there is no "desire" at all, only revealed traversal.

Clarity

Distinguishes the designed affordance from the enacted one, reframing a workaround from "users doing it wrong" (disapproval) to "the design is failing to accommodate something" (curiosity), with durability separating signal from noise.

Manages Complexity

Converts an intractable problem (model every user) into a tractable one (read the aggregate trail) — a few prominent paths against diffuse noise.

Abstract Reasoning

Of any designed system ask: what is its substrate, what does it inscribe, and where are the deviations? — treating the substrate as a sensor and a durable trace as a measurement of unmet need.

Knowledge Transfer

  • Software UX: the export-edit-reimport cycle is a worn diagonal — a feature brief, not a misuse.
  • Organisational design: the shadow spreadsheet is a desire path around the formal process.
  • Ecology: a wildlife-corridor planner reads a game trail exactly as a UX researcher reads a telemetry cluster.

Example

A worn diagonal cuts the hypotenuse across a grassy quad: each pedestrian under friction cuts the corner, and the grass integrates thousands of footfalls for free into a single legible trace — read as a sensor of unmet need and paved rather than fought.

Relationships to Other Abstractions

Local relationship map for Desire PathParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Desire PathPRIMEPrime abstraction: Revealed Preference — is a decomposition ofRevealedPreferencePRIME

Current abstraction Desire Path Prime

Parents (1) — more general patterns this builds on

  • Desire Path is a decomposition of Revealed Preference Prime

    Removing the route-design frame leaves inference of latent preference from a durable trace of costly observed choices rather than stated reports.

Hierarchy path (1) — routes to 1 parentless root

Not to Be Confused With

  • Desire Path is not Path Dependence because a desire path is an epistemic trace of revealed behaviour to read, whereas path dependence is a causal constraint by which past choices foreclose future options.
  • Desire Path is not a Decision because a desire path is the cumulative, substrate-integrated trace of thousands of micro-choices, whereas a decision is a single deliberated choice by one agent.
  • Desire Path is not Habitus because a desire path is the external substrate trace behaviour leaves (in the dirt or the logs), whereas habitus is an internalised disposition in the agent.