strategic impatience

There's an old European folktale about a group of hungry travelers who arrive in a village. The villagers, suspicious of strangers, hide their food and lock their doors. The travelers don't beg for food. Instead, they set a large pot of water over a fire in the town square, drop in a single stone, and begin stirring with great ceremony.

A curious villager approaches: What are you making?

Stone soup. It's delicious, though it would be even better with a little cabbage.

Someone fetches cabbage. Then another villager offers carrots. Then potatoes. Then seasoning. By evening, the whole village is eating together: a feast conjured from a stone and a performance.

The travelers had nothing except the nerve to begin and the faith that beginning would produce what planning never could.

I've been thinking about this story as a manual for building things.

Here is what most people believe about starting something: that there is a minimum threshold of readiness — of knowledge, resources, timing, talent — below which it is irresponsible to begin. That starting before you've crossed that threshold is reckless. That the responsible thing is to prepare.

This belief is wrong. The "readiness trap" is one of the most expensive mistakes a person or a company can make because preparation has a shadow side. Past a certain point, preparation is no longer in service of the work. It is in service of your anxiety. It becomes the thing you do instead of the thing you're afraid to do, while maintaining the pleasant illusion that you are making progress.

Drew Houston wanted to build a file-syncing tool. He had neither a product nor a team. What he had was a three-minute screen recording showing a concept. He posted it online. The beta waitlist went from 5K to 75K people overnight. The video was a stone in a pot. But it generated more signal about demand, about positioning, about what people actually wanted than six months of "preparing" in a room would have.

There is a deeper reason why starting before you're ready works, and it's not just about speed or hustle or "bias toward action".

It's about the nature of knowledge itself. Some knowledge can only be generated by contact with reality. You cannot think your way to it. You cannot read your way to it. It is produced exclusively by the collision between your idea and the world's reaction to it — and that collision requires you to do something visible, i.e. to put the stone in the pot.

I want to draw a distinction here, because I am not making an argument for chaos.

There is a difference between recklessness and what I'll call strategic impatience. Recklessness is closing your eyes and jumping. Strategic impatience is opening your eyes, acknowledging that you can see about ten feet ahead and no further, and walking those ten feet — because you understand that the eleventh foot only becomes visible after you've taken the first ten steps.

The strategically impatient person does not ignore risk. They have a different model of where risk actually is. The naive model says risk is in action — in launching too early, in being wrong publicly, in failing. The more sophisticated model says the greater risk is in inaction — in the slow atrophy of conviction that comes from waiting for conditions that never arrive.

The cost of starting has never been lower. Cursor went from $1M to $500M in ARR with fewer than fifty employees. The efficient size of a company is collapsing. The resources you once needed to begin — capital, talent, infrastructure — are being replaced by tools that didn't exist three years ago. Which means the only remaining barrier to starting is psychological: the belief that you need permission, from the market, from an expert, from some inner feeling of readiness, before you're allowed to begin.

You don't. You never did. But now you really don't.

Frankly, this essay is partly a letter to myself. My natural instinct is to prepare. To plan. To build the framework before building the thing. To read one more book, have one more conversation, gather one more perspective. And preparation has its place.

But I've learned that preparation becomes a liability the moment it starts substituting for action. That there is a particular kind of procrastination — sophisticated, intellectual, highly productive-feeling — that is more dangerous than the lazy kind, precisely because it doesn't feel like procrastination at all. It feels like diligence. It feels like you're getting ready.

You are not getting ready. You are getting comfortable with the idea of getting ready, which is a very different thing.

The travelers in the folktale just performed. They created a visible, public, slightly ridiculous spectacle — boiling a stone — and that performance accomplished something that no amount of planning could have. It created a surface for the world to respond to. It gave the village a reason to show up.

The most important things are built by people who started before the conditions were right — for they understood something that cautious people miss: that readiness is a state you create by moving.

The stone in the pot is a declaration. It says: I have begun. And that declaration, more than any plan or approval or product, is what draws the world to your fire.

Drop the stone. Light the fire.

The village will come.

Onward,
Abhi