Does Proactive Design Still Mean Anything in a Random World?

Nassim Taleb says the world is mostly random, full of Black Swans and pure chance, so trying to predict things is a waste of time. Then Peter Thiel, in Zero to One, says great companies are all about careful, deliberate design. So, which is it? If the world’s a crapshoot, why bother designing anything?

The confusion probably starts with what we mean by “design.” We often think of a perfect blueprint, a detailed plan we follow step by step to a known future. If that’s design, then yes, in a random world, it’s mostly useless. But real design might be something else: building a system that can handle shocks, maybe even get stronger from them, which is what Taleb calls “antifragility.”

Look at Apple

Steve Jobs’ Apple is a good way to see this. It’s easy to think Jobs had a crystal ball for tech trends. I doubt it. What Apple got good at was designing a super flexible ecosystem. The App Store is a classic case. Apple didn’t know which apps would win. They didn’t have to. They just built a platform where thousands of developers could try things out for millions of users, and the good stuff rose to the top. So when smartphones became media players, wallets, or AR viewers, Apple didn’t need to see it all coming, because their ecosystem was built to let these things happen and they were set up to benefit from whatever came next. I bet this came from a deep grasp of antifragile ideas. Jobs didn’t try to nail down one future; he designed for many possibilities by building in options.

Simplicity is another way to be antifragile. Complex things break easily: more features and more parts mean more ways for things to go wrong, especially when something unexpected happens. Early smartphones with all their buttons looked clunky fast as new apps appeared, while Apple’s simple multi-touch screen could handle almost anything. Same with code: tangled code is a disaster when things change, and simple, modular code adapts. Apple often designed by removing stuff, and not just for looks. A simpler product gives unforeseen problems fewer places to hide, and it’s nimbler when the world changes. It’s smart defense, and it leaves room for whatever the future brings.

And Jobs bet on things that don’t change much: people like beauty, ease of use, things that just work. Technology zips along and is hard to predict, but what people find elegant changes slowly, so betting on those constants is antifragile too.

Building it, then riding it

These antifragile systems don’t just happen. Building them takes two kinds of effort, often at different times. First there’s the sheer force of creation. To build something powerful and antifragile from scratch, like Apple’s ecosystem or any company, takes a huge, almost unreasonable push. This is Sam Altman’s “willfulness,” the “zero to one.” You need almost crazy self-belief when everyone else says it won’t work, and you have to grind and push through to make an idea real. Altman notes that the most successful founders often believe in themselves to the point of delusion, think for themselves, take risks, and focus intensely. They know that creating something worthwhile often means failing a lot to get one big win, and that you can’t just wait for luck when you’re starting with nothing. “Design” at this stage is messy and iterative, and it runs on grit.

Then there’s strategic patience: riding the wave. Once you’ve built your antifragile system, if you get lucky and catch a giant wave (like Apple did with mobile and apps), the smart move might change. This is where what I call strategic stillness comes in. Consider Cisco. The founders, Sandy Lerner and Leonard Bosack, did the brutal work of building something new: routers, back when networked computers were just starting. They fought through startup hell and got rejected by VCs endlessly, but they finally launched, and Cisco went public in 1990. Conflicts with the new management followed, and they sold most of their stock for about $170 million. That sounds like a great outcome, but the internet was about to explode, something few could really see in 1990. Cisco’s stock shot up nearly a thousand times by 2000, and that $170 million could have been tens of billions. They nailed the creation part. Holding on and letting that massive wave of compounding do its thing is a different game, and often a harder one.

Strategic stillness means seeing that what you’ve built, plus the trend it’s on, has its own momentum, and that too much meddling at this point can actually hurt. Your initial design did its job; now the design and the trend need time to compound. Founders or investors who sell out of huge successes too early, like Cisco’s founders, are often masters of that first, willful creation, but they may stumble on strategic patience. Maybe the exhaustion of building, the daily battles, blinds them to the slower, massive opportunity that just needs time. They grab the sure thing now and miss a far bigger, if less certain, payoff later.

A tough, adaptable ship

So, back to the first question: design matters a lot in a random world. What matters is building a flexible setup that keeps benefiting from surprises, and that takes both the will to build it from nothing and the patience to let it compound once it has momentum. Apple’s story has both: Jobs’s early, forceful drive, and the later ecosystem that grew on everyone else’s work into a compounding machine.

In a world that keeps surprising you, what you design is mostly how you make things and how you adapt. You stop trying to fight randomness and learn to work with it, maybe even use it. Instead of drawing a perfect map, you build a tough, adaptable ship, and learn when to raise the sails and when to drop anchor. Whether you’re building a startup, investing, or just living your life, the most important design might be how you design your way through uncertainty.