I can tell you the exact moment my last open office broke me. Not metaphorically. Structurally.
It was 2:17 PM on a Tuesday. The person two desks away was eating an apple. Slack notifications fired every eleven seconds from three different laptops—not quite synchronized—creating a polyrhythmic interference pattern my brain could not stop modeling. The HVAC system was cycling at a frequency just below conscious hearing but well within the range my nervous system treats as threat. And the 340 fluorescent panels above me were flickering at 120 hertz, which most people cannot perceive and I cannot not perceive.
I was supposed to be writing a database migration. Instead, my entire cognitive architecture had been hijacked by the involuntary project of processing every sensory input in a 40-foot radius, simultaneously, with no priority filtering.
Because that’s what my brain does. That’s what it has always done.
I went to the bathroom, locked the stall, sat on the floor, and wrote the migration there. It was the most productive fourteen minutes of my day.
The bathroom stall was a better office than the office.
You’ve read the article about how open offices are bad. You’ve read it in the New Yorker and the Harvard Business Review and on LinkedIn, where someone looking contemplative on a balcony explained that open offices “reduce deep work.” Those articles are correct. But they’re correct in a way that still centers a neurotypical experience of discomfort. The premise is: open offices are somewhat worse for most people.
I want to talk about what happens when the building itself is an interface, and the interface was designed without your brain in mind.
The Office Is an API With No Error Handling
I’m a software designer. I think in systems. And when I walk into an open office, I don’t see a room—I see a real-time data stream with no rate limiting, no filtering, no access controls, and no documentation.
Here’s what a neurotypical colleague perceives at their desk: their screen, maybe the person next to them, a general background hum. Their perceptual system applies aggressive lossy compression. It discards most incoming data before it reaches conscious processing. This isn’t a skill. It’s a neurological architecture—a built-in spam filter that sorts signal from noise automatically, below awareness.
Here’s what I perceive: everything.
The conversation fourteen feet behind me. The footsteps approaching from the left, which my brain is already modeling for trajectory and arrival time. Seven distinct light sources in my peripheral vision, each with a slightly different color temperature. The smell of someone’s lunch from the kitchen 30 feet away—not simply “a smell” but a persistent data object my olfactory processing will not garbage-collect for the next forty minutes. The micro-vibration of the floor from the elevator shaft. Fifteen people moving in my sightline, each of whom my social cognition module is parsing for emotional state, intent, and threat level—not because I want it to, but because the system runs at boot and I haven’t found the off switch.
This is not a disorder of attention. It is a difference in filtration.
The software industry has a term for what happens when a system receives more input than it can process: buffer overflow. The open office, for my perceptual architecture, is a buffer overflow that’s been elevated to a design philosophy.
Who the Room Was Actually Built For
The open office didn’t emerge from research on productivity. It emerged from a theory of social transparency.
In the 1960s, a German consulting firm called Quickborner developed Bürolandschaft—”office landscape”—based on the premise that removing physical barriers would increase communication flow. The spatial logic was explicit: if people can see each other, they will collaborate. Walls are friction. Openness is efficiency.
This is a theory about how humans work. More precisely, it’s a theory about how certain humans work—specifically, those whose nervous systems treat ambient social information as low-priority background data that can be cheaply discarded.
By the 2000s, the open plan had merged with Silicon Valley’s ideology of performative collaboration to produce the modern tech office: vast floors of shared desks, “collaboration zones,” glass walls that create the visual language of transparency while providing zero acoustic isolation. The architecture encodes a specific claim: the most productive worker is the most visible worker.
That claim is untestable for me. Not because I lack productivity, but because in the environment designed to measure it, my processing resources are entirely consumed by the act of surviving the room.
I want to be precise here, because this is where the conversation usually gets soft. I’m not saying open offices make me “uncomfortable.” Discomfort is a preference. What I’m describing is a computational problem. My brain allocates processing resources involuntarily to sensory input. In a high-input environment, those resources are unavailable for the task I was hired to do.
This isn’t anxiety. It isn’t a failure of willpower. It’s architecture meeting architecture—the architecture of the room colliding with the architecture of my nervous system, and the room winning, because the room was here first and the room gets to set the defaults.
The Defaults Are Always Someone’s Defaults
In software, we talk about “sensible defaults”—the pre-set configurations a system ships with, designed for the assumed typical user. The open office is full of sensible defaults. They’re just not my sensible defaults.
The lighting: fluorescent, optimized for even coverage and energy efficiency. For neurotypical visual processing, this reads as “neutral.” For mine, it’s a persistent low-level strobe I can’t tune out, degrading my visual processing over hours, producing a specific fatigue that lives behind my eyes and in my jaw, where I’ve been clenching against it without realizing.
The noise floor: “ambient conversation,” which neurotypical auditory processing reads as a soft, ignorable wash. For mine, it’s a concurrent stream of partially intelligible language that my processing centers will not stop attempting to decode. I’m involuntarily eavesdropping on every conversation within range—not because I’m nosy, but because my auditory system doesn’t know how to mark speech as background. Speech is always foreground. Every voice is a thread my brain opens and cannot close.
The spatial layout: “open sightlines,” which neurotypical visual processing reads as spaciousness and community. For mine, it’s a perpetual motion field—every movement in my peripheral vision triggers an orientation response, a tiny involuntary redirect that individually costs almost nothing and collectively costs me my entire afternoon.
Each of these defaults is a design decision. Each design decision encodes an assumption about the user. The user it assumes is not me.
The Accommodations Model Is Backwards
When I’ve raised these issues at jobs, the response follows a reliable pattern. First, sympathy. Then, accommodation. Noise-canceling headphones. A desk near the wall. Permission to work from home on Fridays.
Look at the structure of that response, because the structure is the problem.
The accommodations model treats the open office as the neutral baseline—the zero-state—and treats my sensory processing as the deviation requiring correction. The headphones are a patch applied to me. The wall desk is a configuration change applied to me. The remote day is an exception granted to me.
The room remains unchanged. The room is not the problem. I am the problem.
This is exactly how bad software works. A user reports the interface is unusable. The dev team, instead of examining the interface, ships a plugin that modifies the user’s interaction with it. The plugin is clunky. It solves some problems and creates others. Every time the underlying interface updates, the plugin breaks, and the user files another ticket, and the cycle begins again.
The accommodations model doesn’t fix the design. It maintains the fiction that the design is neutral.
The Same Architecture That Breaks Me Makes Me Good at My Job
Here’s what I think is genuinely interesting—not as an argument for my own comfort, but as a design observation.
My sensory processing is high-bandwidth, low-filter. I take in more data and discard less. This is expensive. It costs energy, processing speed, and it means environments designed for low-bandwidth users overwhelm me quickly.
But the same architecture that makes the open office uninhabitable also makes me extremely good at what I do.
I catch bugs other developers miss because I process code at a level of granularity that isn’t volitional but is very thorough. I notice inconsistencies in system behavior others overlook because their perceptual filters classified those inconsistencies as noise. I see patterns across large codebases because my brain doesn’t pre-filter for relevance—it takes everything in and finds the structure after, which is slower but often more accurate.
The environment is optimized to suppress the exact cognitive architecture it hired me for.
This isn’t a paradox. It’s a design failure. And it reveals something important: we’ve confused “the environment most people can tolerate” with “the environment that produces the best work.” These are different claims. The open office satisfies the first. It has never been shown to satisfy the second.