Tag: leadership

Categories
Aircraft History

The Merlin

There is a sound that men who heard it never forgot. Not the roar exactly, though it roared. Something beneath the roar — a note, almost musical, that settled into the chest and stayed there. Four Rolls-Royce Merlins at full throttle on a Lancaster climbing out of Lincolnshire in the dark, and sixty years later old men would close their eyes trying to describe it and find they couldn’t, not quite, which was itself a kind of description.

The engine was a miracle of the wrong era. Liquid-cooled, sixty degrees of vee, twenty-seven liters of displacement producing over a thousand horsepower from something you could fit in a large kitchen. Rolls-Royce had been making engines since 1906, had learned things about metallurgy and tolerance and the behavior of superheated gases under compression that couldn’t be written down, only accumulated, passed hand to hand through decades of making things that had to work when nothing could be allowed to fail. The Merlin was the distillation of all of it.

And then — this is the part that stops you — they couldn’t build enough of them.

Britain in 1940 was a country running on nerve. The factories were working. The workers were willing. But the math was brutal and the math didn’t care about willingness. So someone made a phone call to Detroit. To Packard. A company that had spent thirty years building luxury automobiles for American industrialists, cars with interiors like drawing rooms on wheels, cars that announced their owners had arrived at exactly the place they had always intended to be. Packard looked at the Merlin blueprints, converted the tolerances from imperial to metric and back again, retooled their entire production line, and started building the engine that would power the Spitfire, the Hurricane, the Lancaster, and the P-51 Mustang.

Think about what that required. Not just the engineering, though the engineering was extraordinary. The belief required. That these tolerances mattered. That this particular arrangement of pistons and supercharger vanes and coolant passages was worth the disruption of an entire industrial operation. Packard’s engineers didn’t question the design. The design had already proven itself.

You built the Merlin because the Merlin worked.

The question — the one that takes longer to arrive — is what you do when the thing the Merlin is for doesn’t.

Arthur Harris believed.

That is the first thing to understand about him, and maybe the last. He believed in the bomber the way certain people believe in a technology so new and so powerful that the believing itself feels like vision. Strategic bombing would break Germany. Not assist in breaking Germany. Not contribute to a larger effort that would break Germany. Would, by itself, through the systematic destruction of German cities and the German will to continue, end the war. Harris had held this view before the war began and he held it after the evidence came in and he held it, unmodified, until he died in 1984.

This is not stupidity. The most costly certainties never are. Harris was shrewd, forceful, organizationally gifted, genuinely courageous in the sense that he was willing to send men to die for what he believed and knew he was sending them. He understood logistics, understood morale, understood the brutal arithmetic of attrition. What he could not do — what the structure of his certainty would not permit — was update.

The evidence arrived slowly enough that you could always explain it away. German war production increased through 1943, then through 1944, even as the bombers came night after night. The factories dispersed. The workers adapted. The morale that was supposed to crack showed instead a remarkable tendency to consolidate under pressure, the way populations sometimes do when the threat comes from the sky and cannot be reasoned with. The theorists had a model of human psychology that turned out to be wrong, and the model’s wrongness kept arriving in the data, and Harris kept flying.

Fifty-five thousand men.

Picture Harris alone. The commander in the early morning after the casualty reports come in, before the day’s work begins again. The loneliness of a certainty that has become structural — no longer a belief you hold but a belief that holds you, because the alternative is not just being wrong but having been wrong, which means all those boys went down over the Ruhr for a theory, which is a weight no living person can carry and continue to function. So you don’t revise. You recommit. You ask for more aircraft, more crews, more nights.

You build more Merlins.

This is the mechanism. Not malice. Not indifference. The certainty becomes self-protective, which means it becomes invisible, which means it becomes the water you swim in rather than a position you hold. Harris stopped being a man with a theory about bombing and became a man for whom bombing was the answer to every question, including the question of whether bombing was working.

