Categories
Business History

The Architecture of Unseen Influence

We build our monuments over the wrong graves. Itโ€™s a bad habit of ours, this craving for the lone geniusโ€”the larger-than-life figure who supposedly commands the tides of progress by sheer force of will. But look beneath the surface of how things actually get built. The reality is messier. And a hell of a lot more interesting.

Take Thomas Edison. Secular saint of American ingenuity. The wizard who single-handedly lit up the dark. Except he didn’t. Edison wasn’t a solitary creator; he was a brilliant, ruthless aggregator of other peopleโ€™s breakthroughs and a master of public relations. He invented the bulb, sure, but his real masterpiece was the myth of himself. In the process, he eclipsed the collective sweat of his own labs and the far more elegant alternating-current systems of his rivals. Heโ€™s our most overrated figureโ€”not because he lacked talent, but because his shadow blinded us to how progress actually happens.

Morgan Housel nailed this structural blind spot by tracing the tangled ancestry of major turning points:

“Every current event โ€“ big or small โ€“ has parents, grandparents, great grandparents, siblings, and cousins. Ignoring that family tree can muddy your understanding of events, giving a false impression of why things happenedโ€ฆ Viewing events in isolation, without an appreciation for their long roots, helps explain everything from why forecasting is hard to why politics is nasty.”

Look past the blinding light of the celebrity inventors and you find the long roots that actually remade our world. Take FCC Part 15. Itโ€™s an event almost no history textbook bothers to mention. In the early 1980s, a lone staff engineer named Dr. Michael Marcus looked at three chunks of the radio spectrumโ€”stuff discarded as “garbage bands” reserved for industrial microwave ovensโ€”and saw an opening. The entire telecom establishment thought he was chasing a recipe for chaotic interference.

Marcus didn’t blink. He spent years pushing through a dry, technical ruling in 1985 to open those garbage bands for unlicensed public use. A total footnote. Yet that single, unheralded bureaucratic open door laid the invisible foundation for Wi-Fi, Bluetooth, and the entire wireless ecosystem running your life today. Marcus didn’t get a ticker-tape parade; he got political friction and a quiet transfer to a back-office enforcement role. No hero on horseback. Just a guy in a cubicle who rewired the world.

We do the same thing with politics. We rank presidents by the volume of their rhetoric or the body count of their wars. Meanwhile, men like Chester A. Arthur get left in the dusty margins of trivia. Arthur was the ultimate product of the spoils systemโ€”a New York machine politician who climbed to power on institutional corruption. Then James A. Garfield was assassinated, and Arthur was thrust into the big chair. Something clicked. Instead of feeding the machine that birthed him, he turned inward, defied his old patrons, and signed the Pendleton Civil Service Act. He dismantled the very patronage system heโ€™d mastered. It was a stunning act of quiet integrity that killed his political future but saved the republicโ€™s administrative soul.

Or take Frances Perkins. Ask the average student who gave them the weekend, the forty-hour work week, unemployment insurance, and the abolition of child labor, and youโ€™ll get a blank stare. Perkins was FDRโ€™s Secretary of Labor. She wasnโ€™t a regular on the campaign posters. She just stood in the back of the room, turning abstract economic suffering into concrete human safety nets.

Iโ€™ve been sitting with this for a few days, thinking about my own careerโ€”and the times I mistook the loudest person in the room for the smartest. I chased the visionary founders with the spellbinding pitches. I ignored the quiet engineers and the mundane infrastructure choices that actually determine whether an idea scales or snaps. It takes a few painful, expensive missteps to realize that the real compounding interest of progress is almost always generated in the dark.

History isn’t a solo act. Itโ€™s an intricate, mostly anonymous collaboration between accidental reformers, stubborn bureaucrats, and regulatory footnotes. If you want to understand where we’re going, stop staring at the stage lights.

Start looking at the wiring.

Categories
AI Business IBM Management

Making It Up As We Went Along

There was a building along Route 270 in Gaithersburg, Maryland where people kept secrets for a living. Not the cloak and dagger kind. The corporate kind, which in its own way requires just as much discipline. The IBM Washington Systems Center occupied a two-story modern building that looked, from the outside, like any other outpost of late twentieth century American business. Inside it was something else. It was where IBM sent its hardest problems, and where the largest IBM customers in the world โ€” the ones whose names you would recognize immediately โ€” sent their most urgent ones back.

I worked there as a manager. But before I was a manager there, I was a hire. And before I was a hire, I was like every other IBM professional on the outside of a particular line โ€” a line I didnโ€™t fully understand until I crossed it.


At IBM there was a protocol so embedded in the culture it had almost ceased to be a rule and become something closer to a religious observance. New products were not discussed until they were announced. Not hinted at. Not alluded to. Not whispered about with a favored customer over lunch. The announcement came in the form of something called a Blue Letter โ€” a formal communication from senior leadership that functioned as the official moment a product entered the world. Before the Blue Letter, the product did not exist in any conversation you were permitted to have. After it, you could talk about nothing else.

