Hub and Spoke Model

A network architecture where all connections pass through a central hub—used in airline routing (connecting flights through hubs), organizational structure (all decisions through a central authority), and information systems (all data through a central server). Hub-and-spoke is efficient for coordination and control: the hub sees everything, standardizes processes, and eliminates redundant connections. But it creates a single point of failure: when the hub goes down, the entire network collapses. It also creates bottlenecks: everything must wait for hub capacity.

When to use it

When evaluating organizational bottlenecks (is everything routing through one person or team?); when system resilience matters and single points of failure are unacceptable; when designing team structures and deciding between centralized and distributed authority; when a key person's absence paralyzes operations.

How it can help

Evaluate whether your organization, communication, or system architecture is hub-and-spoke, and whether that's optimal. Hub-and-spoke is ideal when: coordination and consistency are more important than speed, the hub has capacity to handle all traffic, and the cost of hub failure is manageable. It's dangerous when: speed matters more than consistency, the hub becomes a bottleneck, or hub failure would be catastrophic. The alternative—distributed or mesh networks—trades coordination efficiency for resilience and speed. Most organizations need hybrid architectures.