We sat down with Tim Spence, CEO of BSA, the top-rated healthcare, higher education, and research architecture firm providing comprehensive A/E/I/P services under one roof. Known for delivering environments that support healing, learning, and discovery, the firm brings a fully integrated approach to architecture, engineering, interior design, and planning, one that's increasingly shaping how complex projects are delivered, scaled, and sustained.
In this conversation, we explore how integrated design models are changing not just project workflows, but the outcomes organizations can expect, particularly when consistency, efficiency, and long-term performance matter most.
Tim Spence: The short answer is alignment, but alignment is really just the starting point. What fundamentally changes is the quality of thinking that goes into the solution.
When disciplines operate in silos, even very talented teams tend to solve problems one dimension at a time. Architecture optimizes for form, engineering for systems, interiors for experience, and planning for flow. Integration often happens late, and it’s largely about reconciling conflicts. That’s reactive.
In a fully integrated model, you’re not just coordinating earlier; you’re thinking differently from the beginning. Interdisciplinary teams bring multiple lenses to the same problem at the same time. That allows you to see connections, constraints, and opportunities that simply don’t surface in a linear process. You move from problem solving to problem framing, which is where the most meaningful innovation actually happens.
The second shift is seamlessness. For our clients, complexity doesn’t go away, but it becomes easier to navigate. There’s one team, one set of priorities, one shared definition of success. Decisions are more coordinated, trade-offs are clearer, and the process carries less friction. That translates into speed, but more importantly, into confidence.
The third shift is accountability for outcomes, not just scope. When you have an integrated team, no one is optimizing their piece at the expense of the whole. Everyone is aligned around how the environment will actually perform for the people using it. In healthcare, that means better support for healing. In higher education, it means environments that enhance learning. In research, it means spaces that accelerate discovery.
Ultimately, integration allows us to design not just buildings, but experiences and systems that work. And that’s where you start to see truly inspired solutions that improve lives in measurable ways.
Tim Spence: Cost and efficiency are often framed around managing what happens after design, but the biggest lever is actually the quality and speed of decisions at the front end.
We use a concept internally that a former Chairman/CEO, Monte Hoover, described as “first yield.” If you bring the right disciplines and stakeholders together early, fully engaged around the same problem, you dramatically increase the likelihood of arriving at a high-quality solution the first time. That solution already reflects the real constraints and opportunities, operational, technical, spatial, and experiential.
In more traditional models, decisions are made sequentially. Each discipline adds its layer, and over time, those layers start to conflict. That’s what creates rework, redesign, and ultimately cost escalation. It’s not that the original ideas were wrong. They were just incomplete.
An integrated approach changes that dynamic. You’re compressing the decision cycle while improving the quality of each decision. Engineers, architects, planners, and interior designers are all shaping the solution simultaneously, so trade-offs are understood in real time, not discovered later. That leads to a stronger first yield, which means far less rework downstream.
The result isn’t just efficiency in schedule or cost. It’s a reduction in volatility. Projects become more predictable because you’ve removed a large portion of the uncertainty that typically shows up during construction.
For clients managing multiple projects or long-term capital programs, that consistency becomes even more valuable. You’re not just optimizing a single project; you’re building a repeatable model for decision-making that improves outcomes across an entire portfolio.
Ultimately, cost control isn’t about being cheaper. It’s about being more certain, and that starts with getting the right answer earlier.
Tim Spence: Scalability ultimately comes down to whether you can carry clarity forward as you grow.
For organizations expanding across multiple locations, the risk isn’t just inconsistency in design. It’s the gradual loss of alignment in how decisions get made. Over time, that creates fragmentation in operations, infrastructure, and user experience.
An integrated approach allows you to institutionalize what works. Instead of each project starting from scratch, you’re building a shared logic that travels, how systems are organized, how spaces function, and how performance is measured. That creates a level of continuity across projects without forcing uniformity.
What’s important is that this isn’t about standardizing outcomes. It’s about standardizing the decision framework. When that’s consistent, teams in different locations can move faster and with greater confidence because they’re working from the same foundation, even as they adapt to local needs.
Without that, variability compounds. Small differences in one project become systemic inefficiencies across a portfolio. With it, scale becomes an advantage. Each project reinforces the next, improving speed, performance, and predictability over time.
That’s when growth stops being additive and starts becoming exponential.
Tim Spence: The risks aren’t random; they’re structural. When projects aren’t integrated, fragmentation shows up in very predictable ways.
Late-stage conflict is the most visible. Decisions that seemed reasonable in isolation begin to collide, and by the time that happens, you’re no longer optimizing, you’re negotiating compromises under pressure. That’s where time and cost start to move in the wrong direction.
There’s also a loss of decision velocity. When responsibility is distributed across multiple firms, it becomes harder to trace intent and act quickly. Questions linger longer than they should, and small issues take on more weight because alignment has to be rebuilt each time.
But the more significant risk is less obvious. It’s the gap between what was designed and how the building actually performs. On paper, everything can check out. In practice, misalignment between systems, operations, and user experience starts to surface over time. Those aren’t failures you fix with a change order. They become embedded in how the building functions day to day.
What’s important is that these risks tend to signal themselves early. You’ll see it in disconnected communication, in decisions being made without full context, in documentation that doesn’t carry intent forward. When those patterns are present, the outcome is usually already set in motion.
Integration doesn’t eliminate complexity, but it prevents that complexity from turning into fragmentation. And that’s the difference between a project that performs as intended and one that spends years being quietly corrected.
Tim Spence: The first thing I would say is don’t evaluate integration based on how a firm is structured. Evaluate it based on how decisions actually get made.
Many organizations can present an integrated org chart. Fewer can demonstrate what that looks like in practice. When do different disciplines engage? How early are constraints and opportunities surfaced? How quickly does the team align when something changes? Those are the signals that tell you whether integration is real or just coordinated on paper.
The second thing to look for is continuity of thinking. In a truly integrated model, ideas carry through from planning to design to execution without being diluted or reinterpreted
at each phase. You can see it in how clearly decisions are documented, how consistently intent shows up in the details, and how well the final environment performs.
And then there’s the track record. Not just whether projects were delivered, but how they performed over time. Did the process reduce friction for the client? Did it lead to fewer downstream corrections? Did the building operate the way it was intended to? That’s where integration becomes tangible.
Ultimately, what you’re looking for is a partner that reduces uncertainty in a meaningful way. Not by simplifying the problem, but by bringing the right perspectives together early and carrying that alignment through. When that’s done well, the value isn’t just in a single project; it compounds across everything that follows.