The basic picture
A hub and spoke structure has a central hub connected to several spokes. The hub holds shared resources, expertise or processing. The spokes are the local units, sites or teams that deal directly with customers, products or day-to-day work, and they connect to the hub rather than to each other.
The name comes from transport, where a hub handles routing between many endpoints. In business it describes an arrangement where common work is concentrated in one place while front-line work stays distributed. The hub and spoke structure is one of the common forms of a hybrid design, sitting between full centralization and full independence.
What typically sits in the hub
The hub usually holds activities where concentration brings clear benefits:
- Shared platforms. Core systems, data stores and tooling used by all spokes.
- Specialist expertise. Skills that are scarce or expensive to duplicate, such as legal, analytics or security specialists.
- Standard-setting. Common policies, templates and reference definitions.
- Transaction processing. Routine, high-volume work such as payments or record keeping, which resembles a shared services model.
- Purchasing and supplier relationships. Negotiating once on behalf of many units, as in centralized procurement.
- Oversight and reporting. Gathering information from the spokes into combined views.
What stays with the spokes
Spokes usually keep the activities that depend on local knowledge or speed:
- Customer-facing work. Sales, service and relationships.
- Local operations. Scheduling, staffing and day-to-day running.
- Local adaptation. Tailoring offers or processes to the market.
- Immediate decisions. Calls that cannot wait for a central answer.
- Feedback to the hub. Reporting what works and what does not.
The line between the two is a design choice, not a rule. Different organizations place the same activity in different places, and the line often moves over time.
An illustration
Imagine a retailer with several stores. The hub might run the product catalog, payroll, central purchasing and the shared stock system. Each store, as a spoke, runs its own floor, serves customers and manages its staff rota. Stores order through the hub and report sales back to it. This is an illustration only; real arrangements vary widely.
Strengths
- Shared effort. Common work is done once rather than repeated at each spoke.
- Consistent core. Spokes work from the same data and standards, which supports combined reporting.
- Local flexibility. Spokes keep control of customer-facing choices.
- Easier growth. Adding a spoke can mean connecting to an existing hub rather than building everything again, though the hub has to be able to cope with the extra load.
- Clear routes. Spokes know where to go for help or approval.
Weaknesses
- Dependence on the hub. If the hub fails or slows down, every spoke feels it. This is the classic single points of failure issue, and it deserves deliberate planning for backup and recovery.
- Hub bottlenecks. When many spokes queue for the same central team, delays follow, particularly during peak periods.
- Weak links between spokes. Because communication passes through the hub, spokes may not learn from one another.
- Distance. A hub that loses touch with local reality can set poor standards or prioritize its own convenience.
- Capacity pressure. The hub must keep up as spokes grow in number or demand.
Making the arrangement work
Several practices help.
- Define the interface. State clearly what the hub provides and what spokes must supply in return. Internal service levels are one way to set expectations on both sides.
- Listen to the spokes. A regular route for feedback keeps hub priorities tied to real needs. Measuring how satisfied spokes are with hub services is a useful signal, much as internal customer feedback does elsewhere.
- Plan for hub failure. Consider what each spoke can still do if the hub is unavailable, and keep essential tasks possible locally for a limited time where it makes sense.
- Allow lateral connection. Let spokes talk to each other directly where it helps, rather than routing everything through the hub.
- Watch the workload. Review hub capacity as the number or size of spokes changes.
When it fits
Hub and spoke tends to suit organizations with many similar units, such as branches, sites or regional offices, where there is a clear body of shared work and a clear body of local work. It fits less well where the units are very different from one another, since a hub designed for common needs may serve none of them well, or where nearly all work is local and the hub would have little to do.
It also suits a gradual approach. An organization can begin by placing one or two functions in a hub and see how the spokes respond before moving more, rather than committing to a full design in advance.
As elsewhere in operating model design, the arrangement is a trade-off. Concentrating work in a hub can bring efficiency and consistency, but it also concentrates dependency, and the benefits depend heavily on how well the hub is run.