Lead Design Consultant

In some markets, the architect governs the project. In others, they decorate it. The difference determines who captures the value.

One of the most disorienting things about working across multiple countries is discovering how differently the same profession is understood.

In Spain, the architect carries broad legal and technical authority: over structure, systems, envelope, and delivery. That responsibility is a burden and a constraint, but it also means the architect is the natural integrator of the project. The one who holds the thread from concept to certificate of occupancy.

In Australia, the split came earlier and more completely. Engineering disciplines separated out, project managers assumed coordination authority, and the architect’s territory contracted toward design intent and documentation. The role is well compensated and professionally respected, but structurally limited.

In Vietnam, the picture is more fluid. International firms compete fiercely for concept design, local firms undercut on technical documentation, and external project managers handle time and cost. The architect can end up owning the most visible part of the process while having the least control over its outcome.

None of these models is inherently wrong. Each reflects a specific market’s history, liability framework, and construction culture. But they produce very different outcomes for project quality, particularly in complex, large-scale developments where design intent needs to survive contact with engineering, procurement, and site conditions.

That’s the gap the Lead Design Consultant model was built to fill. Not as a title, but as a structural role: the architect, or architect-led team, that contracts and coordinates all disciplines, governs design decisions across every phase, and takes responsibility for consistency from strategy to delivery.

In markets where the architect has retained authority, it happens by default. In markets where that authority has been ceded, it has to be rebuilt deliberately, through the right contractual structure, the right team configuration, and the credibility to hold the room when engineering or cost pressure pushes back on design intent.

I’ve led and developed that capability within a firm that instinctively resisted the role, because expanding the architect’s authority meant challenging how business development, client relationships, and project control had always been structured. The resistance wasn’t technical. It was organisational, because the LDC model redistributes who controls the project, and therefore who captures its value.

#DesignLeadership #LDC #Architecture