The Lancaster crews knew something was wrong before Harris did. You could see it in the casualty rates, which they could calculate as well as anyone — better, actually, because they were doing the calculating with their own lives as the variable. Forty-four percent didn’t survive their tours. They knew this. They flew anyway, because courage doesn’t require certainty about the strategic framework, only about the man beside you and the mission tonight.

The Merlin started and you went.

The Merlin outlasted the theory. It kept flying for decades after the war, in civilian aircraft, in racing planes, in the occasional restored Lancaster that still tours airshows in Britain, where crowds gather on summer afternoons to watch it pass and hear, carried on the wind, that sound. The note beneath the roar. The thing that settles in the chest.

Beautiful, people say, watching it go.

And it is. It genuinely is.

What they couldn’t know — what none of them could know — was that the engine was the most reliable thing in the entire enterprise.

Categories
Business Storytelling

The Closed Laptop

The conference rooms all look the same after a while. Same long table. Same chairs that cost more than they should. Same window with the same view of the same parking lot baking in the same California sun. You stop seeing them. You develop a kind of practiced receptivity, a professional openness that is also, if you are honest, a professional distance. You have heard the story before. You know where you are in the presentation without looking at the slide number.

Until the day someone sits down across from you and closes their laptop and says: can I just tell you our story?

Fred Wilson, the venture capitalist at Union Square Ventures, has spent forty years learning to tell the difference between founders who can build and founders who can make you believe. The skill he overweights now, he’ll tell you plainly, isn’t technical. It’s selling. Recruiting, fundraising, convincing customers, inspiring teams. “Actually being able to write code,” he said recently, “is probably not a big deal anymore.” What matters is whether you can cross the distance between your vision and someone else’s imagination and deposit something true and alive on the other side.

Most founders never figure this out. They build the deck instead. They pull the projector cable from the drawer — there is always a drawer, there is always a cable — and the room fills with blue light and bullet points and the comfortable geometry of a prepared presentation, and what never happens is the thing that needed to happen.

But there was this one morning.

He came in with his cofounder in the flat gray light that Silicon Valley gets in February, when the rain has stopped but the sky hasn’t decided what it wants to be. They were early. He set his bag down and sat directly across from me — not at the presenter’s angle, not with one eye already calculating the distance to the screen — directly across, the way you sit with someone you already know, or intend to. Neither of them reached for the cable in the drawer.

He looked at me with the particular steadiness of a person who has decided not to manage the moment.

Can I just tell you our story?

I want to be honest about what happened next, which is that I felt something shift before he said another word. Not a decision exactly. More like the precondition for a decision, the ground tilting slightly in a direction I hadn’t chosen. I was, in some way I couldn’t have defended rationally at the time, already with him. And I knew it, and I knew it was not an entirely reasonable response to a man who had been in the room for less than a minute, and I felt it anyway.

The laptop stayed closed for the next twenty minutes. No transitions. No bullet points. No hockey stick arcing toward a number reverse-engineered from a desired outcome. Just his voice and what he believed and the quality of attention you give a person when there is nothing else in the room to look at.

The deck came later. It was beautiful. By then it didn’t need to be anything except true.

Storytelling is not a skill in the way that financial modeling is a skill. It is older than that by such a margin that the comparison almost doesn’t make sense. What we are really talking about is the oldest technology human beings possess — a person in a room, a voice, an image made of nothing but words and the willingness to believe in them. It was doing its work around fires forty thousand years before the first conference room was built, and it has never once required a projector.

What the great storytellers understand, and what the best founders understand in the same unspoken way, is that a story is not a transfer of information. It is a transfer of inner states. When it works — when it really works — something that existed inside one person gets reconstructed inside another, and the listener emerges changed. Not persuaded. Not informed. Changed. These are different experiences, and only one of them makes a person willing to bet their career on something that doesn’t exist yet.

The deck puts glass between the teller and that possibility. The founder stands at the edge of the blue light pointing at things, and the room evaluates the things, and what never happens is the transfer. Everyone files out having formed opinions about the slides rather than beliefs about the person. Opinions and beliefs are not the same.

