Chapter 1The Map Maker

Foreword

The one number that matters most in the life of a company never appears on its balance sheet. It is the attention of the person running it — a quantity that cannot be raised, borrowed, or issued as stock, that arrives fixed and depletes on a schedule no board can amend. A chief executive has a certain amount of it and no more. The whole apparatus of modern corporate governance, the committees and the succession plans and the activist investors who show up the moment the numbers slip, exists to make sure that finite thing is pointed at the company that is paying for it.

Jack Dorsey pointed his at two.

For six years he was the chief executive of two publicly traded companies at once — Twitter and Square, two institutions, two boards, two sets of shareholders who had each been told, in effect, that they owned half of one man's working mind. No one had really done this before, not at that scale, not with that much public money watching. When an activist hedge fund finally did the arithmetic out loud in 2020 and moved to remove him, the surprising thing was not that they tried. The surprising thing was that he survived it, and went back to running both.

I cover the founders and the fraudsters and the venture men of the late technology industry, mostly from a desk in Atlanta, and the people I write about tend to fail in a familiar way: they want too much of one thing, and the wanting eats them. Dorsey was a different problem. He did not want too much of one thing. He wanted two whole things at once, gave each of them exactly half of himself, and the interesting part — the part that made me want three years of his company — is that he mostly got away with it.

I expected the split to be the scandal. I expected to write the story of a distracted man, a cautionary tale about the vanity of a founder who thinks he is large enough to hold two empires and neglects both. That is not the book I found. What I found instead was a man for whom the two companies were never two companies. A tool for broadcasting short messages through a network in real time, and a tool for moving small payments through a network in real time, were, to him, the same tool answering the same question — the one he had been asking since he was a boy in south St. Louis listening to a police scanner: how do you move something through a city the instant it happens? The divided attention was a story the market told about him. It was not the story he was living.

The record I worked from is the ordinary record of a public life: the earnings calls and the shareholder letters, the memoirs and the interviews of the people around him, the court filings and the years of press that accumulate around anyone who governs a piece of the public conversation. It is a strange record to build a life from, because its subject is one of the least forthcoming men ever to run a communication company. He built the loudest instrument of the century and used it, on his own behalf, to say almost nothing. The biographer of a talker drowns in material. The biographer of Dorsey works the way his father worked over the mass spectrometers — measuring the traces a hidden system leaves behind, inferring the shape of the thing from the marks it makes on everything around it.

And there was the other pattern, the one that surfaced every time I thought I had him fixed. This was a man who kept renouncing. He gave up a board seat, then another. He gave up the beard and the tie. He gave up the name Twitter, or watched it given up, and in the end gave up the company itself. He fasted and walked and sat in silence and surrendered, day after day, the ordinary comforts a man of his means could have bought without noticing the cost. He was as defined by what he walked out of as by what he built, and a life organized around subtraction is much harder to write than a life organized around accumulation.

That difficulty is why he is worth a book. Not the money, though there was a great deal of it, and not the platform, though it changed how the species argues with itself. He is worth a book because he does not come apart cleanly along any of the seams the rest of us use to sort people — builder and quitter, believer and cynic, the man of the crowd and the man of the cell. I came to explain a divided executive. I stayed because I stopped believing he was divided at all.

— Sterling Aldridge, Atlanta

Chapter 1 · The Map Maker

The house on Flora Place sat in the Holly Hills neighborhood of south St. Louis, a brick bungalow on a street of brick bungalows, in a city made almost entirely of brick because the Great Fire of 1849 had burned the wood and the city had decided, collectively and permanently, never to burn again. It was 1982, and Jack Patrick Dorsey was six years old, and he was drawing maps.

Not the maps a typical six-year-old draws, crude representations of the house, the yard, the route to school. Jack's maps were attempts at precision. He drew the streets of his neighborhood with something approaching correct proportionality. He marked intersections. He noted which streets were one-way. He drew the routes that buses took, tracing them with a finger on the actual city map his father kept in the glove compartment of the family car before reproducing them, from memory, on sheets of paper that accumulated in stacks on his bedroom floor.