Violation was not a career setback. It was a firing offense. Full stop.

That clarity had a kind of elegance to it. You didnโ€™t have to calibrate how much you could say or navigate gray areas. The line was absolute. And because it was absolute, and because everyone knew the consequence of crossing it, the culture enforced itself. You didnโ€™t need surveillance. You needed people to understand the stakes, and they did.


What I didnโ€™t understand, from the outside, was what that line was doing to my imagination.

When you canโ€™t see the roadmap โ€” when the strategy and the unannounced products and the long arc of where the company is going are all behind a wall you have no access to โ€” you donโ€™t experience that as absence. You experience it as depth. The things you donโ€™t know feel like they must be there for a reason. The gaps in the announced picture feel like the gaps in a great iceberg โ€” whatโ€™s visible is impressive, but whatโ€™s below the surface must be more impressive still.

I had faith in IBMโ€™s strategic intelligence the way you have faith in things you canโ€™t fully see. And faith, uncontradicted by evidence, tends toward beauty. The hidden roadmap wasnโ€™t just unknown โ€” it was, in my imagination, a thing of coherence and intention and vision. It had to be. The alternative was too unsettling to consider.

Then I got hired into the Washington Systems Center and crossed the line.


There was no single moment of disillusionment. No specific product that shattered the dream, no strategy document that read like a disappointment. It was more like a gradual adjustment of the eyes โ€” the way they adapt when you move from bright sunlight into a room lit quite differently than you expected. The room isnโ€™t dark. Itโ€™s just not what you anticipated. And once your eyes adjust you can see perfectly well, but you can never quite recover the image you had of the room before you entered it.

The reality on the inside was messier than the dream on the outside. More improvised. More human. We were, in ways I hadnโ€™t anticipated, almost making it up as we went along. Not carelessly โ€” the people at WSC were extraordinary, the work was serious, the commitment was real. But the beautiful coherent roadmap I had constructed in my imagination from the outside bore only a partial resemblance to the actual thing. Strategy, it turned out, looked different up close. Less like architecture. More like weather.

I absorbed this alone. Nobody sat me down and named what I was experiencing. Nobody had the conversation with me that I would later learn to have with others. I found my way through it by degrees, the way you find your way through most things that donโ€™t come with instructions.

What came out the other side wasnโ€™t cynicism. It was something more useful โ€” a clearer eye, a more grounded relationship to the institution I was part of. The faith hadnโ€™t been wrong exactly. It had just been innocent. And innocence, once lost, canโ€™t be recovered. But what replaces it, if youโ€™re lucky, is something steadier.


Years later I was the manager. And I was hiring IBMers โ€” good ones, experienced ones, people who had spent serious careers on the other side of the blue line. They knew the products cold. They knew the customers. They knew how to work. What they didnโ€™t know, couldnโ€™t know, was what waited for them on the inside of the wall they were about to cross.

I knew it. Because I had been them.

There is a particular expression that crosses a personโ€™s face when the actual roadmap becomes visible for the first time. It isnโ€™t dramatic. It doesnโ€™t announce itself. Itโ€™s more like a subtle recalibration โ€” a slight stillness, a momentary adjustment behind the eyes. The person in front of you is doing quiet interior work, reconciling what they imagined with what theyโ€™re now seeing. The gap between those two things is doing something to them, and theyโ€™re not sure yet what to do with it.

I learned to watch for that expression. And when I saw it I knew what was coming if I didnโ€™t get ahead of it.


The danger wasnโ€™t disappointment. Disappointment is temporary, and smart people move through it. The danger was what disappointment hardens into when it isnโ€™t named and worked through โ€” a corrosive cynicism that poisons not just the person carrying it but everyone around them. A talented IBMer who had invested a career in faith, discovered the faith was misplaced, and decided the whole enterprise was therefore hollow โ€” that person could do real damage to a team. I had seen it happen, or the early stages of it, which was enough.

So I developed what I came to think of as the god is dead conversation.

The name came from Nietzsche, though the application was strictly practical. What Nietzsche meant โ€” or one of the things he meant โ€” was that when the organizing faith of a civilization collapses, the collapse doesnโ€™t leave nothing. It leaves a vacancy that has to be filled with something else, something built rather than inherited. The god is dead conversation was about helping someone through that vacancy quickly, before they filled it with the wrong thing.

It wasnโ€™t a long conversation. It didnโ€™t need to be. What it needed to be was honest, and direct, and delivered before the cynicism had time to set.

