The path nobody planned for

The path nobody planned for

The path nobody planned for

There’s a story, often told about various university campuses, that when a new campus was built, the planners deliberately resisted paving any paths - instead, they waited to see where students and faculty naturally walked, allowing desire lines to emerge across the grass before laying the permanent routes.

I have no idea whether the story is true. Versions of it seem to be attached to different universities depending on who is telling it, but I’ve always liked it because it captures an unusually humble approach to design - rather than assuming they knew how people would move through the space, the planners accepted the possibility that they might not. They observed first and designed second.

Whether or not the story happened exactly as described is almost beside the point. The reason it endures is that it contains a simple truth: users often reveal things that designers cannot predict. That lesson extends far beyond footpaths.

The bin nobody used

Years ago, I came across another story that has stuck with me for similar reasons.

An office bathroom had developed a persistent problem - after drying their hands, employees would often drop their paper towels on the floor near the door rather than placing them in the bin provided.

Management responded in the way organisations often do - They put up a sign asking people, politely, to use the bin. When that didn’t work, they added more signs. Then larger signs. Then increasingly stern reminders about cleanliness and consideration for others. None of it made any difference. The paper towels continued to accumulate by the door.

The problem was eventually solved by moving the bin next to the door.

The issue was never that employees didn’t understand the rules. The issue was that the system had been designed around how people were expected to behave, rather than how they actually behaved.

It’s a funny story because the solution seems so obvious in hindsight. But it’s also a surprisingly common mistake - when reality disagrees with our design, our instinct is often to try to change reality.

We write more instructions, we create more rules, we add more training, we explain more clearly. Sometimes that’s necessary, but often it isn’t. Sometimes the simplest solution is to accept what people are already telling us and adapt the design accordingly.

The interfaces nobody expected

This happens constantly in creative work: a designer spends weeks crafting a beautifully considered interface, only to discover that users are clicking the wrong thing; a communications team carefully refines a message, only to find that audiences interpret it differently than intended; a business launches a feature that customers use for something entirely different than its original purpose.

The temptation is always to conclude that the users are doing it wrong, but at a certain point, it becomes worth asking a different question - what if they’re showing us something?

Every desire line is evidence of a gap between how something was designed to be used and how people actually want to use it. The worn path through the grass is feedback. The pile of paper towels by the door is feedback. The button nobody clicks is feedback. The feature people use in unexpected ways is feedback. In fact, some of the most valuable feedback we ever receive isn’t feedback that people consciously give us at all, it’s simply behaviour.

Many organisations spend enormous amounts of time collecting opinions - surveys, workshops, interviews, questionnaires, all of which can be incredibly valuable. But sometimes the most honest feedback available is what people actually do when nobody is watching.

The value of being wrong

This is one of the reasons I think observation remains such an important skill in design and communication.

Expertise is often framed as the ability to predict outcomes, but in practice, even the most experienced professionals cannot perfectly predict human behaviour. A landscape architect cannot know exactly where every path should go, a UX designer cannot anticipate every workflow, a communicator cannot predict every interpretation. The value of expertise is not perfect foresight, it’s recognising useful signals when reality starts diverging from the plan.

Perhaps that’s why desire lines continue to resonate for me - they remind us that design is not a finished artefact. It’s an ongoing conversation between intention and reality. Every design is a prediction about human behavior - and sometimes the real work begins when we discover whether that prediction was correct.

The path through the grass isn’t a failure, it’s information - evidence that somebody found a better route. And sometimes the smartest thing a designer can do is stop trying to guide people back onto the path they intended, and start paying attention to the one people have already chosen.