The Layer Nobody Draws

Look at a floor plan and you see walls, circulation, and scale. You don't see the light that will reach the eye at nine at night, the sound that will arrive at the bed when the heat pump cycles, or the air that will still be in the room at four in the morning with the door closed. Those conditions aren't on the drawing. They're the result of the drawing, plus every system that gets specified after it.

Architecture sets the form. Interiors set the materials. The mechanical engineer routes the air. The lighting designer lights the surfaces. The integrator wires what's left. Every one of those people does their job well, to their own standard. What's missing is not skill. It's that no one on the team is responsible for how all of it lands on a single person sitting in the finished space.

A person doesn't experience a building one trade at a time. Temperature, air, reverberation, and light arrive together. A space that's acoustically fine, thermally fine, and well lit can still be a space where a conversation is tiring, an afternoon goes foggy, or a night's sleep is thinner than it should be. Each system passed. The space didn't.

That layer, the one that decides how the space feels to live in, gets designed whether anyone designs it or not. Leave it to chance and it still gets built. It just gets built badly.

UX for Spaces

Software gets designed around the person using it. Someone defines what it has to do, tests it with real people, and revises it until it feels obvious. Buildings mostly don't get that treatment. We took that discipline, user experience design, and applied it to the built environment. We call it UX for Spaces.

It starts before hardware. The first question isn't what technology the project needs. It's what each space has to do for the people in it. Is the primary suite for sleep? Is the study for four hours of uninterrupted work? Is the dining space for a full table that can hear itself? Those are the intents. Everything after them is in service of them.

Then each intent becomes conditions a project can actually deliver. A space for sleep needs defined limits on light at the eye in the evening, on sound at the bed when equipment starts and stops, on air with the door closed, and on how a person adjusts temperature in the dark. Those are written as requirements with a location, an operating condition, a test, and a name attached to fixing them. They go into the construction documents alongside everything else the team builds to.

Why it has to happen at schematic

The conditions are set by early decisions. Orientation sets daylight and road noise. Adjacency to plant, kitchen, and bath sets what's heard at night. Ceiling depth and shaft space set whether quiet air is even possible. Glass area and material area set how the space will sound. Those decisions are cheap while they're still lines on a page. By framing, most of them are locked.

So we work at schematic design, alongside the architect, the MEP team, the lighting designer, and the interior designer. We define the intent, translate it into conditions each discipline can own, resolve where those conditions collide, and document the result so the whole team is building toward the same thing. When the space is built, we measure it the way it will be used and we fix what fails.

What remains

The interface disappears. The rack disappears. What's left is a workspace where someone can think, a table where the conversation carries, and a bedroom where a body that's carried too much all day can finally set it down.

Technology isn't the meaning of those moments. It's the infrastructure underneath them. That's the layer we draw.