Soft Mirror

The Invisible Systems Behind Everyday Life

A crowd crossing a street looks spontaneous. It is held together by signals, markings, timing and habit, most of which nobody notices until they fail.

By Soft Mirror6 min read

Aerial view of a busy urban crossing in low sun: crowds on white crosswalk stripes, long shadows, and a translucent window reflection across the street.
A crossing at low sun. The reflection in the glass belongs to the photograph; the order on the street does not.

Look down at a large pedestrian crossing from above and the first impression is of chaos: hundreds of people, each with somewhere to be, moving in every direction at once. The second impression, which takes a little longer, is that almost nobody collides. People slow, angle and slip through gaps without breaking stride. The street works.

None of this is spontaneous. A signal sets the moment everyone steps off the kerb. Paint tells you where the crossing is and, loosely, where to walk. A kerb ramp, the width of the road, the length of the green phase and the habits of the people around you each take a decision off your hands. You are not coordinating with a thousand strangers. You are following a system that has already done most of the coordinating, and you hardly notice it.

Systems that work are quiet

The researcher Susan Leigh Star made the point about infrastructure in general: it tends to be invisible in use, and becomes visible when it breaks. Nobody thinks about the water main until the tap runs dry. Mark Weiser put the same observation into a sentence that technologists still quote, that the most profound technologies are those that disappear, weaving themselves into the fabric of everyday life until they are indistinguishable from it.

The most profound technologies are those that disappear.

Mark Weiser, “The Computer for the 21st Century”, Scientific American, 1991

It is easy to hear that as a goal, and it is one. But it also carries a warning. A system that disappears is a system people stop questioning. If it works well, we never learn what it assumes about us: who is expected to walk fastest, who is expected to see the signal, who is expected to have a phone, an account, a card.

Order that people make as well as receive

Jane Jacobs, writing about city streets in 1961, argued that a lot of what keeps a sidewalk safe and pleasant is not planned at all. It is the accumulated attention of ordinary people going about their day: the shopkeeper who glances up, the neighbour on the stoop. Her phrase for it was “eyes on the street”. The crossing in the photograph has the same double character. The signal and the paint are designed. The way a crowd bends around a person who stops to tie a shoe is not.

Good systems leave room for that second kind of order. They set the conditions and let people do the rest. Systems that try to specify every movement tend to produce workarounds, the worn path across the grass beside the paved one.

What this means for people who build software

Software sits in the same position as the crossing. At its best, the person using it is thinking about the thing they came to do, not the machinery between them and it. Don Norman made this argument about physical objects in The Design of Everyday Things: when a door has to be labelled “push”, the design has failed, and the person who pushed a pull door is not at fault.

We take three things from that. First, a product should carry as much of the coordination as it can, so people do not have to. Second, it should be honest about what it assumes, because a system that disappears can hide its decisions. Third, it should leave people room: to stop, to go around, to do the thing in a way the designers did not expect.

None of this is a method, and a photograph of a crowd proves nothing about software. It is a reminder of what well-made systems are like to live inside. You can walk across a busy street without thinking about it, and that is a large achievement by a great many people you will never meet.