Understanding UX for Spaces: A New Approach to Design

Updated: Sep 17
UX for Spaces
Every space has its own rhythm. A family winding down at night. Friends around a table. A guest stepping into a hotel suite for the first time. The light, the air, the sound, and the controls in that space either support what's happening or get in its way. UX for Spaces is how we make sure they support it.
Where it came from
Software is designed around the person using it. Someone defines what it has to do, watches real people use it, and revises it until it feels obvious. We spent years doing that work, and then years designing and integrating the technology in buildings, where the same discipline mostly didn't exist. Systems were designed around categories, lighting, climate, AV, rather than around the people in the space. So we brought the two together.
How it works
It starts with discovery, before any hardware is discussed. We map how each space will actually be used. Morning routines. Evenings of rest. What "entertain" means for this family, or what "welcome" means for a guest walking in. Each of those becomes an intent for the space: sleep, focused work, a full table that can hear itself, an arrival that feels expected.
Then each intent becomes conditions the project can 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. Each condition is written as a requirement with a location, an operating state, a test, and a name attached to fixing it if it fails. Those requirements go into the construction documents alongside everything else the team builds to, and each space is measured against them once it's built.
That's the whole method. Intent, conditions, requirements, coordination, verification. The drawings, the acoustic treatments, and the programming are how the conditions get delivered. The measurement at the end is how anyone knows they did.
The Six Pillars of Building Intelligence
These are the qualities we hold every design against, and the benchmark we and the client use to judge whether a space succeeded.
Responsiveness. The space reacts to context, not just to triggers.
Anticipation. Preparation that feels like ease, never like surprise.
Awareness. Perception that supports the people in the space without watching them.
Control and Touchpoints. Fewer, clearer interfaces that a guest can use without instruction.
Adaptability. Systems that flex as life in the space changes.
Calmness. Technology that stays in the background until it's needed.
The six layers
We call them Sensory Systems: light, air, sound, water, energy, and presence. Each is a layer of the design and each is something the space can be tested on.
Light shifts with the day, at the levels the intent calls for, at the eye, at the hour it matters.
Air stays fresh and quiet, without sudden swings, with the door closed.
Sound is shaped for the activity, so speech carries where it should and equipment stays below notice.
Water is monitored, and a leak is caught at the first sign.
Energy is tracked and tuned so the systems stay reliable over time.
Presence is sensed, so the space responds to who's there without being asked.
Who does the work
UX for Spaces only works because three disciplines share the same intent.
UX design defines it. Discovery, daily rhythms, and lived scenarios become the brief every technical layer follows.
Acoustic design shapes how sound behaves. Geometry, materials, and isolation are coordinated early, with the architect and the mechanical engineer, so quiet is quiet and clarity holds.
Technical design brings the systems into alignment with the architecture and the intent. Sensor and interface placement. Schematics for audio and video. Specification of speakers, displays, amplification, and control platforms. Every detail in service of the experience, adaptable as needs change.
The outcome
A space designed this way doesn't feel automated. It's ready when it should be, quiet when it should be, and easy to live in without thinking about it. The systems disappear. What's left is the space doing what it was built for, and a record that shows it does.



Comments