Communication and the Failure of the First Skyscraper Project
Long before steel beams and concrete pilings, humanity attempted its first recorded megaproject: a tower designed to reach the heavens. Genesis 11 tells us the builders had everything a modern project director would envy – unlimited manpower, a unified workforce, abundant materials, and total organizational alignment. “The whole earth had one language,” the text says, and it was this very unity that let the project surge forward. The tower rose. Momentum was real. Execution was, by every early indicator, working.
Then it stopped. Not because the bricks ran out. Not because the engineering failed. It stopped because communication broke down. The builders “could not understand one another’s speech,” and a project that had been racing skyward simply could not continue. Babel is history’s first documented case study in catastrophic project failure – and the cause was not technical. It was communication.
Over four thousand years later, we are still building towers, running EPC contracts, managing multinational teams across time zones, cultures, languages, and disciplines – and we are still failing for the exact same reason.
The Myth Engineering School Sells You
If you, like me, trained as an engineer, you were taught that project success is a function of design accuracy, materials science, accurate cost estimate and adequate budget, scheduling logic, and technical rigor. Get the calculations right, sequence the work correctly, and the project succeeds. This is the mental model most technical professionals carry into their first project leadership role – and it is precisely why so many of them struggle once they get there.
In over thirty years working on EPC and EPIC projects across Nigeria, Qatar, and international operations for companies including Shell, Chevron, Addax, Qatar Petroleum and major EPC contractors, I have seen the pattern repeat with remarkable consistency: the projects that fail rarely do so on the technical front. The steel is sound. The process design is sound. What fails is the human system wrapped around the technical core – the contractual clarity, the commercial alignment, the managerial discipline, and above all, the communication architecture holding the whole effort together.
Babel’s builders did not lack skill. They lacked a shared operating language once the disruption hit – and without it, coordination became impossible. That is not an ancient problem. That is Tuesday on most oil and gas construction sites.
Where Modern Towers Fail
Consider how communication failure actually shows up on a live project, because it rarely announces itself as “a communication problem.” It disguises itself as something else entirely:
Contractual ambiguity.
A scope statement written so broadly that the client reads it one way and the contractor reads it another way. Nobody lied. Nobody was incompetent. They simply were not speaking the same language when the contract was drafted – and that gap surfaces eighteen months later as a multimillion-dollar variation dispute.
Commercial misalignment.
Procurement negotiates a price without looping in the site execution team on the delivery implications. Finance approves a payment milestone that engineering knows is technically premature. Each function optimizes its own metrics while the overall commercial picture quietly deteriorates – because no one built the cross-functional communication loop that would have caught it.
Managerial silence.
A site supervisor sees a schedule slippage forming two weeks before it becomes visible in the official report, but there is no clear channel – or no psychological safety – for that information to travel upward quickly. By the time leadership hears about it, the float is gone and the fix costs ten times more than it would have.
In every one of these cases, the underlying technical work may be flawless. The tower is being built correctly, brick by brick. But the moment the language among the people building it fractures – between disciplines, between contract and execution, between site and head office – the project stalls exactly the way Babel’s did. Not from a lack of capability, but from a lack of a common tongue.
The Real Skill Gap in Engineering Careers
This is the uncomfortable truth for technically brilliant engineers stepping into project leadership roles: your calculus was never the risk. Your ability to read a P&ID, size a pump, or sequence a construction schedule got you into the room. It will not keep the project alive once you are in the room, because the room is full of commercial teams, contractors, regulators, and clients who all speak a different professional dialect – and nobody taught you how to translate between them.
Project management, at its core, is a communication discipline wearing a technical costume. It has been said that 90 percent of a project manager’s job is communication. The PMBOK, the contracts, the risk registers – these are all frameworks for making sure information flows accurately and on time between people who see the project from different perspectives. When that movement breaks down, scope creeps, costs escalate, and schedules slip – not because anyone failed technically, but because the organization, like Babel, lost its shared language mid-build.
Rebuilding the Tower – Correctly This Time
The good news is that unlike the builders of Babel, we are not at the mercy of divine intervention. The communication breakdowns that kill modern projects are structural, not supernatural – and structures can be redesigned.
That means building deliberate communication protocols into contracts, creating cross-functional checkpoints between commercial and technical teams, and training engineers explicitly in the managerial and interpersonal skills that engineering schools omit entirely.
This is precisely the gap my Project Management Fundamentals course exists to close. It is not another course on scheduling software or earned value formulas, but a practical grounding in the contractual, commercial, and managerial competencies that determine whether your technical expertise actually survives contact with a real project.
If you are an engineer stepping into project leadership, or a project professional tired of watching technically sound work get undone by communication failures you were never trained to prevent, this is for you.
Join my free Project Management Fundamentals webinar and learn the framework for closing the exact gap that brought down the first skyscraper – and continues to bring down projects today.
Register now and start building projects that don’t need a miracle to reach completion.