Wilson understands this even if he wouldn’t use these words. When he says the skill is selling, what he means underneath the selling is: can this person walk into a room and make other people inhabit their vision? Not convince them. Inhabit. The difference is the difference between reading about a place and being there. One of them changes how you act. The other one you forget on the drive home.

The projector cable is still in the drawer. Someone will pull it out next week, and the room will fill with blue light, and another founder will stand at the edge of it pointing at things, hoping that the right font and the right graph will do the work that only a human being, exposed and without props, can actually do.

It won’t. It never does.

The CEO who closed his laptop had been carrying a story he believed in, and he knew the story was the thing, not the packaging around it. He understood that the oldest container is also the most powerful one. His own voice. A room. Someone willing to listen.

I was ready to work with him before he said another word.

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
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
Living Sports Writing

When the Lights Come On

I was listening to a conversation with the writer Wright Thompson recently, and he struck a profound chord when talking about why he is so captivated by sports. He distilled the entirety of athletic competition down to a single, brilliant truth: it is all about who you are when “the lights come on.”

If you have ever stood in a massive arena or a darkened stadium just before the main event, you know exactly the feeling he means. The anticipation in the air isn’t just an emotion; it is a physical weight. You can feel the collective breath of thousands held in suspense. And then, with a sudden, sharp clack of the breakers, the big stadium lights hit. The room almost shakes with the sudden injection of energy. In that brilliant, unforgiving glare, every shadow vanishes. There is nowhere to hide.

We are taught from a young age to prepare, to practice, to build our skills in the quiet comfort of the shadows. We spend so much of our lives rehearsing our arguments, refining our projects, and constructing our mental models. We tell ourselves stories about who we are and what we are capable of achieving. But the true test of our character—the raw, unfiltered reality of our competence—isn’t found in the safety of preparation.

It is revealed in the sudden shock of execution.

Thompson’s observation about sports is ultimately an observation about the human condition. We aren’t all athletes waiting in the tunnel, shifting our weight from foot to foot, but we all face our own versions of the stadium lights.

I think about the seasons in my own life when the lights suddenly flared. The unexpected crisis that derailed months of careful planning. A sudden pivot required in a business strategy. A moment demanding moral courage when it would have been infinitely easier to remain quietly in the background. In some of those moments, I stepped up, grounded by the quiet work I had done in the dark. In others—and I admit this with a wince—I blinked against the glare, my confidence suddenly outpacing my competence.

That is the terrifying, beautiful geometry of choices. When the lights hit, the gap between who we claim to be and who we actually are is illuminated for everyone to see.

There is a kind of extreme accountability in that moment. It strips away the hedging and the theoretical. You either make the play, or you don’t. You either hold your ground, or you retreat. It is a crucible that burns away the superfluous, leaving only the essential truth of our character.

We cannot control when the switch will be flipped. The world has a habit of throwing us onto the stage precisely when we feel least ready. But we can control how we build ourselves in the dark. We can ensure that our patience isn’t just stubbornness in disguise, and that our confidence is deeply rooted in reality.

The chaos of the sudden glare isn’t an obstacle to the mission; it is the environment in which the mission earns its meaning. The lights will come on. They always do.

The only question that matters is who we will be in the glare.

Categories
AI

The Geometry of Speed

We are surprised when witnessing something move faster than our intuition expects. We are inherently wired to understand slow, compounding growth. We expect the long, grinding years of the plateau—the quiet periods where nothing seems to happen before a sudden breakthrough.

I was looking at a chart Patrick Collison shared this morning, and it challenged that very intuition. It’s a simple, stark visualization: AI model intelligence relative to the formation date of the lab that built it.

If you trace the lines for Google and OpenAI on the right side of the graph, you see the history we’ve all lived through. Thousands of days—more than a decade of quiet, methodical, often unglamorous research—before their trend lines finally bend and shoot upward. It is a geometry of patience. It’s the visual representation of laying bricks, one by one, year by year, until you have a foundation sturdy enough to support the weight of a revolution.

