The Portage That Built a City

In December 1674, Father Jacques Marquette, a French Jesuit missionary, built a small cabin at the mouth of the Chicago River where it meets Lake Michigan. The site was unremarkable -- swampy, prone to flooding. But it was a portage, where canoes could be carried over a short stretch of land connecting the Great Lakes to the Mississippi via the Des Plaines and Illinois Rivers. Chicago was a hinge between two massive water systems. Geography made it inevitable.

Marquette didn't found a city. He built a mission. The name "Chicago" likely derives from a Miami-Illinois word, shikaakwa, referring to wild onions. He recognized what Native traders had known for generations: this was a node in a network. His settlement didn't survive. He died in 1675. But the strategic value remained.

In 1803, the U.S. Army built Fort Dearborn at the same location. The Illinois and Michigan Canal, completed in 1848, formalized the portage route. Railroads amplified the advantage. By the 1850s, Chicago was the hub of the nation's rail network. The Chicago Board of Trade turned commodities into financial instruments. Chicago became a marketplace, a logistics engine designed around flow.

the chicago river, key to the city's founding as a portage route. source: wikimedia commons

Cities form at connection points. Chicago exists because it connected two systems that otherwise didn't touch. The portage was a bottleneck, and bottlenecks create value. Today it's the third-largest U.S. city. O'Hare is a modern portage: a node where routes converge. Marquette's mission lasted months. The city it seeded has lasted centuries. The portage is paved over, but its logic remains.