Content Lexicon.

Silo

In one line

A team, system or channel that keeps its content to itself, so the same content gets made twice, disagrees with itself and can’t be found.

Comms has press releases, research has PDF reports, product has a help centre and none of them knows what the others have published. Each part may work reasonably well alone while the whole content estate becomes repetitive and contradictory.

Silos are almost never created by villainy. Organisations divide work so people can specialise and manage complexity. Trouble starts when a boundary means the help centre team never hears that comms has changed the eligibility rules.

Why it matters for content

Content crosses departmental lines. A service description may appear on a website, in emails, scripts, PDFs and chatbot answers. If each channel has its own source and owner, facts drift. The same change is made several times, or not made at all.

Silos also hide the true scale of content. No team can govern what it can’t see. A shared spreadsheet of every page and who owns it, an agreed word list and one style guide give people enough connection to find related work and make joined-up decisions, without abolishing every useful boundary.

Breaking silos isn’t a case for centralising all writing. Teams can keep their expertise and autonomy while agreeing where canonical information lives, who owns it and how changes travel.

How AI changes the picture

AI assistants can search across collections and make siloed information feel connected. That’s useful, but retrieval doesn’t resolve disagreement. If three teams maintain different policies, an assistant may select one, blend them or present the contradiction with unwarranted confidence.

So each policy needs a named owner and one canonical version more than before. AI can help find duplicates, map relationships and flag conflicts, but people must decide which source is authoritative and repair the process that allowed divergence.

Silos also form around AI projects themselves. Prompts, evaluations and knowledge sources may sit with technical teams while content specialists remain outside. Joined-up work is essential because system behaviour depends on both technology and content.

Questions people ask

Are silos always bad?

Not always. Specialisation is useful, and boundaries help teams focus and protect sensitive information. The problem is a boundary that stops teams coordinating, finding each other’s work or knowing who’s accountable.

Does a single CMS remove silos?

Not by itself. One platform can contain many disconnected practices and duplicate sources. Governance and relationships matter as much as storage.

Should one team own all content?

Usually not. A central content function can set standards and join things up, while the teams with subject knowledge stay responsible for the accuracy of their own pages.

Can AI unify siloed content?

It can make information easier to retrieve, but it can’t decide which conflicting version is true. That remains an organisational responsibility.

Learn more

Type a term, or a word from its definition.⌘K opens this from any page.