His father, Tim Dorsey, was an engineer who worked on mass spectrometers, instruments that identify the chemical composition of substances by measuring the mass-to-charge ratio of their ions. It is a profession that requires patience with invisible systems, the ability to think about things you cannot see by measuring the traces they leave behind. Tim was methodical, quiet, technically precise. He recognized something in his son's map-making that was not a child's game. The boy was trying to understand how the city worked. Not what the city looked like, but how it functioned, how people and vehicles moved through it, what determined their routes, where the bottlenecks were, what happened when a street was closed or a bus was late. The maps were not representations. They were models.

His mother, Marcia Dorsey, was a homemaker who later worked in a coffee shop, a detail that acquires a certain resonance given that her son would, decades later, require his employees to work shifts behind a retail coffee counter as a form of corporate discipline. Marcia was warm, practical, and patient with a boy whose interests were intense but unusual. She did not tell him to go outside and play. She bought him more paper.

Jack was the eldest of three brothers, and his position in the birth order mattered in the way that birth order always matters in families where the eldest child is markedly different from the norm. He set the terms. He organized the games. But the games he organized were not the games other children played. He did not want to play baseball or ride bikes or build forts. He wanted to build systems. He wanted to create rules that governed how things moved, and then watch the rules operate. His brothers, Andrew and Daniel, participated with the tolerance of younger siblings who understood that Jack's enthusiasms were not optional.

The family was Catholic, practicing, though not zealously. They attended mass. They observed the sacraments. The Catholicism mattered later, in ways that are easy to dismiss as affectation but that the biographical record suggests were genuine. Dorsey's adult interest in meditation, fasting, silence, and radical simplicity has obvious monastic antecedents, and friends who knew him well have noted that the spiritual practices he adopted in his thirties and forties were not borrowed from Silicon Valley wellness culture but were extensions of something he had grown up with: the idea that discipline imposed on the body could clarify the mind, that silence could be a form of prayer, that simplicity was not a lifestyle choice but a moral commitment.

But all of that was decades away. In 1982, in Holly Hills, Jack Dorsey was a boy with maps.

St. Louis in the early 1980s was a city in the particular condition that Midwestern cities occupied during that era: declining but not yet collapsed, proud but aware that the pride was increasingly historical, still functioning but with visible evidence that the functions were degrading. The population was falling since the 1950 census, when the city proper held over 856,000 people. By 1980, it was under 453,000. The exodus to the suburbs, accelerated by white flight, deindustrialization, and the peculiar legal structure that made St. Louis an independent city rather than part of St. Louis County, had hollowed out neighborhoods that were dense and prosperous within living memory.

Jack grew up in a neighborhood that was holding on. Holly Hills was working-class and lower-middle-class, stable enough that houses were maintained and children walked to school, unstable enough that the trajectory was legible to anyone paying attention. The boy who drew maps was drawing a city that was in the process of being unmapped, losing the density, the transit routes, the commercial corridors that made a city a system rather than a collection of structures.

This mattered. A child who grows up in a thriving city takes systems for granted. A child who grows up in a declining city, where bus routes are cut, where stores close, where streets that were once busy become quiet, develops an awareness of systems that is rooted not in how they work but in how they fail. Jack Dorsey spent his adult life building systems, for communication, for payment, for the movement of information and money, and his approach to system design would always carry the imprint of a person who had watched systems degrade. His systems were designed not with the confidence of someone who assumed infrastructure held but with the wariness of someone who had seen infrastructure crumble.

Tim Dorsey commuted to work and came home and did not talk much about the mass spectrometers. He was the kind of engineer who kept his professional life and his home life in separate compartments, a trait his oldest son did not inherit. Jack became a person for whom the boundary between work and identity was nonexistent, for whom the company was the self and the self was the company, to a degree that made people who worked with him uncomfortable. But Tim gave his son something more important than conversation about work. He gave him the engineering instinct, the belief that problems had solutions, that solutions could be designed, and that the designed solution, if properly implemented, worked.

