Silo · Departmental Barriers
Organizational Silo
What is a silo?
- When departments are locked into their own information and goals and collaboration breaks down
- Separate KPIs, systems, and cultures build the walls
- Cutting doors through shared goals, cross-functional teams, and leadership
The moment you call a silo 'departmental selfishness,' the fix becomes a pep talk. See it as a structural problem instead, and the places to intervene become concrete. A silo is the result of design, not of people's attitudes. Each team simply acted rationally within the metrics and information it was given, yet those rationalities add up to a loss for the company as a whole. Once you apply the concept properly, the questions in the meeting room change. Instead of 'why won't that team cooperate?', you ask 'how is our company designed so that someone loses when they cooperate?'
In practice, silos usually show up in three layers. The first is the information silo: the same customer’s history sits separately in the sales CRM and in customer service records, so the two departments give the customer different answers. The second is the goal silo: production chases utilization while sales chases closed-won revenue, so the same fight repeats every time a small urgent order comes in. The third is the relationship silo: after the first two build up for years, the assumption that “that team just can’t be reasoned with” has hardened. Information and goals can be fixed in six months, but a relationship silo takes years to recover. Note that division of labor and specialization are not silos in themselves. The test is not whether boundaries exist, but whether there are passages across them.
The most common misconception is that a reorganization settles it. Merge two teams under one division, and if the evaluation form stays the same, all that changes is the seating chart in the meeting room. Demanding collaboration while leaving evaluation and rewards at the department level is where practice most often goes wrong. If the only message sent down is 'collaborate company-wide,' people go through the motions of collaborating while spending real headcount and time on their own metrics. The opposite failure exists too. If, in the name of breaking down walls, you open all information to everyone and set up ten task forces, then even with three meetings a week nothing gets decided, and all you widen is a gray zone where no one takes final accountability.
Seungbin JeonAn instructor who draws on psychology expertise to support communication and leadership growth in organizations
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum Consulting“Silo” is a metaphor drawn from the cylindrical structures that store grain or missiles in isolation, and it has come into wide use in management to describe disconnection between departments. It is seen as a problem that arises naturally as organizations grow and work is divided more finely, and it is used alongside the term “silo mentality.”
Consider a hypothetical case: Company A, an industrial goods manufacturer with 480 employees and annual revenue of KRW 180 billion (≈ US$134,670,100). Marketing collected an average of 310 leads a month from trade shows and online, but sales contacted only 38% of them. The rest sat untouched in the CRM for six months. Both sides said, “We’ve done our part.”
- When the head of sales planning traced back 300 neglected leads, 62% had never even been assigned an owner. The head of Sales Team 2 put it bluntly: “Taking a scrap of a business card and cold-calling is just a waste of time.”
- Chaired by the CEO, six marketing and sales staff worked together for two weeks to agree on a “qualified lead” standard with five criteria, including budget, timing, and decision-making authority. They also drew a clear line: marketing would nurture any lead that fell short.
- They tied 30% of both teams' individual evaluations to a shared metric, 'qualified consultations,' so that handing off and receiving leads directly affected each other's scores.
- Every Tuesday for 30 minutes, the two team heads reviewed the previous week’s lead handling together on a single CRM screen. By month three, staff had started bringing agenda items to the meeting on their own.
- Six months later, lead contact rate rose from 38% to 81%, and the average time from first meeting to closed deal fell from 6.2 weeks to 4.1 weeks. New-customer revenue was up 19% year over year.