Relational Infrastructure

Building foundations for genuine connection

Principle

Anti-Human Systems

Systems built with good intentions that quietly work against the humans inside them, and make people blame themselves for it.

What it is

An anti-human system is any design that optimizes around people instead of for them: the customer service phone tree with three menus before a human, the QR code menu, the self-checkout that films you and flags you for theft, the parking lot where pedestrians walk wherever cars drive, the stroad, the neighborhood with no sidewalks, the cafe with seating designed to make you leave. Each one was put in place for a reason that sounded fine in a spreadsheet: throughput, liability, labor cost, turnover. Together they form an environment where the human is the edge case and the system is the default.

The tell is a specific feeling. You did nothing wrong, but the design makes you feel like you did, standing at a kiosk that won't scan your item, waiting on hold for a human who may not exist, walking across a lot that clearly wasn't built with your legs in mind. That friction isn't a bug they forgot to fix. It's the cost of a decision made somewhere upstream, and it lands on you.

Why it matters

These systems do two kinds of damage. The first is that they delete contact: every kiosk and phone tree is a person you didn't talk to, a greeting that didn't happen, a weak tie that never got its chance to form. Multiply that across a day and a decade and you get isolation that nobody chose and no one can point to a cause for.

The second is quieter and worse. When the system fails you, it feels like you failed, and enough of that teaches people to stop expecting the world to have room for them in it. That lesson generalizes. Someone who's been made to feel like a defect at the self-checkout is a little less likely to strike up a conversation in line, a little more ready to believe the problem is them. None of this is inevitable. The original goals, safety, speed, lower cost, can almost always be met in ways that keep a human in the loop, but only if someone notices the design is hostile in the first place. Naming the pattern is the first step to routing around it, and then to building better.

What to practice

  • Route around them when you can: the staffed lane, the walk-in visit, the phone call that starts with a name
  • When a system makes you feel at fault, pause and check whether the design failed you instead
  • If you build or buy systems, ask who has to fight this to be treated like a person
  • Keep a human in the loop wherever the goal can still be met with one
  • Support the businesses that kept humans in the loop; they're holding the line for everyone
  • Say something when a place gets it right; the good defaults need defenders too

Go deeper

The deletion slide

Each rung down removes one more human from your day, for reasons that sounded fine in a spreadsheet

  1. 1

    The staffed counter

    The baseline. A person, a greeting, a name. Every rung below deletes a piece of this.

  2. 2

    The phone tree

    Three menus before a human who may not exist. The person is still in there somewhere, just guarded.

  3. 3

    The kiosk

    The greeting replaced by a screen that films you and flags you for theft, then makes the failure feel like yours.

  4. 4

    The window

    Drive-through and QR-code service. Contact reduced to a transaction slot.

    Skip the Drive-Through
  5. 5

    The app

    The entire errand, and every person who used to be in it, compressed to a doorbell notification.

  6. 6

    The loop with no human

    Fully automated everything. The system works perfectly, and nobody learned your name.

The way back upFrictionThe small inconvenience of doing things the human way, which is also where most casual contact comes from.

Put it into practice

  • Audit Your Social Media - Social media can point you toward real people or quietly substitute for them. An honest audit sorts the tools from the traps and reclaims your attention.
  • Design for Lingering - If you run a space, every design choice either invites people to stay and talk or tells them to leave. Choose on purpose.
  • Skip the Drive-Through - Park, walk in, and order from a person. Trade ninety seconds of savings for an actual human moment.

See also

  • Friction - The small inconvenience of doing things the human way, which is also where most casual contact comes from.
  • Acknowledgment - Being seen and greeted by the people around you. The smallest unit of belonging.
  • The Built Environment - The physical shape of a place decides how much contact is possible in it. Car-dependent sprawl deletes the encounters community is built from.
  • AI Companions - An AI companion is a product engineered to feel like a friend while removing the last human from the loop. It soothes the symptom and starves the need.
  • Relational Infrastructure - Relational infrastructure is the web of places, habits, and structures that make connection happen on its own. Like any infrastructure, you only notice it once it's gone.
← Back to the Field GuideLast updated July 21, 2026