I would tell them what I saw happening. I would tell them it was normal, expected, that everyone who crossed this particular line felt some version of it. I would tell them the dream theyโ€™d carried on the outside wasnโ€™t foolish โ€” it was a reasonable response to incomplete information, and the information had been incomplete by design, and the design had served real purposes. None of that made them naive. It made them human.

And then I would tell them what Iโ€™d learned on my own, without anyone to guide me through it. That the messiness on the inside wasnโ€™t a failure of IBMโ€™s intelligence or intention. It was just what strategy actually looks like when youโ€™re close enough to see the seams. Every institution looks more coherent from the outside than it does from the inside. Thatโ€™s not a scandal. Thatโ€™s organizational life.


The conversations were tricky. There was real care required. You were asking someone to grieve something โ€” the beautiful imagined roadmap, the faith in a hidden coherence โ€” without tipping them into bitterness about what replaced it. You were trying to accelerate a process that, left alone, might drag on for months and quietly corrode their effectiveness. And you were doing it while also being their manager, which meant you needed them functional and engaged on the other side of the conversation, not just unburdened.

What I had going for me was credibility. I wasnโ€™t delivering a message from outside the experience. I had made the same crossing. I knew the specific texture of what they were feeling because I had felt it myself โ€” the diffuse quality of it, the absence of a single dramatic moment, the gradual adjustment of the eyes. When I told them I understood what was happening to them, I actually did. I think they could tell.

Trial and error had taught me the shape of it. What didnโ€™t work I had found out the hard way, at some cost, early on. What I arrived at had been load tested by real people in real situations. It wasnโ€™t a framework from a leadership seminar. It was something I owned completely, which meant I could adapt it in the moment rather than execute a script.


Most of them came through it well. Better than well, actually.

What I hadnโ€™t fully anticipated โ€” though in retrospect it makes complete sense โ€” was what replaced the faith once it was gone. It wasnโ€™t the steadier, clearer-eyed pragmatism I had found my way to alone. It was something more potent than that. Something that surprised me the first time I saw it and then became one of the things I quietly counted on.

They came out the other side feeling superior.

Not arrogant. Not dismissive of colleagues still on the outside. But quietly, privately elevated โ€” because they were now keepers of the secrets they had once only believed in. The blue line that had shaped their entire professional identity, that had defined the boundary of what they could know and say and imagine, was now behind them. They were on the inside. They had access. They had been trusted with the actual roadmap, the real strategy, the unannounced products that the rest of the world was still constructing faith-based pictures of.

The believer had become the keeper. And keeping, it turned out, was a more powerful identity than believing. The believer is passive โ€” sustained by what they imagine. The keeper is active, responsible, trusted. They carry something real rather than something projected.

It solved my practical problem neatly, though that wasnโ€™t why it moved me. What moved me was watching people find their footing on the other side of a genuine loss and discover that the ground there was solid โ€” different from what theyโ€™d imagined, but solid. They hadnโ€™t just survived the crossing. Theyโ€™d been changed by it in a way that made them more valuable, more grounded, more fully present to the actual work.

Which was, I suppose, what the god is dead conversation had been for all along.


I think about that blue line often these days.

We are living through a moment when artificial intelligence is advancing faster than most people can track, and the organizations building it โ€” the labs, the research teams, the companies placing enormous bets on where this technology is going โ€” have their own version of the wall. Not identical to IBMโ€™s. The competitive and legal architecture is different. The culture is different. But the basic structure is the same: there is what has been announced, and there is everything else, and most people are working entirely from the announced side.

Which means most people are doing what I did before I crossed the line at WSC. They are filling the gaps with faith. And faith, uncontradicted by evidence, tends toward beauty.


The unrevealed AI roadmap looks, from the outside, like a thing of coherence and intention. The capabilities that havenโ€™t been announced yet must be more impressive than the ones that have. The strategy must be more considered than whatโ€™s visible. The gaps in the public picture feel like depth rather than uncertainty โ€” like the part of the iceberg below the surface, which must be vast because the part above is already remarkable.

I am not saying this faith is wrong. I held the same faith about IBM and it wasnโ€™t wrong exactly โ€” it was innocent. The people constructing faith-based pictures of where AI is going are doing a reasonable thing with incomplete information. The information is incomplete partly by design, for reasons that make competitive and strategic sense, just as IBMโ€™s secrecy made sense. None of that makes the faith naive.

But Iโ€™ve been inside enough walls to know what the inside tends to look like. And I think itโ€™s worth saying, clearly and without cynicism, that the reality is probably messier than the dream. More improvised. More uncertain. More human. The people building these systems are extraordinary โ€” the work is serious, the commitment is real โ€” but they are also, in ways that might surprise you, almost making it up as they go along. Not carelessly. But without the complete map that the outside imagines must exist somewhere, fully drawn, waiting to be revealed.

Strategy, up close, looks less like architecture and more like weather.


