Tag: collaboration

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
Writing

The Grain Bin and the Ghost

Richard Rhodes published How to Write in 1995. In it, he offers practical advice about a writer’s reference shelf: keep a dictionary at home, own a one-volume encyclopedia. He mentions, almost in passing, that he just received the OED on CD-ROM as a birthday gift.

That sentence stops you cold in 2026.

Not because it’s quaint — though it is — but because of what it reveals about how a writing life was organized. Rhodes wasn’t describing luxury. He was describing infrastructure. The reference shelf was load-bearing. You kept facts at home the way you kept food in a pantry: because access wasn’t guaranteed, because the library closed, because the gap between not-knowing and knowing could be measured in trips and hours. A writer’s bookshelf was a personal hedge against scarcity.

Think about what it meant that someone’s birthday present was a reference tool. Not a novel. Not a bottle of wine. Twenty volumes of the most authoritative dictionary in the English language, compressed to a disc, given because a writer needed it and couldn’t otherwise have it on their desk. That’s what a writing life cost. That’s what it demanded of the people around you.

That scarcity is gone so completely it’s hard to reconstruct the phenomenology of it.

The bottleneck in Rhodes’s world was access. You either had the fact or you didn’t. Getting it required physical movement — to the shelf, to the library, to someone who knew. The reference book’s value was proximity: it collapsed the distance between the question and the answer. The OED on CD-ROM was remarkable precisely because it put those twenty volumes on your desk. No trip. No waiting. That was the gift.

The bottleneck now is entirely different. Access is solved, trivially, for anyone with a phone. The question isn’t where the facts are. The question is which facts to trust, how they were assembled, whether the source has an agenda, whether the model that synthesized them has introduced drift. We moved from a scarcity problem to a judgment problem, and most of our inherited intellectual habits were built for the former.

But something else happened too, something Rhodes couldn’t have framed because it didn’t exist: the infrastructure became generative. The reference shelf held facts. It didn’t think with you. It didn’t draft alongside you, or push back on your argument, or notice that the claim you just made contradicts something three paragraphs earlier. The CD-ROM OED was static; it waited to be consulted. The tools a writer reaches for now don’t wait. They participate.

This is the structural shift that the grain bin metaphor can’t contain. Rhodes was describing a writer’s relationship to stored knowledge — how you accumulate it, how you keep it close, how you move through it when you need it. That relationship was essentially curatorial. You built a collection. You maintained it. You drew from it.

What’s emerging now is something more like a collaboration with an infrastructure that has opinions. Not always right ones. Not always trustworthy ones. But opinions nonetheless — which means the writer’s job has changed in kind, not just in degree. You’re no longer managing a pantry. You’re managing a working relationship.

Where does it end up? Probably somewhere Rhodes would recognize at the level of the goal — clarity, the right word, the true sentence — and find almost unrecognizable at the level of method. The shelf is still there. But it talks back now. And figuring out what that means — whether to trust it, when to push against it, how to stay the one doing the writing — is the work no one has finished yet. Maybe no one can, while it’s still changing this fast.

Categories
Creativity Photographers Photography Serendipity Writing

He Taught Us How to See

Michelangelo said he didn’t create his sculptures. He just removed the marble that wasn’t the statue.

I’ve been thinking about that lately. About what it means to have a collaborator whose job isn’t to add things but to help you find what’s already there. I’ve been doing that kind of work recently — the excavation kind — and it has changed how I write and honestly how much I enjoy the making of it.

But I’m getting ahead of myself. Start with Jay.

Continue reading “He Taught Us How to See”
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
Creativity Curiosity Living Work

The Human Router

There is a distinct difference between information and wisdom, and often, that difference is measured in velocity. We are accustomed to thinking that faster is better—fiber optic cables, 5G, real-time Slack notifications. We want knowledge to travel at the speed of light.

But Dan Wang, in his book Breakneck, captures a sociological truth about Silicon Valley that defies this obsession with speed:

“When I worked in Silicon Valley, people liked to say that knowledge travels at the speed of beer. Engineers like to talk to each other to solve technical problems, which is how knowledge diffuses.”

It is a charming, slightly irreverent metric, but it points to something profound about how humans solve difficult problems. There is “codified knowledge”—the explicit instructions found in textbooks, API documentation, and internal wikis. This travels instantly. It is frictionless. It is also, usually, insufficient for true innovation.

Then there is “tacit knowledge.” This is the intuition, the heuristic, the war story about why a specific architecture failed three years ago. This knowledge is heavy. It doesn’t travel through fiber optics; it travels through proximity. It requires the social friction of a shared table and the serendipitous collision of two engineers venting about a seemingly unrelated problem.

Crucially, this mechanism requires a specific type of operator: the Connector. These are the unsung heroes of the “speed of beer” economy. They aren’t always the 10x engineers on the leaderboard. They are the “human routers”—the people who instinctively know that the problem you are facing today is the same one Sarah from the Platform team solved last year. They are the ones who drag the introverted genius out to the pub, not to distract them, but to plug them into the grid. They curate the environment where the spark can jump the gap.

In our modern drive for remote efficiency, we are optimizing for the transfer of data. But we must be careful not to optimize away the people who pour the drinks, literal or metaphorical. That slow, liquid diffusion of ideas is often where the real breakthrough hides—steered by those special few who know exactly who needs to talk to whom.

Categories
AI AI: Large Language Models

The Texture of Autonomy

There is a distinct texture to working with a truly capable person. It is a feeling of relief, specific and profound.

When you hand a project to a junior employee who “gets it,” the mental load doesn’t just decrease; it vanishes. You don’t have to map the territory for them. You don’t have to pre-visualize every stumble or correct every navigational error. You simply point to the destination, and they find their way.

I was thinking about this feeling—this specific brand of professional trust—when I read a recent observation from two partners at Sequoia regarding the current state of Artificial Intelligence:

“Generally intelligent people can work autonomously for hours at a time, making and fixing their mistakes and figuring out what to do next without being told. Generally intelligent agents can do the same thing. This is new.”

The phrase that sticks with me is “without being told.”

For the last forty years, our relationship with computers has been strictly transactional. The computer waits. We command. It executes. Even the most sophisticated algorithms have essentially been waiting for us to hit “Enter.” They are tools, no different in spirit than a very fast abacus or a hyper-efficient typewriter.

But we are crossing a threshold where the software stops waiting.

The definition of intelligence in a workspace isn’t just raw processing power; it is the ability to recover from failure without supervision. It is the capacity to run into a wall, realize you have hit a wall, back up, and look for a door—all while the manager is asleep or working on something else.

When Sequoia notes that “this is new,” they aren’t talking about a feature update. They are talking about a shift in the ontology of our tools. We are moving from an era of leverage (tools that make us faster) to an era of agency (tools that act on our behalf).

This changes the psychological contract between human and machine. If an agent can “figure out what to do next,” we are no longer operators; we are managers. And as anyone who has transitioned from individual contributor to management knows, that is a fundamentally different skill set. It requires clearer intent, better goal-setting, and the ability to trust a process you cannot entirely see.

We are about to find out what it feels like to have a digital colleague that doesn’t just listen, but actually thinks about the next step.

Categories
AI

Imagining the Future

“imagining the future is most mind-opening when we do it with others. We can notice how differently others feel about the same possible future. We can take in the details of their imagination so we have material to work with in our own mind. When we take ten-year trips to the future together, it’s much easier to keep adapting and evolving our own beliefs.” (Jane McGonigal, Imaginable)

This is one of the best uses I’ve found for AI. Like having a smart colleague, AI can brainstorm with me and open up new paths for me to explore. An unexpected result.