Marcia gave him something else. She gave him attention. In a household with three boys and the ordinary chaos of a working-class family, she noticed what Jack was interested in and did not dismiss it. When he asked for a police scanner, an unusual request for a child, but Jack had become fascinated with the radio dispatches that coordinated emergency services across the city, she found one. When he sat in his room listening to the scanner, mapping the locations of police and ambulance calls, she did not intervene. She let him be strange.

The police scanner was the second revelation. The maps had shown him how the city was organized in space. The scanner showed him how the city was organized in time, how events happened in sequence, how dispatchers coordinated responses, how the system of emergency communication worked as a real-time network of human beings making decisions under pressure. He listened for hours. He tracked the calls. He plotted them on his maps. He was eight years old, and he was building a real-time dispatch model of St. Louis.

The obsession with dispatch, with the real-time coordination of people and vehicles across a city, was not a phase. It persisted through his childhood and into his adolescence, and it became the direct ancestor of both Twitter and Square. The connection is not metaphorical. It is architectural.

A dispatch system takes a piece of information, a location, a status, a request, and broadcasts it to everyone who needs to know. It is short. It is immediate. It is stripped of everything except the essential data. A police dispatcher does not tell stories. A dispatcher says: Unit 4, respond to 3400 South Grand, assault in progress. The format is compressed. The information is actionable. The broadcast is indiscriminate, everyone on the channel hears it, and each person decides, based on their own position and capacity, whether to respond.

Twitter, when Dorsey conceived it twenty years later, was a dispatch system. A tweet was a dispatch: short, immediate, broadcast to everyone who was listening, stripped of context, designed to convey a status or a location or an event. The 140-character limit was not an arbitrary constraint. It was the natural length of a dispatch message, derived from the SMS protocol, which was itself derived from the paging systems that were themselves descendants of radio dispatch. The entire architecture of Twitter, the brevity, the broadcast model, the real-time feed, the asymmetric following structure that let anyone listen to anyone, was the architecture of the dispatch systems Jack Dorsey was listening to on his police scanner since he was eight.

Square was also a dispatch system, though the connection is less obvious. A payment is a dispatch: a piece of information, an amount, a sender, a recipient, broadcast through a network and resolved in real time. The Square reader, the small white device that plugged into a phone's headphone jack and turned any phone into a point-of-sale terminal, was a dispatch terminal. It took the payment information and sent it through the network. The merchant did not need to understand the network. The merchant needed the terminal to work.

Both companies were, at their core, answers to the same question that had obsessed Jack Dorsey since he was a boy in Holly Hills listening to his police scanner: How do you build a system that moves information through a city in real time?

He did not know this yet. He was eight, and he was drawing maps and listening to dispatches, and the future was twenty years away. But the instinct was already formed. The boy who built Twitter was the boy who listened to the scanner. The boy who built Square was the boy who drew the maps. The obsessions did not change. They scaled.

The police scanner episode is more significant biographically than even its most attentive commentators have appreciated. The scanner was not a toy. It was a professional-grade receiver that monitored the radio frequencies used by police, fire, and emergency medical services for coordination. In the early 1980s, before digital encryption made scanner monitoring less informative, the frequencies carried the raw operational chatter of a city's emergency infrastructure: location reports, status updates, resource requests, medical codes, the compressed, jargon-heavy communication of professionals dispatching other professionals under time pressure. Jack was eight years old when he began listening, and he was listening not for the drama of crime and emergency but for the system. He was mapping which frequencies corresponded to which districts, learning the codes that translated into actions, understanding how a city's emergency infrastructure coordinated across geography and time.

The specificity is important because it distinguishes what Dorsey was doing from what most children who owned police scanners were doing. The ordinary eight-year-old with a police scanner was waiting for the exciting call, the robbery, the high-speed chase, the fire. Dorsey was tracking the pattern, the density of calls by district, the response times, the coordination between units, the information architecture that turned individual dispatches into collective action. He drew the maps not to memorize streets but to visualize the system in space: which neighborhoods generated more calls, which intersections were bottlenecks, which routes the ambulances preferred and why. The maps were a form of systems analysis performed by a child who did not yet have the vocabulary to describe what he was doing.