This isnโ€™t a counsel of despair. Itโ€™s almost the opposite.

The IBMers who crossed the line and survived the god is dead conversation didnโ€™t end up with less than they started with. They ended up with more โ€” a clearer eye, a more grounded relationship to the institution, a more useful kind of engagement with the actual work. The faith they lost was the innocent kind. What replaced it was steadier and more durable.

I suspect something similar is available to anyone willing to look at the AI moment with clear eyes. Not the disappointed cynicism of someone who expected a beautiful coherent roadmap and found a human institution instead. Not the breathless faith of someone still on the outside of the wall, filling gaps with generous assumptions. Something in between โ€” harder to sustain, more honest, ultimately more useful.

The technology is real. The progress is real. The stakes are real. None of that requires the roadmap to be a thing of beauty. It just requires it to be worked on seriously by people who understand what they donโ€™t yet know โ€” which, from everything I can observe, it is.


What I couldnโ€™t give those IBMers, and what nobody can give you, is the experience of crossing the line yourself. The god is dead conversation only works because the crossing has already happened โ€” because the person sitting across from you has already seen the actual roadmap and is already processing the gap between what they imagined and what they found. You canโ€™t have the conversation in advance. The disillusionment has to be real before it can be worked through.

Most of us will never cross the line into the AI labs. Weโ€™ll stay on the outside of the wall, working from the announced picture, filling the gaps as best we can. Thatโ€™s not a failure โ€” itโ€™s just the condition most of us are in, the same condition those IBMers were in for their entire careers before I hired them.

But knowing the wall exists, and knowing what walls do to imagination, seems like it ought to change something about how we hold our faith. Not abandon it. Just hold it a little more lightly. Stay curious about the seams. Remain open to the possibility that the most important thing about the unrevealed roadmap isnโ€™t whatโ€™s in it โ€” but what weโ€™ve projected onto it.

The blue line is still there. Most of us are still on the outside of it.

And the hidden roadmap still looks, from here, like a thing of beauty.

Categories
AI

The Coach Who Wouldnโ€™t Change

In 1975, a twenty-four-year-old Kodak engineer named Steve Sasson built the first digital camera. It was the size of a toaster, captured a black-and-white image at 0.01 megapixels, and took twenty-three seconds to record a single photograph to a cassette tape. Sasson showed it to his managers. Their response, as he later recalled, was essentially: thatโ€™s cute, but donโ€™t tell anyone about it.

Kodak was not a stupid company. It was a dominant one. At its peak it held 90 percent of the American film market and 85 percent of camera sales. Film was not just a product line โ€” it was the entire economic architecture of the company. Processing fees, paper, chemicals, the retail relationships built around the assumption that photographs needed to be developed. Digital threatened all of it simultaneously. So Kodak did what dominant companies do when confronted with a threat they canโ€™t absorb into the existing model: they managed it. They ran studies. They filed patents. They made incremental moves. They protected the thing that was working rather than building the thing that would work next.

Kodak filed for bankruptcy in 2012. The digital camera had been sitting in their own archives for thirty-seven years.

Nokiaโ€™s version of the same story has a different texture. Where Kodakโ€™s failure was about protecting a margin, Nokiaโ€™s was about identity. Through the 1990s and into the early 2000s, Nokia was mobile phones โ€” not a major player, but the category itself. At its peak it held over 40 percent of the global handset market. The company had navigated a remarkable transformation earlier in its history, shedding paper mills and rubber boots to become a pure technology company. It knew how to change. It had done it before.

What it couldnโ€™t do was change from a hardware company into a software one. When the iPhone arrived in 2007, Nokiaโ€™s internal assessments were, by most accounts, accurate. They understood the threat. They had touchscreen prototypes in development. What they couldnโ€™t manage was the cultural distance between building phones that were superb physical objects โ€” durable, reliable, made to exacting standards โ€” and building phones that were primarily platforms for software that other people would write. The excellence that had made Nokia great was manufacturing excellence. The game was becoming something else, and manufacturing excellence was not only insufficient for the new game; it was actively in the way, because it oriented every decision toward the object rather than the experience.

Nokiaโ€™s market share collapsed from over 40 percent in 2007 to under 5 percent by 2013.

Andy Grove, who built Intel into the dominant force in semiconductors, called it plainly: only the paranoid survive. He meant it as a prescription. His successors treated it as a trophy.

Both stories have the clean shape of settled history. We know how they end. The verdict is in, the lesson is available, and itโ€™s easy to read them now as cautionary tales about obvious mistakes made by people who should have known better.

This is the wrong way to read them.

Kodak and Nokia didnโ€™t fail because they were blind. They failed because they were standing on a fulcrum โ€” a moment when the old game and the new game were both plausibly real โ€” and they chose the wrong side. At the time, that choice was not obviously wrong. Film was still enormously profitable. Nokiaโ€™s hardware was genuinely superior. The rational case for staying the course was real, and the people making it were not fools.

