Block - From Hierarchy to Intelligence
Block logo
Author<br>Jack Dorsey and Roelof Botha
Tags<br>Technology, AI, Purpose, Block
Author<br>Jack Dorsey and Roelof Botha
Tags<br>Technology, AI, Purpose, Block
At Sequoia, we see that speed is the best predictor of start-up success. Most companies are focused on AI as a productivity enhancer. Few are focused on the potential of AI to change how we work together. Block is showing what it looks like to fundamentally rethink organization design, ultimately harnessing AI to increase speed as a compounding competitive advantage.<br>Two thousand years before the first corporate org chart, the Roman Army solved a problem that every large organization still faces: how do you coordinate thousands of people across vast distances with limited communication?<br>Their answer was a nested hierarchy with a consistent span of control at every level. The smallest unit was the contubernium, eight soldiers who shared a tent, equipment, and a mule, led by a decanus. Ten contubernia formed a century of eighty men under a centurion. Six centuries made a cohort. Ten cohorts made a legion of roughly 5,000. At each layer, a named commander held defined authority, aggregated information from below, and relayed decisions from above. The structure (8 → 80 → 480 → 5,000) was an information routing protocol built around a simple human limitation: a leader can effectively manage somewhere between three and eight people. The Romans discovered this through centuries of warfare. Even today, the US Army's hierarchical chain follows a similar pattern. We now call it "span of control," and it remains the governing constraint of every large organization on earth.<br>The next big change came from Prussia. After Napoleon's army destroyed the Prussian forces at the Battle of Jena in 1806, a group of reformers led by Scharnhorst and Gneisenau rebuilt the military around an uncomfortable truth: you cannot depend on individual genius at the top. You need a system. They created the General Staff, a dedicated class of trained officers whose job was not to fight but to plan operations, process information, and coordinate across units. Scharnhorst intended these staff officers to "support incompetent Generals, providing the talents that might otherwise be wanting among leaders and commanders." This was middle management before the term existed. Professionals whose purpose was to route information, pre-compute decisions, and maintain alignment across a complex organization. The military also formalized the distinction between "line" and "staff" functions. Line advances the core mission. Staff provides specialized support. Every corporation still uses this vocabulary today.<br>Military hierarchy entered the business world through the American railroads in the 1840s and 1850s. The U.S. Army lent West Point-trained engineers to private railroad companies, and these officers brought military organizational thinking with them. Staff and line hierarchies, divisional structure, bureaucratic systems of reporting and control: all of it was developed in the military before the railroads adopted it. In the mid-1850s, Daniel McCallum of the New York and Erie Railroad created the world's first organizational chart to manage a system stretching over 500 miles with thousands of workers. The informal management styles that worked for smaller railroads were failing. Train collisions were killing people. McCallum's chart formalized the same hierarchical logic the Romans had used: layers of authority, defined reporting lines, structured information flow. It became the blueprint for the modern corporation.<br>Frederick Taylor (1856-1915), often called the "Father of Scientific Management," optimized what happened within that hierarchy. Taylor broke work into specialized tasks, assigned them to trained experts, and managed through measurement rather than intuition. This produced the functional pyramid organization - a structure optimized for efficiency within the information routing system that the military had pioneered and the railroads had commercialized.<br>The first real stress test of functional hierarchy came during World War II. The Manhattan Project required physicists, chemists, engineers, metallurgists, and military officers to work across disciplinary boundaries toward a single objective under extreme secrecy and time pressure. Robert Oppenheimer organized Los Alamos into functional divisions but insisted on open collaboration across them, resisting the military's instinct to compartmentalize. When the implosion problem became critical in 1944, he reorganized the lab around it, creating cross-functional teams unlike anything in corporate America at the time. It worked, but it was a wartime exception led by a singular figure. The question the postwar business world faced was whether that kind of cross-functional coordination could be made routine.<br>With the growth and globalization of companies after World War II, the scale limitations of...