And then, on the far left of the chart, there is a red line. MSL. The team behind Meta’s new Muse Spark model, released today.

The red line doesn’t curve. It doesn’t slope. It simply strikes straight up, like a lightning bolt in reverse.

In roughly 200 days since formation, this new effort achieved a level of capability that took the early pioneers thousands of days to reach. Collison noted how much he loves seeing things done quickly, and it’s hard not to share that specific, visceral thrill of seeing the boundaries pushed so aggressively.

I find myself thinking about the architecture of speed and what it means for the rest of us.

We spend so much of our lives absorbing the lesson that “good things take time.” We are taught that the crucible of meaningful work requires a long, slow simmer. And mostly, that remains true. The compound interest of human experience is real, and wisdom is rarely rushed.

Yet, every once in a while, a new paradigm emerges that doesn’t just accelerate the timeline—it collapses it entirely.

The pioneers cut the agonizingly slow path through the jungle, taking the brunt of the time, the friction, and the missteps. The ones who follow—like xAI, Anthropic, and now MSL—don’t have to clear the brush from scratch. They can look at the map, pave the road, and simply drive.

What does it mean for our own mental models when the timeline from “formation” to “frontier” shrinks from five thousand days to a few hundred?

It is a jarring reminder that the past pace of performance is not a law of physics.

I think about my own assumptions—how often I assume a project, a habit, or a societal shift will take a while, simply because similar things took a while in the past. We anchor our expectations to old geometry.

Meta’s release of Muse Spark is a technical feat, certainly. But the chart itself holds a broader, more human lesson. It’s a visual prompt to constantly re-evaluate our assumptions about how long the impossible is supposed to take.

The future doesn’t always arrive on a comfortable, predictable schedule. Sometimes, it just shows up unannounced, demanding we adjust our stride to keep up.

Categories
Leadership Uncategorized

The Sawed-Off Chair: Hyman Rickover’s Brutal Lesson in Accountability

It sounds like a legend, but it’s true.

If you wanted to command a nuclear submarine in the Cold War U.S. Navy, you first had to survive a personal interview with Admiral Hyman G. Rickover—the uncompromising “Father of the Nuclear Navy.”

In his office sat a notorious wooden chair. The front legs had been deliberately sawed short—several inches in some accounts—causing anyone who sat in it to slide inexorably forward. The seat was often polished slick as glass. While candidates fought to stay upright, Rickover unleashed a barrage of rapid-fire questions on engineering, history, philosophy, and their deepest personal failures. A weak or evasive answer might earn you banishment to a broom closet for hours “to think about it.” Other times, he’d deliberately provoke you just to see how you’d react under pressure.

Why would the man responsible for the most advanced, unforgiving technology of the era—nuclear reactors that could never be allowed to fail—rely on such seemingly petty tactics?

Because Rickover understood a hard truth: technology doesn’t prevent disasters. People do.

A nuclear reactor doesn’t care about your rank, your procedures, or your consensus. It obeys physics.

In an environment where a single mistake could mean catastrophe, Rickover demanded officers who took absolute, personal ownership of every outcome.

He put it best himself:

“Responsibility is a unique concept. It can only reside and inhere in a single individual. You may share it with others, but your portion is not diminished. You may delegate it, but it is still with you. You may disclaim it, but you cannot divest yourself of it… If responsibility is rightfully yours, no evasion, no ignorance, no passing the blame can shift the burden to someone else. Unless you can point your finger at the man who is responsible when something goes wrong, then you have never had anyone really responsible.”

That philosophy is why the sawed-off chair existed. It wasn’t hazing. It was a deliberate test: When your environment is uncomfortable, unfair, and literally working against you, do you complain? Do you slide off and give up? Or do you dig in, brace yourself, and maintain control while thinking clearly under stress?