The reason the Kodak story is still told fifty years later is not that the mistake was obvious. Itโ€™s that it wasnโ€™t โ€” and they made it anyway.

Which brings us to now. Because there is a fulcrum in front of the enterprise software industry, and nobody knows yet which way it tips.

The companies in question โ€” Salesforce, ServiceNow, and most of the SaaS category built over the last twenty years โ€” were constructed on a simple and powerful premise: that businesses would pay recurring subscription fees for software that managed their customer relationships, their workflows, their data. The premise was correct. It produced some of the most durable businesses in the history of technology.

The threat AI poses to this model is not subtle. If an AI agent can handle a customer service interaction, manage a workflow, or synthesize a CRM record without a human touching licensed software to do it, then the per-seat subscription model โ€” the economic engine underneath all of it โ€” starts to look like film processing in 2003. Theoretically intact. Quietly at risk.

The responses of these companies have been instructive, and theyโ€™ve diverged.

Here is the honest position: we donโ€™t know yet. The fulcrum is still in motion.

Itโ€™s possible that Salesforce’s Agentforce is the Kodak digital camera โ€” the real thing, built by the right company, that gets buried under the weight of protecting what already works. Itโ€™s possible that the SaaS model is more durable than the threat suggests, that enterprises will pay for trusted platforms regardless of the underlying labor model, and that the companies racing hardest to cannibalize their own revenue streams are making a different kind of mistake. Itโ€™s possible that ServiceNowโ€™s consistency is discipline, or that itโ€™s the Nokia instinct to keep building the best version of the thing that used to win.

What the Kodak and Nokia stories actually teach โ€” not the simplified version, but the harder one โ€” is that the mistake is never visible in the moment itโ€™s made. It only becomes visible later, when the fulcrum has tipped and the choice that was once defensible has become permanent.

The coach who wins five championships holds the philosophy and rotates the players. The coach who wins one holds the players and calls it philosophy.

The enterprise software companies standing at this moment have a version of the same decision. The ones who make it correctly will, in twenty years, be the ones we cite as examples of adaptation. The ones who donโ€™t will be the ones we cite as examples of something else.

We just donโ€™t know yet which is which. Thatโ€™s not a comfortable place to stand. It is, however, exactly where we are.

Categories
AI Business Consulting

The Toll Bridge and the Terrain

For fifteen years of my life, I lived inside the fortress of information asymmetry. I was part of a payments consulting business, and our model was exactly what Andrew Feldman described on a recent Moonshots episode when he pointed a sharp finger at traditional professional services.

His observation was simple, cutting, and entirely true:

“Their role today is to stand between ordinary people and obscure knowledge. And the application of that obscure knowledge to everyday problems.”

When I heard him say that, it landed with a quiet thud of recognition.

For a decade and a half, my colleagues and I were the ones standing in that gap. The payments industryโ€”with its labyrinth of interchange fees, compliance structures, clearing networks, and legacy tech stacksโ€”is a monument to obscure knowledge. Clients didn’t come to us because we possessed some divine, unreplicable wisdom. They came to us because the map was locked in our heads, and navigating the terrain without us was a recipe for an expensive disaster.

We charged for our time, and we earned it. We untangled complexity and solved real, everyday business problems for people who just wanted to move money safely from point A to point B.

But looking back now, I can see the architectural flaw disguised as a premium service. The economic foundation of that entire era relied on friction. It relied on the fact that it took an immense amount of human energy to retrieve a piece of obscure data and map it onto a specific business dilemma. You weren’t just paying for strategic guidance; you were paying a premium on artificial scarcity.

We are living through a moment where the marginal cost of intelligence is rapidly trending toward zero. When the barrier of “obscure knowledge” evaporates, the traditional toll bridges begin to look absurd.

For anyone starting a consulting business today, the playbook would have to be entirely different. When an LLM can parse thousands of pages of network operating rules, interchange tables, and regulatory compliance frameworks in a handful of seconds, the gatekeeper’s standing ground liquefies.

If your value proposition is merely standing between a client and a hidden database, your business model isn’t just flawedโ€”itโ€™s obsolete.

Yet, this collapses into a fascinating paradox. You might assume that when you democratize expertise, you eliminate the need for the expert. But as Dan Shipper recently observed, the reality of AI is completely counterintuitive.

Shipper points out that AI effectively packages up “yesterday’s competence” and makes it cheap and ubiquitous.

Suddenly, anyone can generate a complex contract, a software pull request, or a payments flow strategy with the click of a button. But when cheap competence skyrockets, adoption explodes, resulting in an unprecedented glut of generic outputโ€”what the internet has collectively taken to calling “slop”. Itโ€™s the default, lazy answer that lacks soul, context, and nuance.

