humaneinfrastructure.org / section through daily life
Sheet 1 of 1 · drawn at full size
Everyone reviews the part you can see. The button, the label, the shopfront, the front door. Almost nobody reviews the pipe behind the wall, and the pipe behind the wall is the part that decides whether your morning goes well. This is a drawing of what is under there.
The layer people believe is the whole system.
Design attention pools at the top. The screen gets a critique, three rounds of copy, and a colour study. The scheduling logic underneath it gets written on a Thursday by whoever is free, and it is never looked at again.
The imbalance is not laziness. Surfaces are legible. You can hold one up in a meeting and everybody has an opinion. Infrastructure is only legible when it fails, and by then the conversation is about blame instead of craft.
When this is done badly The interface apologises for something the interface did not do. A beautiful error screen is still a promise the plumbing broke.
Water, power, transit, payroll, records. The oldest utilities and the newest.
A pipe decides who gets clean water. A timetable decides who can hold a job across town. A form field that rejects apostrophes decides which surnames are allowed to exist. None of these were argued as ethics. All of them were settled as defaults, by someone in a hurry, years ago.
That is the claim of this page: the choices buried deepest are the ones hardest to appeal. You can redesign a homepage on a Tuesday. You cannot redesign a national identifier scheme, so it keeps deciding things about people long after everyone who chose it has moved on.
When this is done badly Somebody is told their situation is not supported by the system, as though the system were weather rather than a set of decisions with authors.
Measured in the bad hour, not the demo.
Systems are specified for the healthy case: the user who is rested, literate in the interface, on good signal, with a charged phone and forty free minutes. Real load arrives at 2am, on a cracked screen, from somebody who is frightened, grieving, or holding a child.
Humane infrastructure is not soft. It is rated for the bad hour. It degrades in a way that keeps you whole: it saves what you typed, it says what went wrong in words, it lets you reach a person, and it never punishes you for the interruption that was not your fault.
When this is done badly Thirty minutes of work vanishes because a session expired, and the recovery path is to start again from the beginning.
The maintainer is a user too, and the one you meet most often.
Care that exists only at launch is decoration. Infrastructure is judged over decades, which means the real question is never how good it was on the first day. It is who is funded to keep it good on day four thousand.
So the humane choice is usually the boring one. Fewer moving parts. Formats that outlive their vendor. Documentation written for the tired stranger who inherits this. Design that assumes you will leave is more generous than design that assumes you will always be there to explain it.
When this is done badly A critical service runs on something one person understands, and everybody has agreed not to say this out loud.
Legibility is a safety feature.
Good plumbing is out of sight and still findable. There are drawings. There are access points. There is a stopcock somebody can reach without a specialist, and a label on it saying what it does.
Systems that cannot be inspected cannot be trusted, only tolerated. Every buried decision should leave a way back to itself: a record of what was chosen, by whom, and what it would take to choose differently. That is the difference between infrastructure and sediment.
When this is done badly The answer to why the system does that is nobody currently employed here knows.
The reward for doing this well is that nothing happens.
Nobody thanks the sewer. The whole point of a good utility is that it removes itself from your attention and gives you back the day. This makes the work structurally thankless, and it is why so much of it is underfunded until the week it collapses.
Which asks something of the people who do it: take the pride from the craft rather than the credit. Quiet is the correct outcome. A morning where the water was hot, the train came, the payment cleared, and nobody had to think about any of it, was built by someone.
When this is done badly The only time the work gets resourced is immediately after an outage, and the budget is gone again within a year.
Treat the pipe as though someone will one day drink from it. Someone will.
Humane infrastructure is a standard, not a style. It says that the care we spend on the visible half of a thing is the minimum owed to the half nobody photographs, and that a system is finished when it behaves well for a person having a bad day, not when it looks right in a screenshot.
It is an unglamorous discipline with a long payback. That is precisely the argument for taking it seriously now, while the concrete is still wet.
Acceptance criteria · six questions to ask before it ships