Desire Path Principle

On many green spaces between apartment blocks, you can see two kinds of paths. One is paved and was drawn by a planner. The other is a brown strip in the grass that people have worn down with their feet. This second path is usually shorter and leads exactly where people actually want to go. The desire path principle transfers this observation to the design of products, software, and rules: one should observe how people actually use something instead of insisting on how they should use it. In English, this worn path is called a “desire path.”

What the worn-down lawn reveals about users

People often say something different in surveys than what they later do. Asked whether they take the official path, they gladly answer yes. The worn-down grass contradicts this answer without any discussion. This is exactly where the value of the principle lies: behavior lies less often than opinion.

For companies, this is concrete and not just a nice observation. When customers permanently repurpose a feature, an unmet need is hidden within it. Whoever recognizes it can turn it into a product. Whoever ignores it will eventually lose users to a provider who pays closer attention.

A well-known example from tech history is the hashtag. Twitter never planned it; users invented it themselves to sort topics. Only afterward did the company officially build it in. The desire path came first, the paving came later.

From observed behavior to the paved path

In practice, the principle unfolds in three steps. First, one observes what people do instead of just asking them. Then one looks for patterns that repeat and are not limited to isolated cases. Finally, one restructures the system so that the convenient path is also the intended one.

With software, usage data provides this observation. One might see, for instance, that many people use a search function because they don’t understand the menu. Or that a spreadsheet column is constantly misused for notes for which there is no dedicated field. Such traces are the digital equivalent of the trampled lawn.

A common mistake is to pave over every desire path immediately. Some shortcuts are dangerous, unfair, or merely the quirk of a small group. If people click away a security window, that is a desire path, but not a good one. The right response then is not to pave it, but to ask why the official path is so unbearably cumbersome.

Desire paths in apps, chatbots, and company figures

The principle is especially visible right now with AI chatbots. These programs were built as tools for writing and research. But many people use them as translators, as therapy conversations, or as advisors for everyday decisions. Providers react to this and subsequently build out exactly these applications.

In business news, the idea often appears without the term itself. When a company reports that a side product has suddenly become its top revenue driver, there is almost always a desire path behind it. Customers used an offering differently than intended, and the company followed them. Such course changes are called a “pivot” in startup language, meaning a shift in the direction of the business model.

The principle can also easily be checked in one’s own everyday life. Notes on the phone instead of in the notes app, chats with oneself as a clipboard, screenshots instead of bookmarks. Each of these habits shows a gap between plan and reality. Whoever notices such gaps understands the product decisions of major tech companies considerably better.