The 5 Love Languages of Construction

I was handed the book, The Five Love Languages: How to Express Heartfelt Commitment to Your Mate. Uggh, another self help book I thought. I had just finalized my divorce and everyone was just trying to be helpful. I read it and found it very interesting. The basic idea being that communication needs to be adapted to the person receiving the communication and not the other way around. Some people are better communicators than others, but in construction, it is about context. This is why we built Foundation Zero to be the rosetta stone of design and construction communication.

Two firms sign a contract to build the same thing, in the same place, for the same people. Then they spend the next two years acting like they’re on opposite sides of a war.

I’ve watched it happen more times than I can count. The architect protects the design. The GC protects the schedule. The owner protects the budget. The subs protect themselves, because history has taught them nobody else will. Everyone is technically doing their job. And the building — the actual reason all these people are in a room together — quietly becomes the thing that suffers.

We’ve come to treat this as normal. It isn’t. It’s a choice we keep making by default.

A few questions I keep getting after people read this one. Answered straight.

Isn’t the adversarial relationship just how construction works? Everyone’s protecting their own risk.

Protecting your risk is rational. The problem is the system we’ve built to do it. When the only way to protect yourself is to hoard information and paper the trail, you get people acting like opponents even when their interests actually line up. The behavior is a symptom. The distance between the parties is the disease. Fix the distance and most of the “difficult personalities” turn out to be reasonable people who just couldn’t see what you were seeing.

You say blame the system, not the people. Isn’t that letting bad actors off the hook?

There are bad actors. There always will be. But if your explanation for a broken project is “we got unlucky with the people,” you’ll be unlucky forever, because you’ll keep rebuilding the same conditions and hiring new people to fail inside them. I’d rather fix the thing that turns good people adversarial than keep auditioning for saints.

Isn’t “AI as a rosetta stone” just a nice metaphor? What does it actually do?

It translates a decision across the languages on the table. A design change gets made in the architect’s language of intent — the rosetta stone renders it, right then, into what it means for the schedule, the sequence, the cost, and the owner’s opening date. The information already exists on most projects. What’s missing is anything that reads it across parties fast enough to matter. That’s the concrete job: real-time translation of consequences, in the meeting, not in a report weeks later.

How is that different from the software we already have?

Most tools are built to help one party do their own job faster — estimate quicker, generate the claim letter quicker, run your side of the fight quicker. That’s pointed inward. The rosetta stone is pointed at the middle of the table. It’s not there to help you win against the other parties; it’s there so everyone can see the same reality at the same time. Same technology, opposite intent.

Are you saying AI replaces the architect’s or contractor’s judgment?

No, and that’s the whole point. Judgment stays with the people who’ve earned it. What gets removed is the delay and the fog — the weeks between a decision and its visible consequences, the translation loss between four disciplines. AI accelerates human potential here; it doesn’t substitute for it. The person still decides. They just get to decide with their eyes open.

Does “no more RFIs” actually mean no RFIs?

Directionally, yes — and I mean it as a goal, not a slogan. The RFI exists to manage uncertainty that wasn’t resolved when it was cheap to resolve. If the question gets answered in the room, with everyone seeing the same context, before the work is in place, then there’s nothing to formally document later. You won’t get to zero on day one. But “how do we resolve this together, now” should replace “how do we document who’s responsible, later” as the default move.

We already do a project charter. Why are you making a big deal of it?

Most charters are a fat binder written to satisfy a process, and nobody reads them after the kickoff. I’m talking about something different: a short, plain-spoken agreement on what this project is actually for, what “done well” looks like, and what you’ll optimize for when the hard trade-off shows up. The test isn’t whether you have a document. It’s whether, eighteen months in, the owner and the GC would still describe success the same way. If they wouldn’t, you never had a charter — you had paperwork.

What if the parties genuinely want different things? A charter won’t change that.

Then you want to find that out in week one, not month eighteen. A real charter surfaces the disagreement while it’s cheap to reconcile. Sometimes the answer is a hard conversation up front. That’s a feature. The adversarial project is the one where the mismatch stays hidden until it detonates in the field.

This sounds expensive and futuristic. What can I do on my next project without any new technology?

Start with the charter — that costs a conversation, not a license. Get the owner, the designer, and the builder to write down, together, what success means and how you’ll handle the first big trade-off. Then in your meetings, make a habit of asking out loud what a decision does to the people downstream before you lock it in. You don’t need a platform to start closing the distance. The technology makes it faster and better. It doesn’t make it possible — you already can.

Why does any of this matter beyond cost and schedule?

Because someone’s life happens inside the things we build. When we let the project turn into a defensive crouch, the building pays for it, and so does the joy of making it. Work this meaningful shouldn’t feel like a fight. Closing the distance between the people around the table isn’t just good business. It’s how you get back to the part of this work that’s worth doing.