The Great Lakes are often described as a collection of industrial cities surrounding inland seas. But that framing misses the deeper structure. The region is not defined by proximity to water — it is defined by movement through it.
Across five interconnected lake basins, cities developed not as isolated centres, but as functional nodes in a continuous system of shipping, manufacturing, and inland distribution. What emerges is not a hierarchy of cities, but a network governed by flow, constraint, and transition.
To understand the Great Lakes is to understand how geography forces interdependence.
A System of Basins, Not Borders
Unlike inland regions structured by roads or rail convergence, the Great Lakes operate as a set of linked water basins. Each basin shapes movement differently, creating distinct sub-systems within a larger whole.
Lake Superior: The Resource Export Spine
Lake Superior functions as the system’s upstream source region, where bulk commodities such as grain and raw materials enter the network for distribution south and east.
Duluth and Thunder Bay anchor this system, acting as parallel export gateways on either side of the U.S.–Canada border. Their role is defined less by consumption and more by outward flow.
Explore: Duluth Collection • Thunder Bay Collection
Lake Michigan: The Industrial Loop
Lake Michigan forms a dense industrial circulation zone linking Chicago, Milwaukee, and Detroit into a tightly integrated production and logistics system.
Unlike linear systems, this basin behaves like a loop, where goods, labour, and manufacturing inputs circulate between interconnected urban centres.
Explore: Chicago Collection • Milwaukee Collection • Detroit Collection
Lake Erie: The Transfer Corridor
Lake Erie operates as a directional transfer system, moving industrial output between inland manufacturing centres and eastern distribution networks.
Detroit, Cleveland, Toledo, and Buffalo form a sequential chain of industrial exchange points along this corridor.
Explore: Cleveland Collection • Buffalo Collection
Lake Ontario: The Transition Interface
Lake Ontario connects the inland Great Lakes system to the St. Lawrence Seaway, creating a transition zone between internal industrial flows and Atlantic-facing trade routes.
Toronto, Buffalo, Rochester, and Kingston sit within this interface layer, where lake-based systems begin to merge with global maritime networks.
Explore: Toronto Collection • Kingston Collection
The Chokepoints That Define the System
Unlike many regional systems defined by major hubs, the Great Lakes are defined by constraints — narrow passages and infrastructural bottlenecks that regulate flow.
Sault Ste. Marie: The System Gatekeeper
The locks at Sault Ste. Marie form one of the most critical control points in North American inland shipping, regulating movement between Lake Superior and the lower Great Lakes.
This is not a destination city, but a structural gate — without it, the upper lake system cannot connect to the broader industrial network.
Explore: Sault Ste. Marie Collection
Detroit–Windsor: A Mirrored Industrial System
Detroit and Windsor function as a single industrial ecosystem split by an international boundary. Automotive manufacturing, logistics, and supply chains operate as mirrored halves of the same system.
Explore: Detroit Collection • Windsor Collection
Buffalo: The Eastern Transition Node
Buffalo connects the Great Lakes system to the Atlantic via the Erie Canal and St. Lawrence Seaway corridors, acting as a critical interface between inland and oceanic trade systems.
Explore: Buffalo Collection
Industrial Circulation Across the Basin
The Great Lakes system is not static. It circulates. Industrial production, raw materials, and manufactured goods move continuously between lake-edge cities, inland rail systems, and cross-border logistics networks.
Chicago anchors much of this circulation, but does not control it in isolation. Detroit, Cleveland, and Milwaukee form parallel industrial nodes that distribute rather than centralize activity.
Explore: Chicago Collection • Cleveland Collection • Milwaukee Collection
From Water to Rail to Air
As rail networks expanded across the interior, they did not replace lake systems — they reinforced them. Cities that already functioned as port and industrial nodes became integrated into continental logistics networks.
Highways later intensified this same structure, and aviation compressed it further. Airports such as ORD, DTW, and YYZ now sit atop infrastructure patterns that predate flight itself.
Explore: ORD Collection • DTW Collection • YYZ Collection
The Great Lakes as a Constraint-Based System
What defines the Great Lakes is not hierarchy but constraint. Geography forces movement into specific channels, creating dependencies between cities that would otherwise operate independently.
Each basin, chokepoint, and transition node plays a role in regulating flow across the system.
This creates a region defined not by centralization, but by interconnection under physical limitation.
A Connected but Non-Hierarchical Region
Unlike inland systems dominated by a single convergence engine, the Great Lakes operate as a distributed network. Chicago, Detroit, Cleveland, Milwaukee, and Toronto each serve different functions within overlapping subsystems.
The result is a region that is highly connected, yet structurally decentralized.
Mapping Your Own Great Lakes Journey
While the Great Lakes can be understood as a system of interconnected basins, industrial corridors, and transport flows, most people experience it in a far more personal way: as a sequence of journeys.
A flight into Chicago, a drive through southern Ontario, a connection through Detroit, a rail line hugging Lake Erie, or a crossing into Buffalo are not abstract components of a system. They are repeating patterns in how people actually move through the region.
Over time, these routes begin to form a personal map of the Great Lakes — not defined by geography alone, but by familiarity, repetition, and connection. Certain airport codes, cities, and corridors begin to carry meaning beyond their location.
In this sense, the Great Lakes are not just a regional structure to be studied from above. They are a lived network of movement, where each journey adds another layer to an individual understanding of how the system fits together.
From Movement to Identity
Airports such as ORD, DTW, YYZ, and CLE become more than transit points. They act as compressed markers of experience — shorthand for entire routes, relationships, and repeated paths through the region.
A return to the same city is never identical. Each pass through the network reinforces familiarity with its underlying structure, turning infrastructure into memory and movement into identity.
Representing the System in Everyday Life
This is where design enters the picture. When a place becomes part of your personal geography, it often needs a way to be held, shared, or remembered outside of travel itself.
YHM Designs translates these layered travel systems into airport-code-based pieces that reflect the way people actually move through regions like the Great Lakes. Each design acts as a visual shorthand for a route, a connection, or a place that forms part of a larger personal network.
Rather than treating cities as isolated destinations, these pieces reflect the same idea this system is built on: that meaning comes from connection, repetition, and movement between points.
