Tag: management

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
AI Programming Prompt Engineering Software Work

The Great Inversion

For twenty years, the “Developer Experience” was a war against distraction. We treated the engineer’s focus like a fragile glass sculpture. The goal was simple: maximize the number of minutes a human spent with their fingers on a keyboard.

But as Michael Bloch (@michaelxbloch) recently pointed out, that playbook is officially obsolete.

Bloch shared a story of a startup that reached a breaking point. With the introduction of Claude Code, their old way of working broke. They realized that when the machine can write code faster than a human can think it, the bottleneck is no longer “typing speed.” The bottleneck is clarity of intent.

They called a war room and emerged with a radical new rule: No coding before 10 AM.

From Peer Programming to Peer Prompting

In the old world, this would be heresy. In the new world, it is the only way to survive. The morning is for what Bloch describes as the “Peer Prompt.” Engineers sit together, not to debug, but to define the objective function.

“Agents, not engineers, now do the work. Engineers make sure the agents can do the work well.” — Michael Bloch

Agent-First Engineering Playbook

What Bloch witnessed is the clearest version of the future of engineering. Here is the core of that “Agent-First” philosophy:

  • Agents Are the Primary User: Every system and naming convention is designed for an AI agent as the primary consumer.
  • Code is Context: We optimize for agent comprehensibility. Code itself is the documentation.
  • Data is the Interface: Clean data artifacts allow agents to compose systems without being told how.
  • Maximize Utilization: The most expensive thing in the system is an agent sitting idle while it waits for a human.

Spec the Outcome, Not the Process

When you shift to an agent-led workflow, you stop writing implementation plans and start writing objective functions.

“Review the output, not the code. Don’t read every line an agent writes. Test code against the objective. If it passes, ship it.” — Michael Bloch

The Six-Month Horizon

Six months from now, there will be two kinds of engineering teams: ones that rebuilt how they work from first principles, and ones still trying to make agents fit into their old playbook.

If you haven’t had your version of the Michael Bloch “war room” yet, have the meeting. Throw out the playbook. Write the new one.

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.

Categories
AI Work

The Rungs We Leave Behind

“Companies, too, must prepare. To thrive they need not only to make the best use of ai, but also to find and nurture the best people to work with it. Some back-office workers will lose their jobs. But others with tacit knowledge of the business may be trained for new roles. The biggest mistake would be to stop hiring young people altogether. That would not only choke off the pipeline for future talent, it would rob businesses of AI natives. Instead, companies should rethink the type of work they offer young people—less grunt labour, more judgment and analysis; speedier rotations across the business so they gain insight that ai cannot have; piloting new roles and trying new approaches.”
— The Economist

There is a specific kind of quiet panic in boardrooms today. It isn’t just about the bottom line; it’s about the lineage of knowledge. For decades, the “entry-level” role served a hidden purpose. It wasn’t just about getting the spreadsheets done; it was about osmosis. By doing the “grunt labor,” a young professional absorbed the culture, the politics, and the subtle, unwritten rhythms of an industry—what we call “tacit knowledge.”

We often view AI as a replacement for the “boring stuff,” but we forget that the boring stuff was the soil in which expertise grew. If we remove the bottom rungs of the ladder because a machine can climb them faster, how do we expect anyone to reach the top?

The shift from “labor” to “judgment” is a profound psychological leap. We are essentially asking 22-year-olds to skip the apprenticeship of execution and move straight into the apprenticeship of discernment. This requires a radical empathy from leadership. We cannot simply hand a junior employee a powerful AI tool and expect them to know what “good” looks like if they’ve never seen “bad” up close.

The “AI native” brings a fluidity with technology that my generation might never fully replicate, but they lack the scars of experience that inform intuition. To thrive, companies must become teaching hospitals rather than just production factories. We need to create “judgment-rich” roles where young people are encouraged to experiment, to fail safely, and to rotate through the business at a pace that keeps them ahead of the automation curve.

The disruption is here. It is unavoidable. But there is a soulful middle ground: using AI to strip away the drudgery while doubling down on the human mentorship that transforms a “worker” into a “leader.” The goal isn’t just to make the best use of AI; it’s to ensure that when the AI provides an answer, there is still a human in the room with the soul and the context to know if that answer is right.

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 Leadership

The Power of Two

I recently watched and thoroughly enjoyed Harry Stebbings’ interview with OpenAI’s Sam Altman (CEO) and Brad Lightcap (COO). In addition to gaining new insights into OpenAI’s evolution, their conversation covered a wide range of topics regarding the future of AI and its implications for society and new ventures.

One of the most fascinating aspects was the dynamic between Altman and Lightcap — hearing them discuss their respective strengths, weaknesses, and how those translate into their roles at OpenAI. It’s uncommon to witness a dual interview like this, with two colleagues who have clearly worked together for years and have complete confidence and trust in each other’s judgment and insights.

Throughout my involvement with various small companies, I wish I could have experienced such a powerful duo! In my experience, it’s not uncommon for the CEO to dominate the senior management team’s dynamics. While this sometimes works well, I’ve also seen it lead to reduced performance or frustration among senior managers due to the CEO’s actions.

Altman and Lightcap (and OpenAI by extension) appear to have a much more synergistic working relationship — effectively amounting to a co-equal division of responsibilities. I highly recommend watching this conversation for anyone involved in a startup aiming to scale quickly and effectively! Congratulations to Harry Stebbings for his hosting this excellent conversation with two key individuals leading the evolution of AI!