Ch10 01: When Growth Stalls, the Algorithm Becomes a Survival Kit#

In 1908, Henry Ford rolled out the Model T and changed the world. Not because the Model T was the finest car ever made — it wasn’t. Not because Ford was the most visionary entrepreneur of his era — that’s debatable. He changed the world because he built a system.

Ford’s assembly line was the Algorithm of its age. It took a process that was slow, expensive, and chained to skilled craftsmen, and turned it into something fast, affordable, and repeatable. The five principles were all there, even if Ford wouldn’t have labeled them this way: he questioned every assumption about how cars should be built, deleted unnecessary complexity, simplified each worker’s task to a single repeatable motion, accelerated flow through the moving line, and automated wherever the technology of his day allowed.

The result was a car that cost $850 in 1908 and $260 by 1925 — an order-of-magnitude leap that put automobiles within reach of ordinary families. Ford didn’t just build a car. He built a system for building cars. And the system was worth more than any individual car it produced.

But here’s the part of the Ford story that matters most for us: the system that made Ford dominant eventually made Ford vulnerable. The assembly line worked so brilliantly that Ford refused to touch it. “Any customer can have a car painted any color that he wants so long as it is black,” he famously declared. That wasn’t a punchline. It was a philosophy — one that treated the system as finished rather than evolving.

General Motors, under Alfred Sloan, grasped what Ford didn’t: the system itself must be continuously improved. Sloan introduced model years, customer segmentation, and design variation — not just better cars, but a better process for making and selling cars. By the 1930s, GM had passed Ford. Not because GM’s vehicles were fundamentally superior, but because GM’s system was more adaptive.

This is the deepest lesson of the Algorithm, and the one I want to leave you with: the Algorithm is not a destination. It’s an operating system. And operating systems must be continuously updated.

Apply the five steps once — question, delete, simplify, accelerate, automate — and you’ll get a significant improvement. Maybe a dramatic one. But if you stop there, you’ll eventually become the next Ford. Your optimized process will harden. Competitors will close the gap. The market will shift. And the system that once gave you an edge will become the cage that traps you.

The organizations that thrive over decades aren’t the ones that find the best process and fortify it. They’re the ones that build the capacity to continuously find better processes — to question their own assumptions, delete their own waste, simplify their own complexity, accelerate their own cycles, and automate their own routines, again and again, without end.

I call this a meta-capability — the ability to produce methods, not just execute them. A specific method — “our production process” or “our onboarding flow” — has a shelf life. It was designed for specific conditions, and when those conditions shift, the method goes stale. But the ability to redesign methods — to run the Algorithm against whatever challenge shows up, under whatever conditions you face — never expires. It’s permanently valuable because it’s permanently adaptive.

The urgency of this message has never been higher. Change is accelerating on every axis — technology, competition, regulation, customer expectations. The average lifespan of an S&P 500 company has dropped from sixty-one years in 1958 to fewer than eighteen today. Companies are being born faster, scaling faster, and dying faster than at any point in economic history.

In this environment, there’s a simple survival equation:

If your rate of improvement outpaces the rate of environmental change, you’re evolving. If it doesn’t, you’re dying — even if today’s numbers look fine.

This is the most dangerous form of decline: the kind that’s invisible in quarterly earnings. The company is profitable. Customers are still buying. The stock price is steady. But underneath, the gap between how the organization operates and what the environment demands is widening. By the time the gap shows up in the financials, it’s usually too late to close.

The Algorithm is insurance against this invisible decline. Not because it guarantees a specific result, but because it keeps the system in motion. Keeps questioning. Keeps deleting. Keeps simplifying. Prevents the calcification that turns today’s advantage into tomorrow’s anchor.

I want to close on a personal note.

I’ve spent my career inside some of the most intense, demanding, exhilarating organizations on the planet. I’ve watched the Algorithm transform companies, careers, and industries. I’ve also watched it fail — usually when people applied it mechanically without grasping its spirit, or when leaders lost the discipline to sustain it.

The Algorithm is not magic. It’s work. Hard, relentless, sometimes unglamorous work. It asks you to question things you’d rather accept, delete things you’re attached to, simplify things you’ve spent years making elaborate, speed up things you’re comfortable doing slowly, and automate things you’d rather keep doing by hand.

But here’s what I know from lived experience: it works. In electric vehicles and insurance startups. In athletic apparel and restaurant technology. In investment management and mobile car repair. In teams of five and organizations of five hundred thousand. The contexts differ. The principles hold.

You now have the full operating system. You understand the five steps and why sequence matters. You understand the cultural infrastructure — the heartbeat, the stage gates, the leadership by example, the dog-fooding — that keeps the engine running. You understand the deeper dynamics: how constraints are spectrums, how simplification unlocks creativity, how problems get redefined when enough constraints are stripped away, and how the system itself must evolve to stay relevant.

The only question left is whether you’ll install it.

I’m rooting for you.

Guidance#

Here’s your starting checklist. Not a plan for next quarter. A plan for next week.

Monday: Pick one process. The most important one. Measure its cycle time and touch time. Calculate the gap.

Tuesday: List every assumption baked into that process. Circle the three oldest. Question them.

Wednesday: Delete one step. The one no customer would pay for. Just remove it and see what happens.

Thursday: Simplify one step. Compress it to half its current complexity. Run the newbie test.

Friday: Review what you learned this week. Write down one thing that surprised you.

Next Monday: Do it again. Pick the next process, or go deeper on the same one. The cycle never stops — and that’s the point.

The Algorithm isn’t something you do once. It’s something you become. An organization that questions, deletes, simplifies, accelerates, and automates — continuously, systematically, relentlessly — is an organization that can survive anything.

Start now. Start small. Start imperfect. But start.