Sensory Load Is a System Resource

The nervous system is a constrained machine. It has bandwidth, latency, a thermal budget. Light, sound, fabric, social context — all of these consume capacity, and they consume it whether or not you notice them consuming it.

AuDHD bodies make the budgeting visible because they cannot hide the deficit. The fluorescent hum that a colleague filters automatically is, for someone else, a background process eating thirty percent of cognition for the day. The cost is not the noise itself — noise is cheap. The cost is the suppression. The cost is the daemon you did not consent to run, draining a battery you needed for the work the company actually hired you to do.

The load is real even when it is invisible

Sensory load behaves the way memory pressure behaves on a machine. Below a threshold, nothing is wrong. Above the threshold, everything slows down at once, and the symptoms look like personality flaws: short temper, decision fatigue, the sudden inability to compose a sentence in a meeting. We pathologize the surface and ignore the resource graph underneath. The person did not become incompetent at 3pm. The system ran out of capacity and started swapping.

This is why telling a sensitive nervous system to ‘just push through’ is the same instruction as telling a database to ‘just handle the load’ when the connection pool is exhausted. The advice is not wrong because it is unkind. The advice is wrong because it does not name the actual bottleneck. The bottleneck is the pool. The bottleneck is the room.

Designing the room is engineering work

When I build a workspace, I treat it the way I treat a production environment. What is the baseline draw? What are the spikes? What is the cost of recovery after a spike? The lamp that replaces overhead lights is not aesthetic preference. It is a config change that drops idle CPU by ten percent. The noise-cancelling headphones are not antisocial. They are a firewall. The Pomodoro timer is not a productivity hack. It is a scheduler with explicit yield points, because the nervous system, like any cooperative runtime, needs places to hand control back.

Teams that take sensory load seriously make these affordances defaults instead of accommodations. The conference room with a dimmer. The Slack channel that is allowed to be quiet for hours. The meeting that comes with an agenda twenty-four hours in advance so the room is not also a cold-start problem. None of this is expensive. All of it compounds.

What you get back

Give the machine fewer things to compensate for and you will get more of what you actually want from it: presence, judgement, sustained attention, the kind of careful pattern-matching that the loudest meeting room reliably destroys. The engineer who looked checked out in the standup will, given thirty minutes of quiet and a written brief, return the analysis that unblocks the quarter.

This is not accommodation in the apologetic sense. This is correct systems thinking applied to the substrate the rest of the work runs on. Every other resource in the stack — compute, memory, network, on-call attention — we model carefully and protect from waste. The human nervous system is the only resource we still treat as infinite, and then act surprised when it brownouts on schedule.

A note from the orchid dark

I am writing this from the same desk where, three years ago, I spent a full afternoon unable to figure out why I could not write a single useful sentence. The answer turned out to be a streetlight outside the window that had developed a faint flicker, just at the edge of what the eye registers consciously. I changed nothing about my discipline. I closed the blind. The afternoon returned. The machine had not failed. The room had.

Treat the room as code. Treat the body as infrastructure. The work that follows will be better, and it will cost less to produce.