Most offices built in the last five years were designed for a version of work that no longer exists. Desks got denser. Meeting rooms got smaller. Reception areas got grander, then mostly empty. If you walked through a speculative office tower finished in 2019 and walked through the same building today, you’d notice something strange: the floor plate is identical, but the traffic never lands where the architect planned.
The reason is software. AI reshaped how businesses use their buildings long before it reshaped how those buildings look, and architects are still catching up to the gap. This piece is about that gap, and what to do about it.
What actually changed on the floor plate
Think about where people used to spend their day. A 2015 workplace was organized around three things: individual focus time, scheduled meetings, and circulation between the two. The floor plate was a percentage puzzle. Give focus work 60 percent, meetings 25 percent, circulation the rest, call it done.
That math collapsed. Spatial analytics suites now track occupancy in near real time. Scheduling systems route meetings to free rooms automatically. Access control logs, badge swipes, and desk sensors get stitched together into one live picture of the building, and facilities teams act on it weekly rather than quarterly.
The result is that demand has fragmented. A room that sat empty 60 percent of the time in 2018 might now swing between fully booked and totally dead within the same morning. Buildings designed around average use get punished by peak use. This is the argument most architecture clients miss when they scope a project: the floor plate isn’t the problem, the variance is.
According to the General Services Administration, workplace utilization studies consistently show that office space is underused relative to its booked capacity, which is why federal and private portfolio owners keep reexamining the assumptions baked into their floor plates.
Where does architecture get it wrong first?
Reception. Almost always reception.
Designers still treat the front-of-house as a moment of arrival, a place where a person walks up to a desk and announces themselves to another person. That exchange has mostly been automated away. Visitors check in from a tablet in the lobby. Deliveries get routed around the side. Contractors log in from a phone. A dozen interactions that used to happen at a fourteen-foot reception desk now happen in the thirty seconds before someone reaches the elevator bank.
I’d argue this is the biggest misallocation of square footage in a typical 2020s office. You’re paying prime rent for a room that mostly holds a plant and a paused screen. If I were speccing a new fit-out today, I’d cut reception by half and put the savings into acoustic zoning instead, because the loudest complaint I hear from actual occupants is never about the lobby. It’s about being able to hear yourself think.
Digital systems are the new load-bearing walls
Here’s a framing that helps clients: treat software integrations the way you’d treat structural steel. They’re not decoration, and you can’t add them late without paying a lot.
In a modern office, the invisible infrastructure usually includes a few of these:
- Occupancy sensors that feed a live floor map to facilities and the booking system
- Conversation analytics on customer-facing calls, pulled from telephony into the same dashboard the workplace team uses
- Badge and access logs joined to desk booking records
- HVAC scheduling that follows actual occupancy instead of a fixed 9 to 5 template
That second item deserves more attention than it usually gets. If a company’s customer service team sits in the same building, the contact center platform and the workplace platform are often run by different departments that never talk. Which is ridiculous. The contact center knows when call volume peaks. The workplace team knows when people are actually in the building. Stitch those two views together and you get something genuinely useful: the ability to schedule training rooms, quiet pods, and shift overlaps around the real rhythm of the business rather than a spreadsheet guess.
The National Institute of Standards and Technology has spent years publishing on how organizations should think about integrating operational systems that were never designed to talk to each other, which remains the core challenge in almost every smart-building retrofit.
Three retrofits you can spec this year
Most clients don’t get to design a new tower. They get a leased floor and a modest capital budget. Here’s what I’d prioritize, roughly in order:
- Acoustic zoning before furniture. Map the floor by noise exposure, not by team. Put the loud functions in one band and the deep-focus functions in another. This is cheap, invisible, and it changes how the space feels more than any new chair will.
- One dashboard, not four. Occupancy, booking, HVAC, and customer operations data should land in a single view. If they don’t, you’ll get conflicting answers to basic questions like “how full was Tuesday,” and everyone will stop trusting the data.
- Adaptable meeting rooms. Build rooms that convert by furniture, not by drywall. A room that flips from six-person standup to three-person focus session in under two minutes survives changing headcount. A fixed room doesn’t.
If you’re accounting for a customer service floor, factor in the tools that already monitor those interactions. Teams evaluating platforms in this space often start with something like cx automation, because the data it produces (call spikes, agent load, escalation patterns) has direct implications for room scheduling and shift design.
The Institute of Electrical and Electronics Engineers publishes widely on the standards that underpin building-to-system integration, and it remains the reference most engineers reach for when they need to argue that a subsystem should be open rather than proprietary. That argument matters more than you’d think, because closed systems age badly. A building with proprietary sensor firmware becomes expensive to modify within five years.
The uncomfortable truth about “smart” buildings
Plenty of buildings advertise intelligence they don’t have. Sensors installed but never wired. Dashboards no one opens. Booking systems launched with fanfare and abandoned within a quarter because the room layouts didn’t match what the system assumed.
The failure mode is always the same: someone bought a technology and never redesigned the workflow around it. The building got smarter. The people inside it kept doing exactly what they did before.
Architecture’s job in this environment isn’t to install more hardware. It’s to design the moments where human judgment still matters, and to stop spending money on rooms that software has already replaced. Reception desks, oversized lobbies, fixed training rooms in a company that trains remotely. Those line items deserve scrutiny.
If you’re in the middle of a fit-out and you haven’t yet asked what your operations data actually says about how your floors get used, do that before the next revision lands. The floor plate is a fixed asset, but the way people move through it isn’t, and the buildings that hold up over the next decade are the ones designed for movement, not for a flowchart. What’s your current floor telling you that you haven’t bothered to listen to yet?