When everything begins to look and smell the same, a strange thing happens: the market’s demand for genuine difference sky-rockets.

The shift we are facing across all professional servicesโ€”whether legal, financial, or consultingโ€”isn’t about eliminating the expert. It is about changing the expert’s job from data-retriever to orchestrator and judge. The floor has been raised. Yesterday’s ceiling is today’s baseline.

What remains is the ability to read a room. To watch a clientโ€™s shoulders tighten when you present an option thatโ€™s technically correct but organizationally impossible. To notice the glance exchanged across the table before anyone speaks. No LLM parses that. The map is universal now; the guide still has to be in the room.

We don’t need fewer guides; we need fewer toll booths. The future of consulting doesn’t belong to those who hoard the map. It belongs to those who use a universally available map to help people actually walk the terrain.

Categories
Architecture Infrastructure

The Architecture of the Indestructible

We are conditioned to look for the center of things. When we try to understand an organization, we ask for an organizational chart. When we look at a nation, we look to its capital. Traditional architectureโ€”whether of a building, a company, or an armyโ€”relies on a classic playbook: a strong hub, radiating outward. You find the center, you secure it, and the system holds.

But what happens when you try to decapitate an enemy, or a technology, that has no head?

In 1964, a brilliant engineer named Paul Baran sat at his desk at the RAND Corporation, trying to solve a Cold War nightmare: How do you maintain a communications network after a catastrophic nuclear strike? Baran realized that traditional networks were centralizedโ€”like a wheel with spokes. If you destroy the hub in the center, every single spoke becomes useless.

His solution was the distributed network, the foundational blueprint for what would eventually become the Internet.

“Under the proposed system, each station would need to be connected to only a few of its nearest neighborsโ€ฆ The system would be highly reliable, even if a large fraction of the stations were destroyed.”

Baran mathematically proved that if you remove the center, the edges don’t die. They simply reroute. A few decades later, telecom engineers used a remarkably similar logic to build cellular telephone networks. Instead of one massive, high-power radio tower serving an entire city, they broke the terrain into a grid of small, low-power cells. If one tower goes offline, the network degrades gracefully rather than collapsing. It bends, but it refuses to break.

There is a profound, poetic irony buried here. The United States government originally funded Baranโ€™s research to create a distributed network so that its centralized monolith could survive. Decades later, asymmetric adversaries across the globe adopted that exact architectural philosophy for their physical defense doctrinesโ€”creating “Mosaic Defense” systems designed specifically so that when you destroy the center, the edges keep fighting.

They copied our homework to survive our strength.

I find myself thinking about this tension far beyond the realms of military strategy or software engineering. It is a metaphor for how we construct our lives. We often build centralized livesโ€”anchored entirely to a single identity, a single career, or a single institution. We project a monolith of strength to the world. But monoliths are brittle. When the center is struck, the whole architecture crumbles.

The lesson of our modern architecture is becoming increasingly clear, whether you are managing a network, building an organization, or navigating the quiet complexities of a human life. The fragile monolith is an illusion of safety.

The future belongs to the web that knows how to reroute.

Categories
Apple Business

The Architecture of Subtraction

Hold an iPhone in your hand, or run your fingers along the cold, machined edge of a MacBook. What you are feeling isnโ€™t just glass and aluminum; you are feeling the physical manifestation of a thousand invisible rejections.

We are conditioned to think of creation as an additive process. But true institutional excellence operates in reverse. It is an act of relentless, unsentimental subtraction.

A few years ago, Tim Cook articulated what became known as the “Cook Doctrine.” It is meant to answer the existential question of what makes Apple, Apple. Reading through it, what strikes me isn’t the corporate ambition, but the brutal, uncompromising geometry of its choices.

We believe that weโ€™re on the face of the Earth to make great products, and thatโ€™s not changing. Weโ€™re constantly focusing on innovating. We believe in the simple, not the complex. We believe that we need to own and control the primary technologies behind the products we make, and participate only in markets where we can make a significant contribution.

We believe in saying no to thousands of projects so that we can really focus on the few that are truly important and meaningful to us. We believe in deep collaboration and cross-pollination of our groups, which allow us to innovate in a way that others cannot. And frankly, we donโ€™t settle for anything less than excellence in every group in the company, and we have the self-honesty to admit when weโ€™re wrong and the courage to change.

The gravity of that doctrine doesn’t live in the pursuit of “great products.” Everyone claims to want that. The gravity lives in the tension between wanting to do everything and having the discipline to do almost nothing.

“Saying no to thousands of projects” is easy to write on a slide. It is agonizing to practice in reality. It means looking at a perfectly good ideaโ€”perhaps even a highly profitable ideaโ€”and killing it because it dilutes the core mission. It is the architectural equivalent of leaving vast amounts of empty space in a room so that the few pieces of furniture inside it can actually breathe.

