Physics By Falling

by Joshua Routh

The Physics I Never Learned in a Classroom

I am not a scientist. I was never the kid acing physics class. I did enough to get by, then moved on.

What I did not realize until much later is that I spent years studying physics anyway.

Every juggling pattern is an exercise in gravity, momentum, timing, and prediction. Drop a club and the room tells you exactly which law you broke.

Every acrobatic catch depends on center of mass, force, and trust that the math works even when you cannot calculate it in the moment. There is no time to solve for x. There is only the catch or the fall.

Every sword swallow relies on understanding your own body well enough to respect its limits. Anatomy stops being an abstraction the moment the margin for error runs down your throat.

I never learned physics with equations. I learned it by dropping clubs, falling off unicycles, and getting back up in front of an audience who paid to watch me try again.

I just finished reading Project Hail Mary by Andy Weir. On the surface it is a book about a lone scientist who wakes up with no memory, on a spaceship, tasked with saving humanity through chemistry and physics done under brutal pressure. It is a book that loves science the way I love a good triple pass.

But the part of the story that has stayed with me longest has almost nothing to do with orbital mechanics. It is about a woman named Eva Stratt.

The Administrator Who Broke the System to Save It

Stratt is a Dutch administrator placed in charge of humanity’s entire response to an extinction-level crisis. Governments recognize early that the normal machinery of international cooperation, the committees, the treaties, the careful jurisdictional lines, moves far too slowly for a threat with a countdown clock attached to it. So they hand Stratt extraordinary authority. She can command resources, override laws, seize technology, and compel cooperation across borders that normally take decades to negotiate.

Weir presents bureaucracy two ways at once, and both are true at the same time.

Bureaucracy is the obstacle. Governments protect jurisdiction. Scientists defend their institutions. Corporations guard intellectual property. Legal systems demand procedures that a crisis with a deadline cannot accommodate. Stratt cuts through all of it. She does not ask people to volunteer. She tells them what they will contribute. That authority is the only reason the mission moves fast enough to matter.

Bureaucracy is also, underneath the friction, the thing that actually builds the ship. The Hail Mary mission requires governments, laboratories, manufacturers, military logistics, engineers, and thousands of specialists coordinating in sequence. Stratt does not eliminate bureaucracy. She turns it into a single machine and removes the normal limits on who gets to run it.

Here is where the story stops being comfortable.

Stratt’s decisions grow more coercive as the stakes rise. She controls information. She manipulates people. There is a decision she makes late in the book, involving one person in particular, that I will not spoil here. If you have read it, you already know exactly what I mean. If you have not, I will just say this: she crosses a line most of us would call unforgivable, and the book asks you to sit with that instead of resolving it neatly.

That is the trade at the center of the story. Humanity may need decisive leadership to survive something this large. But concentrated power still carries a human cost, even when it works. Stratt is effective precisely because she is willing to do things that democratic institutions exist to prevent. She accepts that history may judge her harshly, as long as there is still a civilization left standing to write that history.

The System Still Needs a Person Willing to Answer For It

I keep coming back to that tension because I see a version of it in almost every organization I speak to.

Companies build systems to survive scale. Processes, approvals, metrics, layers of review. Most of the time those systems exist for good reason. They protect people from bad decisions made in a hurry. But every system has a Stratt moment eventually, a point where the process is too slow for the problem in front of it, and someone has to decide whether to follow the procedure or fix the thing that is actually breaking.

AI is accelerating how often organizations hit that moment. Leaders are being asked to move at a pace that outstrips the committees built to slow them down. The temptation is to believe the answer is always more speed, more override, more Stratt. Cut through it. Tell people what they will contribute instead of asking.

But Weir does not let Stratt off easily, and neither should we let ourselves off easily when we lean on that instinct at work. The uncomfortable question underneath her story is whether saving everyone can justify sacrificing the rights of one person. Most of us will never face a decision that dramatic. We will face smaller versions of it constantly: whether the deadline justifies skipping the conversation, whether the target justifies ignoring the person who raised a concern, whether efficiency justifies treating a human being like a resource to be allocated rather than a person to be consulted.

Here is what the book got right that most workplace conversations about systems miss. It is never bureaucracy versus people. It is never AI versus humanity. Stratt does not win because she abandons the system. She wins because she becomes a single point of human judgment inside a system too large to have one. Someone still has to decide. Someone still has to be accountable for the decision. Someone still has to answer for what it cost to get the ship off the ground.

That is the part no algorithm and no org chart can do for you.

As a performer, I learned physics by falling in front of people who trusted me to get back up.

As a speaker, I stand in front of rooms full of smart, capable people building smart, capable systems, and I remind them of one thing they already know but keep forgetting to act on.

Every system in that book runs on thrust, on trajectory, on the physics of getting a ship from one point to another. Weir understood the math well enough to make it feel real. But the thing that actually holds the mission together, the thing no equation on that ship can solve for, is the same thing I close every keynote with.

You matter.