Rickover wasn’t building bureaucrats. He was building leaders who could be trusted with the most dangerous machines ever created—men who wouldn’t hide behind systems, committees, or “shared accountability” when things went wrong.

Today, in our matrixed organizations, endless committees, and culture of diffused blame, this feels almost radical. We’ve grown comfortable with collective responsibility that conveniently means no one is truly responsible. Rickover called this kind of bureaucratic diffusion “systematic strangulation.”

We may not run nuclear reactors, but the principle applies everywhere that matters: in engineering, in business, in life.

True leadership isn’t about comfort or consensus. It’s about character forged in discomfort. It’s the lonely recognition that the buck doesn’t just stop with you—it starts with you, lives with you, and cannot be outsourced.

Categories
Living

The Geometry of Chaos

“Just for a minute, imagine you’re standing on that aircraft carrier flight deck,” said Caine. “There’s 30 knots of wind in your face. The deck is slippery, covered in grease. It’s noisy. There are propellers spinning. There’s jet blast everywhere. The helicopters are running. Your head is on a swivel and you’re trying to direct a multi-million dollar fighter into a one-foot square box so that those naval aviators can be shot off into the black of night to go do America’s work.”

The world often views precision as a quiet endeavor. We picture the watchmaker in a silent room or the coder in a hushed office, finding clarity through the absence of noise. But General Caine’s description of a carrier deck flips this script. It suggests that the highest form of human precision doesn’t happen in spite of the chaos—it happens within it.

To stand on that deck is to exist in a state of sensory assault. You have the “thirty knots of wind,” the “grease,” the “spinning propellers,” and the “jet blast.” It is an environment designed to overwhelm the nervous system.

Yet, in the center of this metallic purgatory, there is a person—head on a swivel—tasked with moving a multi-million dollar machine into a “one-foot square box.”

There is a profound metaphor here for the modern life. We often wait for the “wind” to die down before we attempt our most important work. We tell ourselves we will start the project, have the difficult conversation, or find our focus once the “noise” of life subsides. But the “black of night” doesn’t wait for the deck to be dry. America’s work—or rather, the soul’s work—is often requested exactly when the deck is most slippery.

The beauty of the flight deck officer is not just their technical skill, but their ability to maintain an internal stillness while the external world is screaming. It is the realization that the “one-foot square” is the only thing that matters, even when the rest of the world is a blur of grease and jet fuel.

We are all, at various points, standing on that deck, trying to guide something precious into position so it can take flight.

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

Categories
Business Living

From Know-It-All to Learn-It-All

Momentum is a strange phenomenon. In physics, it is simply mass times velocity. But in human organizations, it is tradition multiplied by ego. When a ship reaches a certain size, its sheer mass resists any change in direction. Microsoft, a little over a decade ago, was the ultimate corporate supertanker. It was massively successful, incredibly profitable, and dangerously stagnant.

When Satya Nadella took the helm, he inherited a culture defined by its own historic brilliance. They were the smartest people in the room, and they knew it. But in a world moving faster than anyone could comprehend, being the smartest person in the room quickly becomes a liability. It creates a defensive posture. You spend your energy protecting your status and proving your intelligence rather than exploring the horizon.

As the observation goes, Nadella had to turn this bigger ship. His mechanism for doing so wasn’t a massive restructuring or a ruthless wave of firings; it was beautifully, disarmingly simple. He told his organization that they were going to make a fundamental, psychological shift.

“We’re gonna go from being a know-it-all to a learn-it-all culture.”

This isn’t just a corporate soundbite; it’s a profound philosophical pivot. The “know-it-all” operates from a place of fragility and fear. If your identity is built on knowing everything, any new information that contradicts your worldview is a threat that must be neutralized. A “learn-it-all,” however, operates from a place of abundance and curiosity. Contradictions aren’t threats; they are invitations to expand.

Looking inward, it is striking how easily we slip into a “know-it-all” posture in our own lives. Competence is deeply comfortable. When we get good at our jobs, our daily routines, or navigating our relationships, we build a fortress of certainty around ourselves. We stop asking questions because we assume we’ve already mapped the territory. We begin to ossify.

