Culture Is the New Contract: Lessons from the 2025 DBIA Conference

As someone immersed in the commercial construction space—especially in the pre-construction and design-build arena—I walked away from this year’s DBIA Conference in Las Vegas with one dominant theme: collaborative culture drives high-performance design-build projects. Across multiple tracks, the message repeated: when Owners, GCs, Designers, Architects and Project Managers act as one unified team instead of separate silos, the outcomes drastically improve.

Here’s a breakdown of what I observed, what I believe, and how Owners and GCs can apply this to their next design-build or AI-enabled design-build project.

Why this matters (and why design-build is growing)

Let’s start with a refresher: design-build continues to grow because it gives project teams a single contract for design + construction, aligns incentives, and allows schedule and cost benefits. DBIA reports that design-build is delivering projects faster and with fewer cost overruns than traditional design-bid-build (DBB). DBIA+1

But here’s the catch: all that advantage evaporates if your procurement and culture treat design-build like old-school DBB. I heard several speakers underscore that part of the reason the method succeeds is not just the contract form—but the team mindset.

This aligns with what I’ll call “AI-savvy design-build culture” too—because as we layer in artificial intelligence tools (for scheduling, risk-analytics, collaborative dashboards, etc.), the human element—trust, communication, shared culture—becomes even more important.

Major takeaway: Culture over process if you want success

A recurring message at the conference: successful design-build is less about neat checklists and more about collaborative culture. Some notable observations:

• Many parties on a design-build team are new to the delivery method. That means upfront trust building becomes mission-critical.
• It’s not enough to agree on the schedule, budget or scope—you must also align on how you’ll work together, how you make decisions, how you escalate issues.
• The best design-build teams act like they’re building a company for that project: they “hire” people they trust to get the job done and participate in the culture, not just fulfill a contract.
• That company mindset demands openness and vulnerability—something rare in a traditional construction procurement environment.

For example: DBIA’s “Collaborative Delivery Leadership Academy”, in partnership with Barbara Jackson, identifies leadership, communications, teaming, trust, mindset and culture as stand-out modules. DBIA Education+1

In my opinion: if you’re an Owner or GC thinking “we’ll just pick the lowest cost GC/design team and use the DB contract” you are missing the culture piece—and you’ll run high risk. The culture piece is what unlocks the speed, innovation, AI-enabled collaboration, and fewer change orders.

How to develop the optimal design-build culture

From my notes and conversations at the conference, here are three actionable steps to build the right culture at the outset of a design-build project (or when transitioning into AI-enabled design-build/lean + digital workflows).

1. Get the right people on the bus.
   Think about organizational competencies when choosing your partners. The University of Florida’s general leadership competency model outlines key quadrants: Build Trust, Advance Vision, Generate Alignment, Cultivate Talent. They are publishing their construction industry specific work soon!
   In practical terms, ask:
   • Do the GC and Designer have prior design-build / integrated delivery experience?
   • Are they willing to adopt early collaboration, data sharing, digital tools/AI dashboards rather than working in silos?
   • Are they comfortable with ambiguity early on (because early design, early budget risk, AI scenario modeling will bring it) rather than waiting for “complete drawings” before collaborating?
     If the answer is no, you’ll still use DB—just expect more friction.
2. Set a clear culture process from the start and reinforce it at every interaction.
   At the kick-off session, embed the process: define roles, responsibilities, decision-making rights, how you escalate disagreements, how you use digital collaboration tools/AI tools to drive transparency.
   Make sure you explicitly cover:
   • “How do we make decisions distributively?” — We heard in the first big session on Day 1 that distributed decision-making is possible if you agree on the process at the start.
   • “How will we use our AI/data tools for schedule, risk, design trade-offs?”
   • “What are our communication norms—what must happen before each meeting, who leads, who documents, who follows up?”
     Every meeting agenda should reinforce those norms: e.g., “What changed since last time? What data do we have? What decisions are outstanding?”
3. Abide by best practices: transparent schedules, candid conversations, vulnerable discussion.
   The process side of design-build (tools, schedule, contract language) matters—but only if you use it as a vehicle to support the culture. For example: share your draft schedule openly, use AI-driven schedule risk analysis, highlight “we don’t know yet” rather than pretending you do.
   Hidden facts or silos kill trust faster than missed deadlines. Best practice: collaboratively build a risk register, review openly as a team, update honestly.

