Article by Gilbert Boustany.

There’s a version of success in construction that almost everyone in the industry has chased at some point. It looks like speed. It sounds like “we mobilized in 48 hours,” or “we handed over two weeks early.” For a long time, that was the story that got told at industry dinners and written into company profiles. Fast was capable. Fast won work.

But fast, on its own, is no longer worth chasing and the projects suffering most right now are proof of that. Not because timelines don’t matter. They do. A brand that misses its store opening after the marketing campaign has already launched doesn’t need anyone to explain what that costs. Timelines are real. Penalties are real. Nobody is pretending otherwise.

What’s also real, though, is this: the teams consistently delivering well, at scale, under pressure, are not the fastest ones in the room. They are the clearest.

I have sat in conversations that cost more than most people realize, not because of the room rates or the consultants’ fees, but because of what should have been settled months earlier. A developer still working out what a space actually needed to do. A brand team that hadn’t reached internal alignment before the architect started drawing. A procurement model chosen in the same meeting where it should have been questioned.

In large-scale developments, ambiguity compounds fast. There are more stakeholders, more interfaces, more contractors, more handoffs. Unclear thinking at the top of a project doesn’t stay at the top. It travels. By the time it surfaces on site, it shows up looking like a program problem or a budget overrun. But it isn’t really either of those things. It’s an information gap that was never closed.

The organizations winning right now invest serious time and rigor at the front end in programming, briefing, and stakeholder alignment before a single appointment is made. That is not bureaucracy. That is protection.

The gaps nobody thought to assign

One of the most common failure patterns I see has nothing to do with conflict between parties. It’s the absence of ownership over the things no one thought to assign. The space between one contractor’s scope and the next. The decision sat unanswered in an email chain for three weeks. The risk everyone noted and nobody formally accepted.

The difference between a complex project that delivers and one that doesn’t is almost always the quality of its governance: how clearly roles are defined, how quickly decisions actually get made, and how honestly problems are surfaced when they appear.

I’ve watched projects with extraordinary talent fail because the structure around those people was unclear. I have also watched projects with far more modest resources deliver well because everyone knew exactly what they were responsible for and held to it.

The thing nobody wants to say out loud

This one is cultural, which makes it harder to address. There is still a tendency, particularly in this region, to manage upward by managing information. To smooth over early warning signs. To present a clean picture when the reality is messier.

It’s understandable. Nobody wants to be the person who raises the alarm. But projects don’t collapse overnight. They erode slowly, through a series of small decisions not to say what’s actually happening. By the time the problem is visible to everyone, the window to recover has usually already closed.

The teams I trust most are the ones who bring me problems early with context and a proposed path forward. That takes more courage than silence, and it’s worth more than almost anything else a delivery team can offer.

Speed still matters. Just not by itself.

The market here moves fast, and clients are right to expect responsiveness. But speed built on unclear briefs, fragmented accountability, and sanitized reporting isn’t a competitive advantage. It’s a risk being carried forward, one program update at a time.

The real edge, the one that compounds across years, projects, and relationships, is the ability to make things clear. And to keep them that way.