Most buildings begin with an answer already in mind:
We need an airport terminal. A school. A stadium. An office. A store.
From there, the design process often works backward from precedent. We study what already exists, establish a program, improve the model, design the building and spaces, and eventually integrate the technology required to make it work.
This is a perfectly rational way to design. But it may also be increasingly flawed.
Technology now changes faster than buildings do. It changes how people work, travel, shop, learn, communicate, operate businesses, and experience the world around them. More importantly, it continually creates new capabilities — things we can do today that were difficult, expensive, or impossible only a few years ago.
And yet we often begin major building projects by assuming the building type itself is settled. What if we reversed that?
What if, before accepting the typology, program, or precedent, we asked a more fundamental question:
What does technology make possible now?
That is what I call tech-first thinking.
A first lens, not a first priority
Tech-first does not mean putting technology before people. It does not mean filling buildings with screens, sensors, robots, or whatever happens to be fashionable this year. And it certainly does not mean allowing technology vendors to dictate the design.
Tech-first is a first lens, not a first priority. Human outcomes remain the goal. The difference is that technology is considered before the physical answer is assumed, because technology can fundamentally change how those outcomes are achieved. A conventional process might move from:
known typology → precedent → program → design → technology
A tech-first process asks us to think forward:
desired outcome → technology and capability → behavior and operations → program and typology → design
That inversion sounds subtle, but it can produce radically different results.
Instead of asking how to make a better check-in hall, we might first ask why check-in needs a hall.
Instead of asking how many classrooms a school requires, we might first ask how emerging learning technologies change what a classroom is for.
Instead of determining how much physical capacity future demand requires, we might ask whether digital networks, automation, or new operating models can satisfy some of that demand without adding equivalent physical resources.
Sometimes the answer will confirm the building we already expected to build. Sometimes it will change it. Occasionally, it may reveal that we should be building something else entirely. That is the point.
Why this matters now
There are at least three reasons to think tech-first. The first is practical: it makes us better designers of the buildings we already have.
Modern buildings are increasingly dependent on operational technology, IT, data, software, automation, and interconnected systems. Airports are obvious examples, but the same is increasingly true of hospitals, workplaces, schools, entertainment venues, homes, and cities. The physical environment does not operate independently from the digital one.
Understanding that relationship early (and well) helps us design buildings that actually perform better — operationally, functionally, and experientially. Technology should not arrive late in design as a layer of equipment that needs somewhere to go. It should inform the thinking that determines how the place works in the first place.
The second reason is financial: it helps us avoid designing the right building for the wrong future.
Buildings are long-lived capital investments built around assumptions. Assumptions about behavior. Demand. Staffing. Operations. Transportation. Business models. Customer expectations. Technology.
Those assumptions eventually become square footage, infrastructure, structure, circulation, utilities, and concrete. The problem is that the building may last fifty years while some of its underlying assumptions last five.
For anyone planning a project that may take years to design and construct — and then operate for decades — the question is not simply whether the design works today. It is whether the assumptions behind it have a reasonable chance of surviving tomorrow.
Tech-first thinking makes those assumptions easier to see before they become expensive to change. But avoiding mistakes is only half the opportunity.
The third reason is the most exciting: tech-first thinking makes us better innovators.
Technology expands the space of possibility. New capabilities create new behaviors. New behaviors create new business and operating models. Eventually, those changes alter the physical environment.
The challenge is that architecture usually responds late. We retrofit new technology into old building models until the accumulating change becomes impossible to ignore. Only then does the typology evolve. Tech-first thinking asks whether we can see that evolution earlier. A useful thought experiment is:
If today’s technology had existed when this building type was invented, would we have invented the same building?
Sometimes the answer exposes an obsolete assumption. Sometimes it reveals unnecessary space or complexity. Sometimes it suggests a distributed model instead of a centralized one. And sometimes it opens the door to an entirely new typology.
This is where technology stops being something that happens to architecture and becomes a way of imagining what architecture could become.
The gap worth closing
There is a growing gap between what technology makes possible and what we actually build. Part of that gap is unavoidable: Buildings require certainty. Capital demands evidence. Safety, regulation, operations, and human behavior do not change as quickly as software.
Precedent exists for good reasons. The goal is not to reject it — the goal is to stop confusing precedent with inevitability. The most consequential question at the beginning of a project may no longer be:
What have we built before?
It may be:
What has become possible since then?
That question can lead to a better version of an existing building. It can expose a costly assumption before it becomes permanent. Or it can reveal a future nobody has designed yet.
Think tech-first. Then design what should be.