Isaacman's Inheritance: A SpaceX Mindset Meets a Legacy Institution
What the discipline of simplification reveals about leadership, culture, and change.
I followed Jared Isaacman’s confirmation hearing to lead NASA with interest. He was pressed on his plan to streamline the agency and move faster, a vision shaped by his time flying SpaceX missions rather than by any background in federal bureaucracy. His message was direct: focus on what matters, remove what does not, and act with the urgency the moment demands. He had logged more hours in orbit than most career astronauts. He had performed the first civilian spacewalk. He was not theorizing about work and process simplification. He’s lived it his entire career.
Some time before that hearing, I had experienced the results of that philosophy firsthand. I joined a Teams call from a remote location over a Starlink connection. No lag. No buffering. It felt like I was sitting in my office. That kind of satellite network performance does not emerge from a bureaucracy. It comes from an organization that has stripped away work and process complexity and built around first principles.
Isaacman comes from that world. NASA does not, at least not yet. Last week, a NASA crew was aboard Orion and completed a flight around the far side of the Moon using the Space Launch System rocket, the first humans to travel that far from Earth since Apollo 17. The mission flew on time. The rocket performed. That is not nothing. It is, in fact, the result of an institution choosing to rationalize a legacy program rather than abandon it, which is harder and rarer than building something new from scratch.
In today’s Dispatch, I contrast the discipline of work and process simplification and lean innovation that made SpaceX what it is with the accumulated bureaucracy and complexity that NASA is now working hard to shed under Jared Isaacman, and ask what either story means for institutions trying to simplify and transform from within.
The big picture
NASA and SpaceX make for a useful contrast in how institutions approach complexity, cost, and change. The contrast is not clean. Jared Isaacman, now confirmed as NASA’s fifteenth administrator, came to the job shaped by his SpaceX experience and the conviction that large institutions can move faster by removing what does not matter. He inherited a 322-foot rocket that embodied nearly everything he had criticized and chose, deliberately, to standardize and fly it to the moon rather than abandon it. Meanwhile, Congress passed NASA a budget exceeding $27 billion for fiscal year 2026, the largest in nearly three decades in real terms. These are not the conditions of a failing institution; they are signs of political capital.
The more useful question is not whether SpaceX’s model defeats NASA’s. It is whether an institution can internalize the discipline of simplification after years of complexity accumulation, and whether political will can sustain that effort long enough to matter. That question is harder and rarer than building a company from scratch. It is also more relevant to higher education, where no one gets to start over.
Max Weber wrote about ideal types not as descriptions of reality, but as analytical tools for understanding the forces that shape political, social, and economic behavior. No organization is purely legal-rational or purely traditional. But comparing institutions to ideal types reveals what motivates both their actions and decisions. SpaceX and NASA remain useful ideal types, not because one succeeded and the other failed, but because they represent two fundamentally different institutional responses to the same problem: how to get work done when complexity accumulates.
Work Simplification at SpaceX
Work simplification is not a slogan. It is a discipline. It forces an institution to examine every step in a process and ask whether it is necessary. Most organizations never do this, either because of internal politics or because they are afraid of what they might find. SpaceX built a culture around it. The result is visible in five lessons that remain instructive regardless of how any particular rocket program turns out.
Every requirement must have an owner. SpaceX attaches a name to every requirement. If no one can defend it, it disappears. This creates clarity and accountability in equal measure. The institutional default, visible in large procurement programs across both government and higher education, is to carry requirements forward without ever asking who still needs them or why. Untraceable requirements are not neutral; they are dead weight.
Delete before you optimize. SpaceX removes steps before improving them. They eliminated hydraulic systems in favor of simpler electric controls. They dropped the complex fairing-catching system after realizing the same results came from simply letting the fairings splash down and retrieving them. The institutional default is to solve problems by adding new layers, which seems like progress. Deletion requires confidence that the original requirement was not worth keeping.
Simplification makes systems more reliable. SpaceX reduces failure by reducing components. The choice of stainless steel over carbon fiber for Starship removed both the heat shield requirement and its intricate manufacturing steps. Reliability through complexity is a contradiction. Every additional component is a new way for a system to fail. Organizations that rely on oversight and controls to ensure quality are managing the consequences of complexity that they did not eliminate.
Vertical integration eliminates friction. SpaceX builds most parts in-house. Teams talk directly. Decisions move fast. The fragmented supply chain model, common in both aerospace and enterprise technology, adds negotiation, delay, and coordination costs at every process step. Those costs are easy to justify individually and hard to see in aggregate until the system stops moving.
Work simplification is a cultural choice, not a technical one. This is the lesson that matters most for institutional leaders. SpaceX built a culture where unnecessary work is treated as a problem to be eliminated. The institutional default is a culture where unnecessary work is invisible and quiet, absorbed into the budget and the calendar by habit and without comment. The difference is not engineering talent or organizational size. It is a decision about what the organization pays attention to.
Work simplification is a way of seeing. It forces an institution to confront what it does and why. That clarity is the precondition for lean innovation to take hold.
Lean Innovation and the Discipline of Constraint
Lean innovation comes from scarcity, but not only from scarcity. More precisely, it comes from the discipline of treating resources as a constraint rather than a permission slip, regardless of how much funding is available. NASA’s current budget offers a useful illustration of why this distinction matters. Congress approved more than $27 billion for fiscal year 2026. That is not scarcity. But if Isaacman allows that abundance to dissolve the pressure for simplification, the same drift that produced a $23 billion rocket program with a ten-year delay will reassert itself quickly.
SpaceX grew up under financial pressure where failure had direct consequences for the company’s survival. That pressure sharpened judgment about what to invest in and what to cut. The lesson for institutions operating in relative abundance is not that they should manufacture artificial scarcity. It is that they need a substitute discipline: the deliberate choice to treat every investment as if the capital were limited, and to measure returns with the same scrutiny that austere conditions would demand.
Four additional lessons follow from the SpaceX example.
Controlled failure accelerates progress. SpaceX flew prototypes, knowing some would explode. Each failure revealed something useful and cheaply. The institutional alternative is to avoid failure at all costs, which typically means designing for perfection from the start, delaying until certainty is within reach, and producing systems that are late, expensive, and still imperfect. When failure becomes organizationally unacceptable, learning slows and costs escalate.
Iteration outruns optimization. SpaceX improves through constant cycles of build, test, and refine. The institutional preference for comprehensive design before implementation is not inherently wrong; it reflects legitimate risk management in high-stakes environments. But it tends to produce systems optimized for the requirements of three years ago, delivered into a changed environment. The discipline of iteration is not about moving recklessly. It is about shortening the distance between assumption and evidence.
Architectural honesty is non-negotiable. SpaceX chose reusable engines because expendable designs were financially unsustainable at scale. The organization confronted that reality and designed around it. Institutional architecture that avoids honest reckoning with cost and sustainability does not make the problem disappear; it defers and compounds it. Higher education is full of architectural decisions that were reasonable when made and have never been revisited.
Innovation flows from constraints, not from comfort. SpaceX made hard tradeoffs. Steel instead of carbon fiber. Simpler systems instead of more capable ones. Lower cost through deletion rather than through engineering. The institutional instinct is to innovate by adding. SpaceX demonstrated that the more durable advantage comes from subtracting what does not add value.
Lean innovation is the discipline of doing less, better. It is not frugality for its own sake. It is strategic austerity that channels effort toward what matters.
What NASA Is Learning, and Why That Matters More
The story that deserves attention is not SpaceX’s continued success. It is what NASA under Isaacman is attempting to do with a legacy program that was already built.
Isaacman standardized the SLS design to enable a more predictable cadence of flights. That is Lesson Two in practice: delete non-value-added activities and handoffs before you optimize. He publicly named the failure modes in the Starliner program and held the institution accountable. That is Lesson One: every requirement, and every decision, must have an owner. He is pursuing a multi-vendor launch strategy that introduces competition into a procurement culture that had operated without it. That is a structural intervention in the economic conditions that produce drift.
None of this is as elegant as starting from scratch. Legacy architecture does not submit gracefully to simplification. The requirements that have accumulated over decades each have defenders, and those defenders have political relationships. Progress in this environment depends on negotiation, credibility, and accrued trust that lowers the temperature enough for people to let go of what no longer serves them. That is a different kind of leadership challenge than building a rocket company.
This is the more useful lesson for higher education leaders, because it is the situation they actually occupy. No project ever starts with a clean slate. ERP projects, infrastructure investments, academic technology decisions, and organizational redesigns all begin with inherited constraints, established stakeholders, and requirements that no one can quite explain but everyone seems to depend on. The discipline that SpaceX practices from inception has to be applied in higher education retrospectively and incrementally, against resistance, in an environment where failure is organizationally unacceptable and consensus is required for any change.
That is harder than what SpaceX does. It is also what the job requires.
The final word
The SpaceX model offers durable lessons about work simplification and four more about lean innovation. Those lessons apply to any institution attempting change, including universities undertaking ERP modernization, technology consolidation, or organizational redesign. But the harder and more instructive example may now be NASA itself: a legacy institution with an inherited program, a new leader shaped by a different model, and the deliberate choice to simplify rather than abandon what exists.
The real barrier in higher education is not technical. It is political. Internal politics can overwhelm even the best-designed transformation. Progress depends on negotiation, relationships, and the slow accumulation of trust that makes it possible for people to release requirements they have protected for years. Those things matter little in a private rocket company. They are everything in a public institution. The leaders who understand both the discipline of simplification and the patience that institutional change requires are the ones most likely to get somewhere worth going.