There was one more thing about young Jack that shaped everything that followed. He stuttered. He was known as a quiet student not because he had nothing to say but because speaking was a minefield. The words tangled in his mouth. Sentences that moved freely in his mind came out broken, halting, incomplete. But he was determined to overcome it, and he did — through oratory competitions, of all things, forcing himself into the exact situation his stutter made most terrifying. He competed in oratory until he could speak without stuttering. The discipline required to overcome a speech impediment through sheer repetitive exposure to public speaking is the same discipline he would later apply to fasting, to ice baths, to the extreme wellness routines that made him a figure of fascination and mockery in equal measure. The pattern was established early: identify the weakness, attack it directly, master it through repetition.

At Bishop DuBourg High School, a Catholic institution on the south side of St. Louis where the tuition was modest and the discipline was not, Jack Dorsey was a difficult student to categorize. He was not a troublemaker. He was not a class clown. He was not antisocial. He was something more unsettling to the teachers who encountered him: he was a student who was clearly intelligent but whose intelligence did not map onto the available categories of academic achievement.

He was interested in computers. This was the early 1990s, and computers in a south St. Louis Catholic high school were not yet the universal educational tools they became. There was a computer lab. There were classes. But the classes taught the basics, word processing, spreadsheet software, the rudimentary skills that the educational establishment of that era believed constituted computer literacy. Jack was already past this. He had been programming since he was a child, teaching himself from manuals and from the nascent internet, and the gap between what he knew and what the school could teach him was wide enough to create a particular kind of adolescent frustration, the frustration of a person who can see the future but is stuck in an institution designed to prepare students for the past.

He found his own way. He became interested in dispatch software professionally, not just as a listener but as a builder. While still in high school, he began writing code for dispatch systems, creating software that could route couriers and delivery vehicles. This was not a school project. This was a business. He had identified a real problem, the coordination of moving vehicles in real time, and was building a real solution, using skills he had taught himself, at an age when most of his classmates were thinking about prom.

The dispatch software brought him to the attention of people outside his high school world. By the time he was a teenager, he was communicating with professional software developers, participating in early internet forums, and building a reputation in the small community of people who worked on real-time messaging and dispatch systems. He was not a prodigy in the conventional sense, he was not winning science fairs or acing standardized tests. He was a prodigy in the precise sense that he had identified his problem early and was working on it, obsessively, since childhood.

His parents watched this with the particular mixture of pride and bewilderment that characterizes parents whose children have surpassed them in a domain the parents do not fully understand. Tim Dorsey knew engineering. He understood that his son was building something. But the nature of what Jack was building, real-time dispatch software, messaging protocols, the coordination of movement through networked systems, was outside Tim's professional experience. He supported it the way he supported everything his sons did: quietly, practically, without drama.

Marcia was more vocal in her support, and more vocal in her concern. She saw a teenager who was spending too many hours in his room, staring at a screen, communicating with people she had never met through channels she did not understand. The internet in the early 1990s was not yet the ubiquitous presence it became, and for a parent in south St. Louis, the idea that her teenage son was spending his evenings in conversation with strangers on the other side of the country was not reassuring. But she had established the pattern early, she let him be strange, and she did not reverse it now.

The first real rupture in Jack Dorsey's life was not a crisis. It was a departure. After graduating from Bishop DuBourg in 1995, he enrolled at the Missouri University of Science and Technology in Rolla, a school known for engineering, located in the Ozarks, about a hundred miles southwest of St. Louis. It was a logical choice for a boy from a working-class Catholic family in south St. Louis: affordable, practical, close to home, focused on the technical skills that were obviously going to define his career.

He lasted two years. The problem was not academic failure. The problem was that Rolla was not where the future was happening. Dorsey had been building dispatch software, communicating with developers in New York and San Francisco, and thinking about problems that were being solved, or at least attempted, in places that were not the Missouri Ozarks. The internet was exploding. The web was being built. The companies that would define the digital era were being founded in garages and dorm rooms and rented offices in cities that vibrated with the energy of people building new things. Rolla was a fine school. It was not the right school for a person who had already identified his life's work and was impatient to begin it.

