What it means
The name comes from the tall sealed containers used to store grain, each holding its contents entirely separately from the next. Applied to a business, it describes functions that operate as self-contained units with very little information flowing between them.
The behaviour is rarely deliberate obstruction. It grows because incentives are set locally, so if sales is paid on bookings and finance is judged on collections, each team optimises its own number even when the combination damages the company.
The financial cost is real but scattered, which is why it goes unchallenged for years. It appears as duplicate software licences, rework caused by teams building on stale data, inventory held because nobody shared a forecast, and slow decisions that let competitors move first.
Finance teams often feel the effects earliest, because they are the ones consolidating everybody's numbers. When marketing, sales and operations each maintain their own version of revenue, the month-end close becomes a reconciliation exercise rather than an analysis one.
The fixes that work change measurement rather than simply encouraging collaboration. Shared metrics across functions, one agreed source for key numbers, cross-functional teams with a single budget, and leaders who visibly refuse to arbitrate turf disputes all achieve more than another away day.
One caution is worth adding: not every boundary is a silo. Specialist teams genuinely need focus and confidentiality in areas such as payroll, legal advice and unannounced transactions, so the target is unnecessary isolation rather than the removal of every departmental line.
In practice
Real-world examples
Example 1
A furniture manufacturer plans production from its own historic run rates because the sales team never shares its pipeline forecast. When a major retailer cancels a range, the factory is left with $340,000 of finished goods that have to be written down to clearance value, and both teams blame the other in the post-mortem.
Example 2
A hospital group lets each of its four sites run its own procurement, so the same surgical consumable is bought on three separate contracts at three different prices. Consolidating onto one national agreement cuts the unit cost by 18% and, more importantly, gives clinicians a single specification to work to.
Example 3
A software company logs customer complaints in the support system while engineering tracks defects in a separate tool, and nobody reconciles the two. A recurring integration failure is reported eleven times over four months without ever reaching a developer, and a customer worth $90,000 a year leaves at renewal.
Think of it
Imagine a rowing boat where each rower faces a different direction and pulls whenever they feel like it, rather than listening to the coxswain and working as a unified crew.
Case study
Seen in the real world
The following is an illustrative and entirely fictional example. Ravensmere Group, an invented professional services firm of 340 staff across four divisions, had grown by acquisition and let each division keep its own systems, targets and reporting. Nobody described the culture as difficult, because the divisions were polite to one another and simply did not interact.
The costs surfaced when a new chief operating officer asked three plain questions. Three divisions were paying separately for customer relationship systems at $52,000, $38,000 and $31,000 a year, a total of $121,000, where a single enterprise agreement would cost $74,000 and save $47,000. The month-end close was taking fourteen working days because each division defined revenue differently and the group team had to reconcile by hand. Worst of all, two divisions had bid against each other for the same client, discounting until the client paid $180,000 for work either would have priced at $240,000.
The remedy was mostly about measurement. The group adopted one revenue definition and one system, moved 20% of each division head's bonus onto group-level results, and required any bid above $100,000 to be logged centrally before it went out. Within two quarters the close had shortened to six working days, the licence saving was banked, and the fictional firm had stopped competing with itself, though the finance director was careful to say the culture had shifted rather than been fixed.
Watch out
Common mistakes
- Treating silo mentality as a people problem and running team-building events, when the incentives and reporting lines that created it are left untouched.
- Assuming a shared software system automatically breaks down silos, when teams simply keep their real numbers in private spreadsheets alongside it.
- Overcorrecting by putting every decision through a cross-functional committee, which replaces isolation with paralysis.
Questions
People also ask
What is the clearest early warning sign?
Two teams presenting different figures for the same measure in the same meeting, which shows there is no agreed source of truth.
Do silos only appear in large organisations?
No, they can form in a company of thirty people once functions have separate managers and separate targets, and they are easier to fix at that size.
Who is responsible for breaking down silos?
Senior leadership, because only they can change how departments are measured, budgeted and rewarded, which is where the behaviour actually comes from.