--- title: "Decentralised governance" description: "A governance model in which separate parts of an organisation plan, create and publish their own content, with little central control." category: "Governance" canonical: "https://contentlexicon.com/decentralised-governance" updated: "2026-10-14" --- # Decentralised governance _Governance_ > A governance model in which separate parts of an organisation plan, create and publish their own content, with little central control. Decentralised governance spreads the authority to publish across an organisation. Departments, product teams, regional offices or local [branches](https://contentlexicon.com/branch) decide what content they need, produce it and manage it themselves. Some have content specialists of their own, such as a [content designer](https://contentlexicon.com/content-designer) in each product team or a [writer](https://contentlexicon.com/writer) in each department; in others the work falls to staff who publish alongside another job. Shared standards may exist on paper, but nobody has the authority or the time to apply them across the whole. It sits at the opposite end of the spectrum from [centralised governance](https://contentlexicon.com/centralised-governance), with [hub and spoke](https://contentlexicon.com/hub-and-spoke) in between. Few organisations choose it outright. More often it's where they end up as [websites](https://contentlexicon.com/website), intranets and channels multiply faster than anyone can coordinate them, and it's familiar in universities, federations of charities and companies that have grown through acquisitions. ## Why it matters for content Decentralisation keeps content close to the knowledge it depends on. The people who run a service or study a subject can publish when something changes, without waiting in another team's queue, and they often know their own audience better than a central team could. For organisations with very different products, markets or local communities, that autonomy can be the right choice. The costs build up across the estate rather than on any one page. [Voice](https://contentlexicon.com/voice) and quality drift apart, pages on the same topic contradict one another, navigation follows the organisation chart instead of what readers are looking for and nobody can say how much has been published or what's out of date. Mel Conway observed in 1968 that organisations produce systems that copy their own communication structures, and a decentralised website is a vivid example: a reader who wants to make a complaint first has to work out which department handles complaints. Embedded specialists face their own version of the problem. Without peers, review or a manager who understands their craft, they can end up defending standards alone, with no clear route to progress. Decentralisation works best when it's chosen deliberately and given some shared infrastructure: a common platform, a short set of standards, named owners and a community where publishers compare notes. At that point it starts to resemble hub and spoke, which is where many organisations move once the costs become visible. ## How AI changes the picture Good AI infrastructure can narrow the gap between well-resourced teams and stretched ones. A local team can draft, check [readability](https://contentlexicon.com/readability) and translate without calling on specialists it doesn't have, and shared guidance such as a [style guide](https://contentlexicon.com/style-guide) or [content principles](https://contentlexicon.com/content-principles) can be built into the tools each team uses, so standards travel with the work rather than sitting in a document few people open. AI can also give a decentralised organisation something it has usually lacked, which is a view of the whole. Comparing thousands of pages to find duplicates, contradictions and abandoned sections once needed a central team with months to spare. Language models can now produce a first pass much faster, for people to check. That doesn't settle who should fix what, but it makes the cost of sprawl harder to ignore. The same tools speed up the sprawl itself. When more teams can publish more material faster, duplication grows with the output, and chatbots or AI search drawing on that material may serve readers whichever version they find first. ## Questions people ask **Does decentralised mean ungoverned?** Not necessarily. Some decentralised organisations have clear owners, shared standards and regular reviews, and leave decisions about what to publish to the teams themselves. The trouble starts when decentralisation is a default rather than a decision, and nobody is responsible for the whole. **Who should embedded content specialists report to?** Reporting to a team they serve keeps them close to the work but can leave them without anyone who understands their craft. Some organisations keep the reporting line within a content or design discipline while placing people in product teams for long stretches. Either way, a community of practice helps prevent isolation. **How do you know decentralisation has gone too far?** Several pages answer the same question differently, readers and staff aren't sure which site is official, sections belong to people who left years ago and nobody can say how many pages exist. A [content audit](https://contentlexicon.com/content-audit) usually confirms the suspicion quickly. **Can a decentralised organisation have one voice?** It can share one, but it takes work: a clear style guide, examples people can borrow, training for occasional publishers and someone who reads a sample of what's published and talks to teams about it. Some variation in [tone](https://contentlexicon.com/tone) between, say, a research unit and a fundraising team is appropriate, provided the voice underneath stays recognisable. ## Learn more - [Organising structures for content teams: a guide](https://lapope.com/resource/organising-structures-for-content-teams-a-guide) – Lauren Pope's comparison of five structures, rated for control, scalability and agility, which separates decentralised teams of content professionals from federated models that devolve publishing to non-specialists. - [How Do Committees Invent?](https://www.melconway.com/research/committees.html) – Melvin Conway's 1968 paper, the origin of Conway's law; written about the design of systems such as software, its argument applies readily to websites built department by department. - [Managed-UX Integration: A Team Model for UX Autonomy and Product Alignment](https://www.nngroup.com/articles/managed-ux/) – Anna Kaley's proposal for embedding designers in product teams while they report to design leadership, aimed at the isolation and missing community common in decentralised models; written for UX, it transfers directly to content design. Related terms: [Author experience](https://contentlexicon.com/author-experience), [Centralised governance](https://contentlexicon.com/centralised-governance), [Content audit](https://contentlexicon.com/content-audit), [Content governance](https://contentlexicon.com/content-governance), [Content owner](https://contentlexicon.com/content-owner), [Content team](https://contentlexicon.com/content-team), [Hub and spoke](https://contentlexicon.com/hub-and-spoke), [ROT content](https://contentlexicon.com/rot-content), [Silo](https://contentlexicon.com/silo), [Single source of truth](https://contentlexicon.com/single-source-of-truth), [Style guide](https://contentlexicon.com/style-guide) Also called: Decentralised model; Distributed publishing; Dispersed model This page was last reviewed in October 2026.