Nobody builds a communication silo on purpose.
They form organically — as the natural result of people working independently in separate systems, with separate filing habits, communicating in parallel streams that never quite converge. By the time a silo is causing visible problems, it's been there for weeks. Maybe months.
Understanding how silos form is the starting point for preventing them.
The Anatomy of a Silo
The inbox silo. A design decision is made in an email thread between the PM and the structural engineer. The MEP engineer wasn't on the thread. They make a coordination decision that conflicts with the one made in the email exchange. Nobody knows until both sets of drawings are overlaid in a coordination review.
The verbal decision silo. A client calls the principal and provides direction on a design element. The principal acknowledges the direction but doesn't document it. Three weeks later, when the project architect produces drawings based on the earlier design direction, the client is confused about why their input wasn't incorporated.
The discipline silo. Each consultant works in their own system, issues their own coordination drawings on their own schedule, and communicates primarily with the architect of record. The structural and MEP engineers have limited visibility into each other's work until a formal coordination review, which is often too late to avoid significant rework.
The version silo. Team members working from different versions of the same drawing believe they're coordinated when they aren't. The silo isn't in the communication channel, it's in the file system.
What Silos Actually Cost
The cost of communication silos is almost always invisible in the project record, because it shows up as symptoms rather than causes.
Rework coded as "client-directed changes" that was actually triggered by a decision the client communicated through a channel the design team didn't monitor. Coordination failures coded as "consultant error" that were actually caused by the consultant working from outdated information. Schedule slippage attributed to "complexity" that was actually caused by coordination gaps that could have been resolved weeks earlier.
The true cost compounds: the rework happens, the schedule compresses, the team works longer hours to recover, and nobody identifies communication silos as the root cause. So the conditions that created them persist into the next project.
What Closes Silos
One principle closes most communication silos: project information lives in the project, not in individual inboxes, personal drives, or verbal agreements.
In practice, this means:
- Design decisions made in any channel get recorded in the project communication record before end of day
- File updates go to the project system, not into email attachments
- Consultants have access to current architectural information through the project, not through periodic transmittal emails
- Client direction received through any channel gets documented in the project before it becomes actionable
The mechanism doesn't have to be elaborate. It has to be consistent.
A project where all participants know there's one place to find current information. And where decisions go when they're made: has most of its silo problem solved. Not all of it. But enough that the coordination failures that do occur are small, contained, and recoverable rather than large, distributed, and expensive.