He transferred to New York University. The move was significant not because NYU was a better school, though it was, for his purposes, but because New York was a different system. St. Louis had taught him how cities worked. New York showed him how cities felt when they worked at maximum capacity, the density, the speed, the overwhelming volume of human activity compressed into a grid of streets that forced interaction. He loved it. He walked everywhere. He rode the subway and noted the system design, the way millions of people were routed through underground tunnels with a precision that was invisible until it broke down. He observed the messengers, the couriers, the delivery trucks, the flow of goods and people and information through the city's arteries. New York was a dispatch system operating at scale, and he was inside it.

At NYU, he studied technology and design, but he did not graduate. The pattern, enrollment without completion, was establishing itself, and it would define Dorsey's educational history. He was not a dropout in the romantic Silicon Valley sense, the genius who could not be contained by the academy. He was a person whose interests were so narrow and so consuming that the general curriculum of a university could not hold his attention. He wanted to build dispatch systems. Everything else was noise.

What he did do, at NYU, was discover something that would change the trajectory of his life. He discovered that the dispatch problem he was working on since childhood, how do you move information through a city in real time, had a social dimension he had not previously considered. It was not just about vehicles and locations. It was about people and status. People wanted to know where other people were. People wanted to broadcast what they were doing. The social dimension of dispatch, I am here, I am doing this, this is my status, was, he realized, at least as important as the logistical dimension.

This realization did not arrive as a thunderbolt. It accumulated. He was walking through Manhattan, watching people on their phones, watching the rhythm of the city, thinking about his dispatch software, and the idea assembled itself piece by piece: What if the dispatch was not about a courier's location but about a person's status? What if everyone could broadcast a short message, where they were, what they were doing, and anyone could listen?

He was twenty-three years old. The idea would take another six years to become Twitter. But it was there, in 1999, walking through New York, formed from two decades of maps and scanners and dispatch software and the restless movement of a boy from south St. Louis who had been trying, since he was six years old, to understand how things moved through cities.

He did not stay in New York. The dispatch software he was building attracted the attention of a company in San Francisco, a startup that needed someone who understood real-time messaging. He moved west. He was twenty-four. San Francisco in 2000 was at the peak of the dotcom bubble, and the city was vibrating with money, ambition, and the collective delusion that the internet had repealed the ordinary laws of economics. Startups were everywhere. Developers were in demand. A young man who could write dispatch software and who understood real-time systems found work immediately.

The company was called Dispatch Management Services Corporation, and it did exactly what its name suggested: it managed dispatch. Couriers, taxis, emergency services, the company built software that routed them. For Dorsey, this was the professional realization of a childhood obsession. He was being paid to solve the problem he had been thinking about since he was eight years old.

But the company, like many companies in 2000, did not survive the bubble's collapse. The dotcom crash wiped out firms across the Bay Area, and Dispatch Management Services Corporation was among them. Dorsey found himself in San Francisco without a job, without a degree, and without a clear next step. He was twenty-five years old, and for the first time in his life, the systems he understood, the networks, the dispatches, the real-time flow of information, could not help him. He was not a piece of information moving through a network. He was a person, standing still, in a city where the network had crashed.

He did what people in their twenties do when the plan fails: he improvised. He took jobs. He drove for a time. He considered going to fashion school, an aspiration that his later critics would seize on as evidence of unseriousness but that, in context, reflected a genuine interest in design and aesthetics that had been present since childhood. The boy who drew maps cared about how things looked, not just how they worked. The desire to study fashion was not a digression from the path that led to Twitter. It was an expression of the same instinct that would later produce Twitter's famously clean interface, its blue bird logo, its aesthetic of simplicity.

He also became a licensed massage therapist. This fact has been reported in profiles with an air of amused condescension, as if a future billionaire's detour into bodywork were a biographical embarrassment. It was not. It was a twenty-five-year-old trying different things while waiting for the right thing to arrive. And the massage therapy, like the fashion interest, reflected something about Dorsey that the standard tech biography tends to flatten: he was not purely technical. He was a person who cared about bodies, about physical presence, about the felt experience of being a human being in a physical world. This would matter later, when he built Square and insisted that the payment experience feel natural, when he designed Twitter and insisted that the interface be calm, when he adopted the daily practices, the ice baths, the walking, the fasting, that would make him the strangest CEO in Silicon Valley history.