How to keep that culture going throughout the project

Starting strong is critical—but sustaining the culture is equally important, especially when things get hard (which they will). Here’s how to keep it alive:

1. Gain and keep trust through transparent communication—even during hard conversations.
   We heard a lot about “exquisite communication” at the conference. The principals must stay aligned with one another and with the Owner. When a GC or Designer says “we need to adjust schedule” or “budget risk here”, the team must respond with candor: “Here’s the issue, here’s why, here’s the impact, here’s our recommendation.” That builds trust and keeps decision-making flowing.
   As one speaker (Jim Whitaker) noted in a “Gone Wrong” session: good communication with high Owner engagement can sometimes make up for a lack of deep design-build experience on the GC side. DBIA+1 If you, as an Owner, engage actively, ask the right questions, are transparent yourself—you can help accelerate the learning curve of your team.
2. Create a “culture of accountability” where each principal owns their deliverables and no one person is the task-master.
   In many conventional projects, the GC ends up chasing everything—design, submittals, approvals. In high-performing design-build, every key stakeholder (Owner, GC, Designer, PM) owns a piece, shows up proactively, and the team behaves like a company rather than disparate vendors.
   For example: The Designer owns design milestones + integration with GC; GC owns constructability & schedule; Owner owns strategy/vision + major decisions; the “company” mindset means shared goals, shared transparency.
3. Consistent communication expectations with thoughtful preparation.
   This means scheduled check-ins (weekly or bi-weekly), pre-meeting prep (who brings data/agenda, what are the decisions, what tools/AI dashboards will we review), designated roles in meeting, and follow-up notes with action owners and deadlines. Because we’re bringing more digital tools and AI into design-build, the data becomes more visible—but that’s only useful if communication is habitual.
   Example: Use a shared collaboration platform where schedule, budget, risk logs, decision logs are available; each meeting starts with review of “what changed” and ends with “what actions and owners”. That rhythm reinforces the culture.

Special note to Owners

Since your role as Owner is unique, here are a few things I’d highlight specifically for you:

• You must trust that the GC, Designer, Architect, Project Manager, etc., are acting in good faith and guiding the process for the betterment of the project. But trust doesn’t mean abdication—it means leadership.
• To develop that trust, every party needs to be transparent in their actions. They must be clear with decisions and share the why behind recommendations. For instance: If your designer suggests a major change, don’t just ask “how much?” Ask: “Why is this better? What risk does this mitigate? How does this align with our overall project goals (schedule, scope, budget, future operations)?” That “why” builds alignment.
• Treat the team as a “company” (for this project) rather than a bunch of vendors. That mindset shift is subtle but powerful: you see the team as your partner, and you invest in their culture and process. When you make that shift, you’ll get higher engagement, fewer surprises, and stronger performance.

What I left Vegas thinking (and what you should too)

Walking out of the DBIA Conference this year I walked away with a few sharp thoughts:

• Even if you’re experienced in design-build, never treat culture as a side-car. Culture is the glue that turns the method into performance.
• If your organization is new to design-build (less than 3 projects), allocate dedicated time to relational/collaborative skills before jumping into execution. This means team formation, culture process, communication norms, digital/AI tool alignment.
• Tools and contracts matter—but only if your team trusts each other and communicates openly.
• As an Owner, your role evolves in design-build: you still make major decisions, but you also act as team steward, culture setter, blocker remover, clarifier of “why”.
• For GCs especially: the design-build opportunity isn’t just “do more projects” it’s “do them differently”. If your firm can lead culture, you gain a clear competitive edge.
• Finally: if you treat your project team like a company and invest in the people + process of collaboration early, you’ll reap benefits throughout: fewer surprises, smoother decisions, better schedule, better cost control, happier stakeholders.

If you take away one thing from DBIA in Vegas: You don’t just execute a Design-Build contract—you build a team and a culture. That cultural foundation is what activates all the benefits of design-build and AI/lean integration. For Owners and GCs diving into or deepening their design-build practice, invest early (and continuously) in trust, shared expectations, clear communication, accountability, and the right digital/AI-tools platform. The mechanical parts (contracts, schedules, tools) will follow—but only if the people and culture lead first.

Ready to make your next design-build (or hybrid AI-enabled design-build) project a high-performing team instead of a siloed procurement? Let’s build the culture—and the outcomes—together.