To adopt a learn-it-all mindset requires something deeply uncomfortable: vulnerability. It means walking into a room and quietly accepting that you might be wrong. It means replacing the urge to provide a quick, authoritative answer with the patience to ask a better question. It means letting go of the ego’s demand to be the expert.

The turnaround of Microsoft wasn’t just about a pivot to cloud computing or new product pipelines. It was a quiet victory of humility over arrogance. It was the realization that in an ever-changing world, the ultimate advantage isn’t what you already know, but how fast—and how willingly—you are prepared to learn.

We are all steering our own ships through shifting waters. The moment we decide we have nothing left to learn is the exact moment we begin to sink.

Categories
AI Work

Why IBM is Hiring Beginners

There is a pervasive anxiety humming beneath the surface of the modern workplace—a quiet, collective fear that the bottom rungs of the corporate ladder are being systematically sawed off by artificial intelligence.

The common wisdom, echoed in countless op-eds and boardroom whisperings, is that entry-level jobs are the natural prey of the Large Language Model.

The tasks of summarizing, drafting, formatting, and basic coding are easily consumed by algorithms. If a machine can execute the rote labor of a junior analyst in three seconds, why hire the junior analyst at all?

It is a seductive, mathematically appealing logic, especially in an era of tightening belts and efficiency mandates.

Consequently, we are witnessing a landscape where many tech companies are quietly, or sometimes loudly, slashing their junior roles to lean on AI.

But amidst this trend, an alternative approach emerges that feels almost rebellious in its long-term optimism.

IBM, a legacy titan that has weathered every technological revolution of the past century and where I started my career, is leaning entirely the other way. Rather than cutting, they are reportedly tripling their entry-level hiring.

Reflecting on this strategy, IBM’s chief HR officer noted:

“The companies three to five years from now that are going to be the most successful are those companies that doubled down on entry-level hiring in this environment.”

This perspective is profound because it challenges the very premise of what an entry-level employee actually is.

The prevailing, perhaps cynical, view treats a junior worker merely as a unit of basic output. If you view a beginner only as a spreadsheet compiler or a draft-writer, then yes, they appear redundant in the face of AI.

But what if we view the entry-level role not as a terminal function, but as an apprenticeship?

When we hire a beginner, we aren’t just buying their immediate, unpolished labor. We are investing in a trajectory.

We are bringing them into the fold so they can absorb the tacit knowledge of the organization—the unwritten rules, the cultural nuances, the complex, human art of navigating institutional friction.

An AI cannot learn the subtle interpersonal dynamics of a specific team, nor can it develop the intuition that comes from failing, recovering, and being mentored by a seasoned veteran.

If we automate away the entry-level, we effectively destroy the incubator for our future mid-level and senior leaders. Where will the experienced managers of 2030 come from if no one is allowed to be a beginner in 2026? You cannot suddenly parachute someone into a senior role and expect them to possess the deep, intuitive judgment that is only forged in the crucible of early-career trial and error.

The institutional memory breaks down.

IBM’s strategy recognizes a crucial reality: AI shouldn’t replace the beginner; it should accelerate them.

Imagine a junior employee who isn’t bogged down by mindless grunt work, but instead is handed the tools to instantly bypass the mundane. They can spend their foundational years analyzing, questioning, and engaging in higher-order problem-solving alongside their mentors. They transition from data-gatherers to hyper-learners.

By doubling down on human potential in an age of artificial intelligence, companies are making a strategic bet on the one asset that cannot be replicated by a server farm: the evolving, adapting, and deeply creative human mind.

The most successful organizations of the near future won’t be the ones with the fewest employees and the most algorithms; they will be the ones that used algorithms to cultivate the most formidable, deeply experienced human talent.

The ladder hasn’t been dismantled. It has merely been redesigned.

The only question is whether we have the foresight to keep inviting people to climb it.