The massage therapy certification deserves a closer reading than it typically receives. Dorsey pursued it in the early years of the 2000s, attending a formal program and completing the training that California licensure required. The decision was not arbitrary. Massage therapy, in its formal practice, demands a particular kind of attention: the practitioner must read the body's tension and resistance, locate the places where the system has failed, and apply precisely calibrated pressure to restore function. The vocabulary of bodywork, tension and release, restriction and flow, is also the vocabulary of network engineering. Both practices require the same fundamental diagnosis: where is the system blocked, and how do you clear the blockage?

The connection is not fanciful. It is the kind of lateral thinking that characterized Dorsey's approach to every problem he ever engaged. He did not divide his interests into technical and non-technical, relevant and irrelevant. He brought the same analytical orientation to every domain: what is the underlying system, what is preventing it from functioning optimally, and what minimal intervention would restore the optimal flow? The answer was the same whether the patient was a person's knotted shoulder or a startup's broken payment infrastructure. You found the blockage. You cleared it. You reduced friction to its minimum. You let the system work.

His interest in fashion operated through a similar logic. Fashion is, at its core, a system of signals: materials, cuts, colors, and assemblies that communicate status, identity, and membership to other people in the social network. The designer is an information architect, encoding signals into objects that other people decode. Dorsey enrolled in fashion design courses at NYU and took additional coursework in the early 2000s, drawn not by the glamour of the industry but by its semiotic precision. The best designs communicated everything essential and nothing unnecessary. The standard was the same standard he applied to dispatch messages and, eventually, to tweets.

The early 2000s in San Francisco were lean years. The bubble had burst. The money was gone. The developers who had been making six-figure salaries were driving for delivery services and waiting tables. But the infrastructure the bubble had built, the fiber-optic cables, the server farms, the software tools, the community of developers who knew how to build things on the internet, survived the crash. And from that infrastructure, the next generation of internet companies would emerge.

Jack Dorsey was waiting, in a city where the network had crashed, for the network to restart. He had his maps. He had his dispatch instinct. He had an idea about status messages that he could not yet build because the technology was not ready.

The technology would be ready soon. And when it was, the boy from Holly Hills would build the thing he was imagining since he was six years old.

He just needed to meet the right people first.

What St. Louis gave Dorsey that New York and San Francisco could not was an understanding of failure at the system level. By the time he left for Rolla in 1995, the city's population had fallen to roughly 380,000 from its 1950 peak of 856,796. The decline was visible in the streetscape, the empty storefronts on once-busy commercial corridors, the bus routes that had been cut as ridership fell, the parks that had been maintained in the 1960s and were not being maintained now. The infrastructure persisted but the density that had animated it was gone.

The bus system was instructive. St. Louis had operated a comprehensive streetcar network until 1966, when the last lines were abandoned in favor of the automobile culture that was consuming American cities. By the time Dorsey was drawing his maps, the bus system that replaced the streetcars was running reduced routes on reduced schedules, a skeleton of the network that had once made the city navigable without a car. He tracked the routes. He noted which neighborhoods had been disconnected from the system. He understood, in the way that a child who has been paying attention understands, that a city is a series of connections, and that the removal of a connection does not simply make one thing inaccessible; it reduces the accessibility of everything connected to it.

The systems principle: a network's value derives not from the number of its nodes but from the connections between them. Remove enough connections and the network ceases to function, not because the nodes have disappeared but because the links between them have. St. Louis in the 1980s and 1990s was a lesson in what happens to a network when the connections thin. Dorsey learned the lesson before he had a name for it, and the lesson would inform his approach to both Twitter and Square: build a network that maintains its connections, that routes around blockages, that finds alternative paths when primary paths are closed.

He carried this understanding to San Francisco, where the network had crashed but the nodes remained, where the talented developers and the technical infrastructure and the cultural appetite for new things were all still present, waiting for the reconnection that would turn individual capability back into collective function. He was one node, waiting. The network would restart. He would be there when it did.