I think about the times in my own career when I lacked that specific kind of courage. I have held onto projects that had long since lost their spark, simply because of the sunk costs. I have said yes to interesting distractions that slowly eroded my focus on the essential work. We dilute our attention not because we intend to fail, but because the alternativeโ€”staring at a promising path and refusing to walk down itโ€”feels entirely unnatural.

That is where Cook’s point about “self-honesty” becomes the linchpin. You cannot admit you are wrong unless you have created a culture where the truth outranks the ego. The deep collaboration Cook speaks of isn’t just about sharing resources; it’s about sharing the burden of that honesty. It is a collective agreement to not settle, to look at a nearly finished product and have the courage to say, this isn’t right yet.

Ultimately, the Cook Doctrine isn’t a strategy for building computers. It is an observation about human nature. The future is only guaranteed for those who can afford to survive the presentโ€”and survival demands knowing exactly what you are not.

The chaos isnโ€™t an obstacle to the mission; it is the environment in which the mission earns its meaning.

Excellence is not just about what you build. It is also about what you are willing to destroy.

Categories
Investing Living

The Lonely Quadrant: Why the Crowd Never Outperforms

There is a profound comfort in the consensus. When we agree with the crowd, we are protected by a shared canopy of logic. If we are wrong, we are wrong together. The sting of failure is diluted by the sheer number of people who made the exact same miscalculation. We can shrug our shoulders, look at our peers, and say, “Who could have known?”

But this comfort comes at a steep price: mediocrity.

Years ago, the legendary investor Howard Marks crystallized a framework that has haunted my thinking ever since. He mapped out the relationship between predictions and outcomes, arriving at a blunt, inescapable truth about generating extraordinary results. To make really good moneyโ€”or to achieve outsized success in almost any competitive endeavorโ€”you cannot simply be right. You have to be right when everyone else is wrong.

“You can’t do the same things others do and expect to outperform.”

Marks’ logic is beautifully ruthless. If your prediction aligns with the consensus and you are right, the rewards are merely average. The market, or the world, has already anticipated and priced in that outcome. There is no edge in seeing what everyone else sees. If your consensus prediction is wrong, you lose, but you lose alongside the herd.

The danger, and the opportunity, lies in the contrarian view.

If you are non-consensus and wrong, you look like a fool. You bear the entirety of the failure alone, stripped of the insulation of the crowd. This is the quadrant of public mockery, isolated defeat, and bruised egos. It is the fear of this quadrant that keeps most people safely tucked inside the consensus.

But the magicโ€”the life-changing returns, the paradigm-shifting innovations, the profound personal breakthroughsโ€”lives exclusively in the final quadrant: being non-consensus and right.

This isn’t just an investing principle; it’s a philosophy for navigating life. We are biologically wired to seek the safety of the herd. To step outside of it requires not just immense intellectual conviction, but a formidable emotional threshold. You have to be willing to sit with the discomfort of being misunderstood, sometimes for years. You have to endure the sympathetic smiles of peers who think youโ€™ve lost the plot.

Creating truly great art, building a lasting company, or making an exceptional investment demands a willingness to be lonely in your convictions. It requires looking at the exact same data as everyone else and seeing a completely different narrative.

However, a vital caveat remains: being different isn’t enough. There are plenty of contrarians who are simply wrong, confusing blind rebellion with profound insight. The goal isn’t to be a contrarian for the sake of being difficult or edgy. The goal is to perceive a truth the crowd has missed.

It is a quiet, solitary bet against the world’s prevailing wisdom. And when the world finally catches up to where you have been standing all along, the reward is entirely yours.

Categories
Curiosity

Hunting for the “Why”

Iโ€™ve spent a lot of time watching peopleโ€”myself includedโ€”hit what feels like a glass ceiling. We often chalk it up to a lack of “natural talent” or the missing spark of genius. We look at the high-flyers in our industry and assume they were born with a blueprint we never received. But lately, Iโ€™ve realized that the most successful people I know aren’t necessarily the ones with the highest IQ; theyโ€™re the ones who simply never stopped asking why.

Bill Gurley puts a name to this:

โ€œThe thing that will differentiate you more in your career than anything else is being the most hyper-curious person.โ€

For me, curiosity isn’t a personality trait; itโ€™s an appetite. Itโ€™s that itch in the back of your brain when something doesn’t quite make sense. Hyper-curiosity is the willingness to be the “annoying” person who asks for the raw data or the one who stays up an hour late following a rabbit hole that has nothing to do with tomorrow’s to-do listโ€”and everything to do with how the world actually works.

We live in an age where the “ivory tower” has been dismantled. The walls are down.

