Pirate vs Navy

I’ve sat in both kinds of rooms, and you can usually tell which one you’re in within about four minutes.

In one room, somebody says “let’s just try it and see what happens” and everyone nods and the conversation moves on. In the other room, somebody says the exact same sentence and there’s a short, polite pause, and then a person asks who would own it.

Neither room is stupid. That took me an embarrassingly long time to figure out.

The quote everyone knows is Steve Jobs in 1983, telling the Macintosh team it’s better to be a pirate than to join the navy. They actually ran a Jolly Roger up the flagpole over their building. Great story, gets repeated in every startup pitch deck for the last forty years, usually by someone who wants you to believe that his eleven-person company is spiritually superior to a bank.

And the way that quote gets used is almost always lazy. Pirates good, navy bad, rules are for cowards, ship it Friday. I’ve said versions of that myself and I’d like some of it back.

Because the actual interesting thing isn’t that pirates are better. It’s that a pirate ship and a navy fleet are solving two completely different problems, and each one looks insane if you score it using the other one’s scorecard.

What a pirate is actually optimising for

A pirate ship’s problem is: stay alive long enough to hit one big score.

That’s it. That’s the whole business model. You don’t have a treasury. You don’t have a reputation to protect because nobody knows who you are and nobody would trust you anyway. You have a boat, some people who are angry enough to be here, and a limited runway before the food runs out.

Which means variance is your friend. A wild swing that works ten percent of the time is a rational bet when the alternative is starving slowly. You should take risks that look reckless to an outsider, because “safe” for you means guaranteed death, just later.

This is why small teams move the way they do. It isn’t courage and it isn’t culture. It’s arithmetic. When you have nothing, the downside of a bold move is roughly the same as the downside of a careful one, so you may as well swing.

I think a lot of startup mythology gets this backwards. Founders are not braver than corporate managers. They’re just playing a game where bravery is cheap.

What a navy is actually optimising for

A navy’s problem is the opposite: don’t lose the fleet.

The navy already has the treasure. It has ports, supply lines, a hundred thousand people whose salaries depend on ships coming home. Its job is not to find gold. Its job is to make sure the gold that already exists keeps flowing, on schedule, boringly, forever.

For that problem, variance is the enemy. A captain who does something brilliant and unauthorised and wins is a problem, not a hero, because you cannot build a fleet out of people who might do something brilliant and unauthorised and lose. Consistency at scale beats genius in a single ship. That’s not cowardice. That’s the correct answer to the question they’re actually being asked.

The thing that finally made this click for me: every process in a large company is a scar.

Somewhere, at some point, something went badly wrong. Money vanished, a customer got hurt, a regulator showed up, somebody got sued. And the organisation did what organisms do, which is grow tissue over the wound so it can’t happen again. Ten years later a new joinee looks at that form with fourteen fields and thinks these people are idiots. He’s not wrong that it’s slow. He’s wrong that it’s arbitrary. He just wasn’t there for the injury.

Young companies mock rules they’ve never needed. That’s not insight. That’s just being young.

And now the part where I stop being fair

All of that said, both models rot in extremely predictable ways.

The navy’s rot is that scars outlive the wound. The threat that justified the rule disappeared in 2009 and the rule is still there in 2026, being enforced by people who’ve never asked why. Nobody in the history of corporate life has been promoted for deleting a policy. The incentive is entirely one-directional: adding process is prudence, removing it is risk. So the tissue keeps growing until the organisation can’t move its arms.

You can spot it easily enough. Ask why something is done a certain way and count how many people you go through before someone actually knows. If it’s more than three, that rule is a fossil.

The pirate’s rot is the mirror image, and honestly it’s the one I have more sympathy for and less patience with. The scrappiness that got you from zero to something becomes an identity, and identities are hard to give up. So you keep celebrating being a pirate long past the point where you have a fleet to protect. Everything is a heroic scramble. Nothing is written down. The founder is still personally approving invoices at two hundred crore in revenue because delegation feels like betrayal.

I’ve watched teams die of this. Not from moving too fast, from refusing to learn a second gear.

Why corporate innovation labs mostly don’t work

This is the bit I’ll get pushback on, and fine.

Big companies figured out they wanted pirate energy, so they built pirate zones. Innovation labs, skunkworks, digital transformation offices, a floor with beanbags and a whiteboard wall and, I promise you, an actual pirate flag somewhere.

It almost never works, and the reason is boring: they gave people a pirate flag and a navy pay structure.

If failing at your bold experiment means your career takes a hit, and succeeding means you get a certificate and a mention in the town hall, then you will behave like a sailor no matter what’s flying over your desk. Every single time. People are not stupid. They read the payoff matrix, not the culture deck.

Real pirates got a share of the prize. That’s the entire mechanism. Not the flag, not the vibe — the share. If you want people to take asymmetric risk, you have to give them asymmetric upside, and most large organisations are structurally incapable of doing that, because giving one team asymmetric upside is exactly the kind of variance a navy exists to prevent.

So the lab produces PowerPoints. Everyone is confused about why. Nobody wants to say the real reason out loud in the room.

The ending nobody quotes

Here’s the part of the Jobs story that never makes it into the pitch deck.

The pirate ship got absorbed. Jobs got pushed out of his own company two years after that flag went up. And when he came back and Apple became the most valuable company in the world, it did so on the back of one of the most disciplined, ruthless, boring supply chain operations ever assembled, run by a man whose entire genius was logistics.

The pirate built a navy. That was the actual win. Not the flag.

I don’t think there’s a neat lesson in that, and I’m suspicious of essays that end with one. The best I’ve got is that “pirate or navy” is the wrong question, and the useful one is: what problem am I actually solving right now, this year, with these people?

If the honest answer is “we might not exist in eight months,” then stop writing process documents and go swing at something.

If the honest answer is “we’re fine, we’re just slow,” then your problem isn’t a lack of courage. It’s that you’re carrying scar tissue from injuries nobody remembers, and somebody needs to do the deeply unglamorous work of cutting it out. Nobody will thank you for it. Do it anyway.

The flag doesn’t matter. The payoff matrix does.