Think in Limits
Set a target at the physical limit of what is theoretically possible, then work backwards toward it, instead of setting it as a percentage improvement over what already exists. The standing reply to an objection is not to argue, but to ask what would have to be true.
The discipline underneath first principles
First-principles reasoning tells you how to reason; thinking in limits tells you where to aim before reasoning even starts. The move is to refuse the comparative frame entirely, never asking how to be ten or twenty percent better than what already exists, but instead asking what the absolute physical limit of a given thing could be and how close it is possible to get to that. The target gets called the platonic limit, or the strong form of the technology, and the corollary is that you have to start from a clean sheet, because the moment an existing design is adapted, its ceiling gets imported along with it. Musk names his own violation of the discipline: building the first Roadster on a Lotus chassis.1 The limit being aimed at is physics, and only physics, on the reasoning that physics is a law and everything else is a recommendation, so the only useful question becomes: show the specific law of physics that makes this impossible, not whether anyone has done it before, or what current methods allow, or which analogy seems to apply.
The two-phase tactic
Thinking in limits is not useful if an organization only treats the limit as rhetoric, so a specific, repeatable procedure keeps the discipline honest. First, propose something within the absurd, actively throwing out the idea that sounds insane on its face. Second, convert the objection into a specification: when people say an idea is crazy, the reply is not an argument, it is a reframe, don't tell me no, tell me what would have to be true, turning a refusal into a list of concrete requirements. Third, buy a day or a week for the team to design the idea under the working assumption that it is actually possible, and see how far they get. Fourth, wait for the churn, since dismissal on day one reliably turns into "wait, this might be possible" within roughly a week. The reframe in the second step is the load-bearing part: no ends a conversation, while what would have to be true converts a refusal into a list of requirements, many of which usually turn out to be softer than assumed once actually questioned.1
Worked cases
Catching a returning rocket became possible by thinking to the limit of reusability: landing legs add mass, must be shielded through re-entry, and leave a large rocket sitting somewhere other than the launch stand, so the aircraft analogy, land and immediately take off again, suggests catching the rocket on the launch tower itself using mechanical arms, an idea described by its own originator as sounding completely absurd in the initial discussion before it was actually built.1 Choosing steel over carbon fiber for a rocket body followed the same logic: carbon fiber is expensive, hard to work with, and needs a large industrial oven to cure, while steel gains strength at low temperatures, making the vehicle stronger once it is actually in orbit, and can be welded in a tent in a parking lot rather than a specialized facility, a material choice that fell directly out of asking what physics permits rather than what the existing aerospace industry does by convention. A weld-thickness spec came from asking the people actually doing the welding rather than trusting the engineering drawing: they said 4.5 millimeters was where it got sketchy, so the team tried 4 millimeters, and it held up in practice. And a giant casting technique for vehicle manufacturing came from studying toy cars, cheap, reliable, and scaled, even though nobody had previously built casting machines that large, and of six companies capable of building such a machine, five said no and one said maybe, with that maybe treated as a yes.1
Relationship to other concepts
Musk Algorithm sets the process for getting to a target once thinking in limits has set that target; the two interlock at the first step of the algorithm, since a limit-based target makes almost every inherited requirement look questionable, which is exactly the mental state the algorithm needs before it can work. The Idiot Index applies the same instinct to cost, setting a price target at the floor of raw-materials cost, the physical limit of what a part can cost to make. And Simplicity as Distillation is a useful tension to hold alongside this: one tradition reaches simplicity by understanding an essence deeply enough to strip everything else away, while this discipline reaches it by pushing designs and materials to the point of failure and reading the answer off the wreckage, insight versus demolition arriving at the same destination by different roads.
Open question
The loop described here has a survivorship problem it does not resolve on its own: keep trying, show me why it is impossible is, from inside the room, indistinguishable from a founder who is simply wrong and happens to outrank everyone else. The catching-the-rocket story gets told because it worked, and there is no equally well-documented case of the same pressure applied to something that genuinely was impossible, nor any account of how the loop is supposed to terminate when the honest answer really is no.
Practiced by
Connections
Loading connections…
References
- 01
Eric Jorgenson · podcast · 2026
Related