By Bruce Wilson
In architectural education, we are often led to believe that architecture is the creative discipline, while engineers deal with the technically specific and predictable. The architect is flamboyant and whimsical; the engineer is precise and, if we are honest, perhaps a little automatic and dull.
How wrong we were.
The longer we practice, the more we realise that engineering is no less a human endeavour than architecture. Structural engineers, civil engineers, mechanical engineers and quantity surveyors are not technical machines processing information with perfect certainty. They work under pressure. They make judgments with incomplete information. They balance competing constraints. They exercise creativity. They carry responsibility. In short, they are as human as the rest of us.
This matters because the construction industry often behaves as though project delivery is a technical problem rather than a human one. We create increasingly sophisticated systems to manage information, define responsibilities and coordinate outputs. Yet despite these systems, projects still encounter the same difficulties they always have.
For example, every BIM execution plan tells us exactly how to do things technically. The level of clarity and coordination that modern project planning tools provide is remarkable. They define roles, responsibilities, information exchanges, timelines and outputs with increasing precision. On paper, everything is clear.
And yet it always goes wrong, because the associated human behaviour is never addressed in these plans.
None of this is surprising to anyone who has actually delivered a building. But it raises an important question: if our plans are so clear, why does reality diverge so consistently?
The answer is simple, and largely unspoken.
Projects are delivered by people, not systems.
Execution plans describe how work should flow in ideal conditions. They do not describe what happens when those conditions are not met. They do not account for pressure, uncertainty, fatigue, competing priorities, variance in experience, or simple human error. They do not explain how a team should respond when something goes wrong, which it inevitably will.
In our experience, the quality of a project is determined less by how well it is planned and more by how well the team responds when the plan breaks down.
Broad professional culture matters.
A high-functioning team does not rely solely on the plan. It has a shared understanding of how to behave under pressure. It knows how to communicate clearly when something is wrong. It knows how to take ownership rather than deflect responsibility. It knows how to solve problems together rather than retreat into contractual positions.
At BWA, we take our relationship with engineers extremely seriously and believe that this behavioural layer is not optional; it is a core part of delivery.
The first structure defines what should happen. The second determines what actually happens. Most of the industry invests heavily in the first and assumes the second will take care of itself. Our experience is that it does not.
If anything, as projects become more complex and more tightly coordinated, the human dimension becomes more critical, not less.
Engineers are people too. So are architects. So are clients. So are contractors.
We invest heavily in coaching and team performance within our practice, and we know that many other firms do the same. We have recently broadened our training to include project teams.
If you are a fellow professional and believe that the future of project delivery lies not only in better systems, but also in helping the people inside those systems perform at their best, then get in touch with us and let’s explore what that might look like together.