โ€œI canโ€™t make you the most talented person in your company or your field, but you have no excuse not to be the most knowledgeable person. The information is all out there.โ€

This hits hard because it removes our favorite excuse: “I just wasn’t born for this.” It shifts the weight from our DNA to our discipline. Iโ€™ve found that the moment I stop being a passive consumer and start being a hunter of information, my world gets bigger. Knowledge is the only asset that doesn’t depreciate; in fact, it compounds.

When you commit to being the most curious person in the room, you arenโ€™t just “doing well.” You are building a life in high-definition.

โ€œIf you are the most curious person constantly learning in your field, you will do extremely well.โ€

But beyond the “doing well,” thereโ€™s a deeper peace that comes with it. You realize that you don’t need to be the smartest person in the roomโ€”you just need to be the one most willing to learn from it.

Categories
Living Serendipity

The Architecture of the Unexpected

We spend an incredible amount of energy trying to build a ceiling over our lives, a structure made of spreadsheets, five-year plans, and trend forecasts. We convince ourselves that if we just gather enough data, the future will become a navigable map. But Morgan Housel, in Same as Ever, cuts through this illusion with a quiet, devastating observation:

“We are very good at predicting the future, except for the surprisesโ€”which tend to be all that matter.”

It is a humbling thought. We can predict the mundane with startling accuracyโ€”the seasons, the commute, the steady inflation of a currency. But the events that actually shift the trajectory of a life, a business, or a civilization are precisely the ones that no model accounted for. We are experts at forecasting the rain, yet we are consistently blindsided by the flood.

This reveals a profound tension in the human experience. We crave certainty because certainty feels like safety. We want to believe that the “tail events”โ€”those low-probability, high-impact occurrencesโ€”are outliers we can ignore. In reality, history isn’t a steady climb; itโ€™s a series of long plateaus punctuated by sudden, violent leaps.

The problem isn’t that our models are broken; itโ€™s that we are looking at the wrong thing. Instead of seeking total foresight, we must prioritize serendipity and resilience. If the future is defined by surprises, then the most valuable asset isn’t a better crystal ballโ€”itโ€™s a wider margin of safety.

We must learn to live with the paradox: we must plan for a future that we know, deep down, will not go according to plan. The surprises aren’t just interruptions to the story; they are the story.

Looking back at the last decade of your life, what was the single ‘surprise’ event that defined your path more than any plan you ever made?

Categories
Business

The Geometry of Focus: Finding the Limiting Factor

In the modern landscape of high-stakes management, there is a recurring temptation to solve everything at once. We are taught to optimize across the boardโ€”to improve efficiency by 2% here, 5% thereโ€”until the entire machine hums. But in a recent conversation with John Collison and Dwarkesh Patel, Elon Musk repeatedly returned to a single, almost obsessive mantra: the “limiting factor.”

It is a deceptively simple phrase. It suggests that at any given moment, there is one specific bottleneck that dictates the speed of the entire enterprise. If you aren’t working on that, you aren’t really moving the needle. You are merely polishing stuff.

“I think people are going to have real trouble turning on like the chip output will exceed the ability to turn chips onโ€ฆ the current limiting factor that I seeโ€ฆ in the one-year time frame itโ€™s energy power production.”

Muskโ€™s management technique is not about broad oversight; it is about a radical, almost violent prioritization. He looks at the timelineโ€”one year, three years, ten yearsโ€”and asks: What is the wall we are about to hit? Right now, it might be the availability of GPUs. In twelve months, it might be the physical gigawatts of electricity required to plug them in. In thirty-six months, it might be the thermal constraints of Earthโ€™s atmosphere, necessitating a move to space.

This approach requires a high “pain threshold.” To solve a limiting factor, you often have to lean into acute, short-term struggle to avoid the chronic, slow death of stagnation. John Collison noted this during the interview:

“Most people are willing to endure any amount of chronic pain to avoid acute painโ€ฆ it feels like a lot of the cases we’re talking about are just leaning into the acute painโ€ฆ to actually solve the bottleneck.”

For many leaders, the “limiting factor” is often something they aren’t even looking at because it lies outside their perceived domain. A software CEO might think their limit is talent, when itโ€™s actually the speed of their internal decision-making. A manufacturer might think itโ€™s raw materials, when itโ€™s actually the morale of the factory floor.

To manage by the limiting factor is to admit that 90% of what you could be doing is a distraction. It is a philosophy of subtraction and focus. It demands that we stop asking “What can we improve?” and start asking “What is stopping us from being ten times larger?” Once you identify that wall, you throw every resource you have at it until it crumbles. And thenโ€”and this is the part that requires true staminaโ€”you immediately go looking for the next wall.

By focusing on the one thing that matters, we stop being busy and start being effective. We stop managing the status quo and start engineering what may feel like the impossible.