Why Simplicity Wins: Lessons from SpaceX and the Drift Into Complexity

Olivia Carter

Alright Mark, let’s start by talking about something that really jumped out at me reading Timothy Chester’s Substack on SpaceX. It’s this idea of the institutional drift into complexity, right? Like, with Boeing’s SLS program—he calls it the “as-is” condition. There’s just layer after layer of legacy rules, requirements, committees. Nobody can quite remember how half the stuff got there, and somehow all this complexity becomes something, well, nobody questions anymore.

Mark Putnam

That’s right, Olivia. And Chester draws on Max Weber here—he talks about “ideal types.” So, think of Boeing and NASA as the classic ideal type for big institutions trapped by their own accumulated baggage. It’s not that anyone sets out to build a monster, it’s that over time, everything from old compliance needs, to one-time political guardrails, just gets embedded. Soon, the organization can’t change anything without months of negotiation. Moving a single requirement feels like trying to reroute a river.

Olivia Carter

Exactly. And then he contrasts that “as-is” kind of scenario with what he calls the “to-be” condition—SpaceX. They basically decided, ‘Hey, what’s actually necessary?’ and threw out anything that wasn’t. I love the way he highlights how this is about culture first and foremost, not just engineering talent.

Mark Putnam

Let me ground this with an example from higher ed IT. Years ago, we ran an ERP implementation—a big one. At first, we were all excited to “start fresh,” but then stakeholders started insisting we migrate every legacy widget and workflow—most nobody could actually defend. But, boy, did people fight to keep them in. Before we knew it, the project was bogged down, loaded with invisible complexity just like SLS. No one could quite recall why all these steps existed, but nobody wanted to let go. It’s the same drift—just a different galaxy.

Olivia Carter

That’s such a good point, Mark. It becomes normal. The slowness, the endless checklists, all the friction—not because anyone loves it, but because complexity turns almost invisible after a while.

Olivia Carter

So let’s get specific about how SpaceX keeps from drifting, because this next principle honestly blew my mind. At SpaceX, every requirement gets an owner—and if you can’t attach a name to something, it’s gone. Not automated or passed on or memorialized. Just deleted.

Mark Putnam

That’s right. There’s a stark discipline there. If you’re the owner, you’re accountable. If a requirement can’t be owned, it disappears. Boeing, on the other hand, carries requirements forward—sometimes nobody even knows who wrote them. The inertia just builds. That difference matters more than a dozen process charts ever could.

Olivia Carter

Yeah. And the example Chester gives is so visceral—like, instead of optimizing complex systems, SpaceX will just literally delete the entire subsystem. Like their famous fairing-catching experiment. First they built a whole thing to catch the fairings as they fell from space, but once they realized letting them splash down and retrieving them from the water worked just as well, they dropped the whole catching system. That delete-before-you-optimize mindset feels so radical in traditional settings.

Olivia Carter

I remember covering a Silicon Valley start-up a few years ago—totally different scale than SpaceX, but same spirit. Every decision needed a clear owner. It made meetings shorter, honestly, but also a lot more direct. Nobody could hide behind ‘the group.’

Mark Putnam

It isn’t just about streamlining, either. Work simplification is leadership. It’s an institutional choice. SpaceX built a culture where unnecessary work is a bug, not a feature. And that’s something any leader, in any sector, can emulate.

Mark Putnam

This is where things get interesting. Chester argues that much of SpaceX’s innovation comes from scarcity—you know, growing up with limited capital and relentless pressure to show results or risk extinction. That kind of environment sharpens judgment. Each tradeoff is real—there’s no cushion for pet projects.

Olivia Carter

Totally. And you see that in the choices they’ve made—like switching to stainless steel for the Starship instead of exotic carbon fiber. Not only is steel cheaper, it let them skip a lot of the fussy heat-shield engineering. Or going vertical with their supply chain—building as much as possible themselves so decisions could happen fast, not over a chain of a zillion subcontractors.

Mark Putnam

It contrasts sharply with Boeing. There, abundance—steady funding, long-term contracts—lets you postpone hard choices. At my university, we went through a period when budgets were razor thin. That pressure forced us to ask, ‘What do we really need? What can we subtract, automate, or eliminate altogether?’ That discipline led us to reimagine digital student services. Necessity spurred breakthroughs we never would’ve reached with a blank checkbook.

Olivia Carter

Yeah, it’s counterintuitive: comfort can stall progress, while constraints fuel it. The faster build-test-learn cycles at SpaceX wouldn’t exist if they’d had unlimited resources and time.

Olivia Carter

Let’s get real about the dark side of abundance, though—perfectionism. Chester describes how Boeing’s obsession with flawless plans just breeds delay. The irony is, for all that planning and optimizing, progress slows to a crawl. Meanwhile, SpaceX expects prototypes to explode—it’s built into the learning cycle.

Mark Putnam

Exactly. SpaceX’s policy is “controlled failure.” They fly, fail, and learn quickly. In contrast, traditional institutions seem to think you can engineer risk completely out of the system. In reality, you just delay the learning and amplify the cost when failure does come.

Olivia Carter

I’ve seen that up close. I covered a story on data privacy at a tech company—leadership kept postponing the release of a much-needed tool because it wasn’t ‘perfect’ yet. By the time they shipped, competitors had already leapfrogged them, and their delay made customers way angrier than any initial bugs ever could have.

Mark Putnam

There’s a lesson here for every ERP or tech project in higher ed, Olivia. The drive for perfection is often a disguise for avoiding hard tradeoffs. If we’d spent less time arguing over the ideal state, and more time iterating on what worked, our students would’ve seen better results far sooner.

Mark Putnam

And this brings us to maybe the hardest part—why letting go of old requirements is so much tougher outside of SpaceX. Chester makes this point plain. In most legacy sectors—higher ed, government, you name it—change is slow not because we lack technical knowledge, but because there’s a trust deficit. People are wary. There’s negotiation, fear, need for reassurance. Building trust is the precondition for real simplification.

Olivia Carter

Right, and we’ve circled around this in a bunch of past episodes—transparency, influence rights, what you called ‘lowering the temperature’ so folks feel safe enough to try something new. At SpaceX, they can just cut requirements; in higher ed, it’s like every deletion is a potential landmine for someone’s turf or anxiety.

Mark Putnam

You’re right. From my experience, sometimes the real work isn’t technical at all—it’s helping people believe that it’s safe to let go. Even when intellectually everyone gets that a step is obsolete, nobody wants to be the first to drop it. Accruing trust—slowly, intentionally—that’s the leadership task.

Olivia Carter

And that’s really the takeaway here, right? The magic isn’t in the tech or the rocket—it’s in the discipline, the clarity, and the trust to actually embrace simplicity. If higher ed, or honestly, any institution, could master that, the potential would be enormous. Alright, Mark, I think that does it for today’s episode. You wanna sign us off?

Mark Putnam

Gladly, Olivia. Simplicity isn’t just a buzzword; it’s a discipline—and a cultural decision, more than a technical one. Thanks as always for the conversation, and thanks to everyone listening. We’ll be back soon with more on the intersection of technology, leadership, and change. Till next time, Olivia.

Olivia Carter

Thanks, Mark. See you all next episode. Take care, everybody!