When Your Army Fights Your Project
Ibrahim Fawarji — ArchUp
In the early twentieth century, Sigmund Freud proposed one of the most contested theories in the history of psychology. The debate that followed lasted decades and continues in quieter form today. But beneath the controversy, the idea Freud was reaching toward was simpler than most of its critics acknowledged: human beings do not always fight over money or direct material interest. Sometimes they fight over status. Over authority. Over the desire to possess what the other person has.
I am not here to defend or dismiss Freud. What I can say, after more than twenty years of practice in architecture and construction, is that the dynamic he described appears with remarkable consistency on building sites. Not between men and women, as Freud framed it, but between architects and contractors.
A few months ago I was speaking with a senior architect whose judgment I respect. He was describing what he looks for when entering a new project. He did not mention price. He did not mention company size or equipment or track record. He said something much simpler.
He said he was looking for a contractor who was a man of his word.
In an era that moves quickly toward misreading, let me be precise about what he meant. He was not speaking about physical strength or anything biological. He was invoking an older professional meaning that anyone who has spent serious time on construction sites understands immediately: commitment, the honoring of an agreement, the willingness to stand with the project when things become difficult, and the refusal to convert every minor ambiguity into a negotiating opportunity.
That is the quality he was searching for.
The strange thing is that his words returned me to a different question entirely. Why does the tension between architect and contractor exist at all?
Both parties are working on the same project. Both are being paid from the same budget. Both, in theory, should be celebrating the same outcome when the building is complete.
And yet some of the most damaging conflicts in construction do not arrive from outside the project. They originate from within it.
The hardest enemy for a commander to fight is his own army.
The architect, by the nature of the role, is not a specialist in a single task. He is required to hold in his mind simultaneously the client’s expectations, the budget constraints, the regulatory requirements, the operational logic, the aesthetic ambition, the construction sequence, and the long-term performance of the building. He carries the complete image at all times.
The contractor, regardless of his competence and experience, typically enters the project from a more defined position. He has a scope of work, a price, and a specific set of tasks to execute.
This is where the friction begins.
The architect is fighting for the vision. The contractor is fighting for the margin. The architect is trying to protect the idea. The contractor is trying to protect his business. In successful projects, these differences produce a productive tension that sharpens both the design and the execution. In failing projects, they collapse into a conflict where the battle itself becomes the objective.
When that happens, the project stops being the goal.
What I have observed across years of practice is that the most dangerous conflicts rarely begin with a major engineering failure. They begin with something much smaller: the moment when one member of the team begins to read the other’s success as a personal threat.
This is what I would call the real dynamic beneath the surface of contractor-architect friction. It is not always about money, though money is always present. It is sometimes about the desire to occupy the authority that the other person holds. The contractor who has spent decades building things occasionally looks at the architect and asks, privately, why that person is the one whose name is on the project. Why that person makes the decisions about form and material and spatial sequence. Why the client calls that person first.
The answer, of course, is that the architect made a series of choices over many years: six years of formal education, unpaid internships, site exposure, technical licensing, and the sustained development of a particular kind of thinking that integrates aesthetic judgment with structural logic with human behavior. These were deliberate choices, made at real cost. The contractor made different choices, equally valid in their own terms, but directed toward a different kind of expertise.
The conflict emerges when the contractor, consciously or not, attempts to reclaim through resistance what he did not pursue through formation.
The clearest evidence of this dynamic appears in competitive tender situations. In a direct appointment, the architect typically brings a contractor he knows, one whose working relationship has been established over time and whose professional culture is compatible with the project’s demands. The contractor understands his role within the team and operates accordingly.
But in an open tender, the lowest price wins. A contractor arrives who has never worked with this architect, who does not know the project’s ambitions, and who has priced aggressively to win the contract. His model depends on recovering margin through variations, not through efficient execution.
In these situations, something specific sometimes occurs. The contractor identifies a gap in the tender documentation, an ambiguity, an item that was underspecified or omitted. He does not raise it before signing. He waits. He wins the contract. Then, once mobilized on site and the client is financially and emotionally committed, the gap becomes a negotiating instrument.
This is not an engineering problem. It is an ethical one.
Because the project could have succeeded if everyone had played for the same team. The information existed. The opportunity to resolve it existed. The choice was made to preserve it as leverage instead.
I want to be precise about something, because precision matters here.
The vast majority of contractors I have worked with over two decades are professionals who take their obligations seriously. The dynamic I am describing is not universal. It is not even common in the absolute sense. But it is common enough that every architect who has spent meaningful time on large or complex projects has encountered it, and few speak about it directly because the professional culture discourages that kind of candor.
The point is not to assign moral inferiority to one party. The point is to name a structural condition that the industry largely pretends does not exist.
Tender processes create incentives that are misaligned with project success. A system that selects the lowest price as the primary criterion is a system that rewards contractors who are skilled at pricing low and recovering margin later, not contractors who are skilled at building well. This is not a character failure. It is a rational response to the incentives the system provides.
The architect who understands this is not the one who complains about bad contractors. He is the one who structures his documentation, his contracts, and his client relationships in ways that reduce the space for misaligned incentives to operate. Ambiguity in tender documents is not just a technical problem. It is an invitation to the dynamic described above.
Freud may have been wrong about many things, and the specific theory that prompted this reflection has been contested and largely rejected within his own discipline. But he was right about one thing, and it is perhaps the most durable insight in his entire body of work: some conflicts are not really about the surface issue at all.
The contractor who makes a project difficult is not always doing so because the drawings were inadequate or the schedule was unrealistic. Sometimes he is doing so because the authority structure of the project places him in a subordinate position that conflicts with his self-understanding. And the architect who manages that situation poorly is not always doing so because he lacks technical competence. Sometimes he is doing so because he mistakes his formal authority for actual influence, and has not done the relational work necessary to make the contractor a genuine stakeholder in the project’s success.
Great projects do not require the smartest contractor or the largest firm or the most sophisticated equipment.
They require people who understand that their real success does not begin when they win the contract.
It begins when they become part of the vision.
And the architect’s job, beyond all the drawings and specifications and site meetings, is to make that transition possible. To make the project’s success feel like everyone’s success. To give the contractor a reason to fight for the building rather than against it.
That is what the senior architect meant when he said he was looking for a contractor who was a man of his word.
He was not describing a personality type.
He was describing the outcome of a relationship built correctly from the beginning.
✦ ArchUp Editorial Insight
The persistent operational friction between the architect and the contractor is a clinical symptom of systemic misalignment within institutional procurement systems and deep-seated psychological authority structures. Data layering of competitive open-tender ecosystems reveals that prioritizing the lowest financial bid incentivizes an adversarial business model dependent on margin recovery through variations rather than execution quality. This structural pressure generates an institutional decision framework where technical ambiguities within project documentation are weaponized as instruments of leverage. The building site is subsequently converted into an internal battlefield where struggles over status, subordinate positioning, and professional formation override collective operational success.
Consequently, the architectural outcome demands the urgent re-engineering of contracts and tender documentation from passive technical specifications into proactive instruments of behavioral and ethical alignment. Built massing can no longer survive on the myth of absolute formal authority; it requires the systematic elimination of informational gaps that invite strategic resistance from a misaligned workforce. In 2026 cities, where tightening capital markets place immense strain on complex infrastructure, the architect’s role must evolve into a strategic fiduciary of relational mechanics. The final transition of architecture depends on moving away from top-down spatial command toward a collaborative matrix, transforming the builder from an institutional adversary into an active stakeholder bound to the sovereign design vision.
