Content Lexicon.

Hub and spoke

In one line

A federated governance model in which a central content team sets shared standards while local teams create and manage content.

Hub and spoke describes how many organisations divide content work: a small central team, the hub, supports and sets standards for the many teams across the organisation, the spokes, that publish in their own areas. It sits between centralised governance, where one team controls most publishing, and decentralised governance, where each part of the organisation decides for itself. Most large organisations end up working this way whether or not they use the name, and much of their governance pain lives in the joins.

The hub usually provides standards and a style guide, training, the publishing platform and templates, shared components, specialist help with research, accessibility and search, and sign-off for high-risk content. The spokes own the subject knowledge: planning content for their area, drafting it, keeping it accurate and retiring it when it’s no longer needed. The name comes from transport networks, where routes radiate from a central hub.

Why it matters for content

The model keeps local knowledge and speed while giving the organisation enough common practice to behave like one organisation. Distributed publishing happens anyway. The communications team owns the homepage, service teams own guidance, human resources owns internal policy and enthusiastic colleagues own several pages everyone has forgotten. The governance problem is distribution without an agreement.

The usual failures come from one side doing too much or too little. A hub that reviews everything becomes a bottleneck, and spokes find ways round it, publishing in shared drives or on social channels instead. A hub that only issues rules becomes a distant authority whose standards nobody follows. Spokes without training or time drift apart in quality, tone and structure, producing duplicated pages and abandoned sections.

The model works when both sides have defined duties, the hub is funded to support rather than police, and spoke roles are part of people’s jobs rather than an extra on top.

How AI changes the picture

AI can strengthen the model by making shared guidance easier to apply. A central team might provide approved tools, prompt patterns, quality checks and source collections while local teams use them for their own content.

It can also magnify inconsistency. If every department builds an assistant from different copies of policy and guidance, users receive different organisational truths. Federated AI needs common standards for sources, ownership, evaluation and escalation, with room for local subject knowledge.

Questions people ask

Is hub and spoke the same as a hybrid model?

Often, yes. Nielsen Norman Group’s hybrid model, where a central team controls top-level pages and distributed editors publish within its guidelines, is one version of hub and spoke under another name.

When does a spoke need its own content specialist?

When it publishes enough, or carries enough risk, that occasional contributors can’t keep up. Many organisations place trained content designers in the largest spokes and leave smaller ones with part-time editors supported by the hub.

Is hub and spoke cheaper than a central team?

Not automatically. It distributes work but still requires investment in training, support and oversight. Unfunded spokes tend to produce abandoned pages.

How do you know it’s working?

Look for consistent quality, clear ownership, fewer duplicated pages and faster decisions. Also ask the spokes whether the hub helps them publish well or mostly sends them documents.

Learn more

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