The Long Game: Civilization & Work - Why Smart Institutional Reforms Fail.

Episode Date: May 28, 2026

Systemic Redesign: Ackoff’s Methodology and Its Human Limits We explore the intellectual transition from harmonizing different ideas to a more rigorous method called collision, which generates insights by highlighting where frameworks disagree. While Russell Ackoff’s systems thinking provides a vital methodology for redesigning failing institutions, the text argues that his approach is limited by unresolved tensions involving power, human cognition, and civilizational decay. By forcing Ackoff’s theories to impact the hard realities described by thinkers like Quigley, Kuhn, and Glubb, a more durable form of institutional design emerges. This "collision" reveals that any successful reform must account for human irrationality and the tendency for planning bodies to become stagnant obstaclesthemselves. Ultimately, the text advocates for Power Aware Design, an approach that treats systemic friction and the inevitability of corruption as primary constraints rather than secondary problems. This methodology rejects the tidy consensus of traditional synthesis in favor of a "Particle Accelerator" model that finds truth in high-energy intellectual conflict.

🎵 Welcome back to The Long Game. I'm Gregory Sparzo. And before I hand you over to the conversation that follows, I want to spend a little more time than usual setting the table. This episode goes deeper than most, and I think you'll get more out of it if I lay the foundation myself. Most people who work on broken institutions reach the same common instinct. They gather the best thinkers, find where those thinkers agree, and blend the agreements into a unified framework.

work. That blending has a name. We call it synthesis, and we tend to treat it as if it was the highest form of intellectual work. I am here to challenge that. Synthesis smooths things out. It sands down the edges where two powerful ideas refuse to fit together, and those edges are usually where real insight lives. So instead of synthesis, I work by collision. I take frameworks that cannot be reconciled, hold them in the same room, and pay close attention to the sparks that fly

when they refuse to merge. The contradictions are not a problem to be solved. They are the data. This episode applies this method to one of the most important figures in systems thinking, Russell Ackoff. Ackoff gave us something genuinely valuable. He drew a hard line between analysis and synthesis

as ways of understanding a system. Analysis takes things apart to see how they work, how the pieces work. And it is an engineer's instinct and it's powerful, but it has a big blind spot. When you break a system into parts and fix each part, you can still end up with a system that fails because the failure was never in the parts.

It lived in the interactions, the feedback loops, the incentive structures, the way the whole thing behaves when nobody is looking at any single component. Ekoff's contribution was to insist that you treat the interaction structure as the whole, structure of the whole, think about it, as the real object of the design. He wanted us to dissolve problems

by redesigning the system that produces them, rather than chasing symptoms one at a time. That idea survives everything I'm about to say. I want to be clear about that really up front, because when it comes to this, it's not a complaint or a criticism, it's a rescue. So here's the trouble. Akhoff built his methodology in the 1970s, and it carries the optimism of that moment. It assumes that if you bring the right stakeholders together

and invite them to imagine an idealized design, they will reason their way towards a better whole. It assumes rational actors who can subordinate their own interests to a shared purpose. and this assumption does not survive contact with how institutions and human beings really behave. So rather than defend Ackoff or discard him, I collide his work against four other thinkers who each expose a different way the optimism breaks down. I call these the four collisions and they form the spine of this episode and my forthcoming book, Human Economics. The first is the Quigley

problem I call it. Carol Quigley studied the rise and the fall of civilizations and he noticed that institutions tend to follow a trajectory. A tool gets created to solve a problem. It works. It acquires staff and budget and prestige and over time it begins to serve its own survival interests rather than the purpose for which it was built. The instrument becomes the obstacle. Now turn that lens on systems thinking itself. The methods I am describing can just as equally ossify in the way these other things, other systems are. They become a brand, a credential, a consulting best practice that protects its own franchise. The very discipline meant to keep institutions honest is not immune from the disease it diagnoses. The second is the Kuhn problem. Thomas Kuhn taught us

that knowledge advances through paradigms, and that people trapped inside a paradigm cannot easily see past it. System thinking itself is a paradigm, which means it can be captured. Watch what happens when an organization committed to, say, shareholder value adopts the language of systems redesign. The vocabulary gets borrowed, the workshops get held, and the outcome quietly preserves the exact extractive machinery that the redesign was supposed to dismantle. The words change. The mechanism does not. Next is the Glubb problem. John Glubb wrote about the life cycle of empires

and he observed that civic capacity is not permanent. It depletes. In the early vigorous phase of a civilization, the orientation is towards building. In the late phase, it shifts towards protecting what one already has. This matters enormously for Ackoff because idealized design depends on stakeholders willing to set aside self-interest for the collective future. In a late-stage culture, those stakeholders may simply no longer have that orientation in them. They just don't have it. You cannot run a building exercise with people whose entire instinct has become defensive. The fourth is the Kahneman problem and this one

cuts the deepest. Daniel Kahneman showed that human cognition runs mostly on system one, the fast automatic loss-averse machinery that governs our defaults and occasionally engages system two, the slower more deliberate reasoning that we like to imagine drives our choices. Ackoff's rational actor is a System 2 fantasy. Real participants, the moment a redesign threatens something that they value, drop into loss aversion and defensive reflex. The process degrades.

What started out as a bold reimagining collapses into a proposal that looks suspiciously like the status quo, but with new language stapled to it. Put those four collisions together and a pattern emerges. Every one of them points to the same missing ingredient, which is an honest account of power and human frailty. Ackoff gave us a methodology built for an idealized humanity. What I am building is a methodology for the humans that actually show up here.

I call it power-aware design. It keeps Ackoff's structural insight, the focus on interactions and incentives, and the whole rather than the parts, that's all good, but it strips away some of the 70s optimism and rebuilds the method on behavioral foundations. It assumes entrenched interests. It assumes cognitive bias. It assumes that civic capacity may be running low. It's designs for sinners, not saints. And the way all of this comes together is through what I call the collision map. Rather than averaging these thinkers in tidy consensus, the map holds them in tension

and lets the friction between them generate insight that no single one of them could produce alone. Quigley warns you about the instrument decaying. Kuhn warns you about the paradigm being co-optive. Glubb shoots up a warning flare about the depleted reservoir of civic goodwill. Kahneman warns you about the wiring inside everyone's head. None of them is sufficient. Each one corrects the others.

The tension is the engine. So, as you listen to this conversation that follows, keep that frame in mind. We are not blending ideas. We are banging them together on purpose, and the value is in the differences. This is the rugged alternative. a systems thinking honest enough to account for its own failure modes and durable enough to work in the world as it really is. Let's get into it.

have you ever you know watched a team of incredibly smart well-intentioned people implement this brilliant institutional reform and then you just watch it fail spectacularly Oh, absolutely. It's honestly maddening. Right. You stare at a failing hospital or maybe a stagnant school district or, I don't know, a company being strip mined by its own executives. And you just know the plans were flawless. Yeah, the data was solid. Exactly. But the execution just turned into a complete disaster. You look at these situations and you think, well, the people here aren't inherently malicious.

So why is the outcome so consistently destructive? And it's usually not because people aren't trying. It's because the tools we use to fix broken systems are they're fundamentally ignoring human reality, which is exactly what we are digging into today on this deep dive. It's a fascinating topic. It really is. So today we're looking at Gregory Sparzo's March 2026 book, Tragedy and Work, a rugged alternative to despair. Specifically, we're focusing on chapter six alongside his supplemental notes on a concept he calls collision dynamics. Yeah. Sparzo is essentially tackling the ultimate design problem here. He's trying to answer why genuinely smart institutional reforms keep failing. Right. And more importantly, how we can actually create systems that survive the really messy, irrational reality of human behavior.

So let's start with how Sparzo even approaches this, because his idea of collision dynamics goes against, well, basically everything we are taught about problem solving. It really does. I mean, we are usually told to synthesize, right? Take the best parts of different ideas, find the common ground and just snap them together. I always picture synthesis like like building a Lego house. You take a piece of theory A, snap it onto theory B and you build a safe, stable model. Yeah, the Lego model is comfortable. It's exactly how we are trained to think in school. Right. But Sparzo actually argues that tidiness is intellectually destructive. Destructive? Wow.

Yeah, because when you smooth out the rough edges of two different frameworks just to make them fit together, you're discarding the exact things that make them valuable. You basically lose their sharp, specific angles of vision. Oh, I see. So he counters your Lego model with a radically different one, which he calls the particle accelerator. Wait, a particle accelerator. So the goal isn't to build a working model at all, but to intentionally break the theories apart to see what's left. Essentially, yes. That sounds, I mean, incredibly counterproductive if you were actually trying to fix a hospital or a school district. It sounds chaotic for sure, but the real insight lives in the wreckage.

I mean, in a particle accelerator, you don't gently snap incompatible theories together. You smash them into each other at high velocity. Right. Just total destruction. Sparzo uses a geological concept here, the shear zone. So think about two tectonic plates or maybe two massive gears that just don't quite mesh. Yeah. You have brief moments where they grip, but mostly you get this intense, slick, and structural grinding. That friction, that stress, that's where new knowledge is generated.

Because when they grind, you actually expose what one theory completely misses. Exactly. You expose what he calls the incommensurability gap. That's a mouthful. It is, yeah. But it just means that blind spot where one framework literally cannot comprehend what another framework is describing. Okay, that makes sense. So our mission today isn't to draw some neat Venn diagram of management strategies. We're going to take the absolute best institutional design tool we have,

and we're going to crash it head on into four brutal realities of human nature just to see what survives the impact. Okay, let's bring out the design tool then. The victim of our particle accelerator. Sparzo points us to Russell Ackoff. Yes, Russell Ackoff. He was an architect who eventually became a real pioneer in operations research. Okay. He spent about 50 years at Wharton building this comprehensive methodology for treating organizations as complete living systems.

And his whole approach really hinges on redefining how we look at complex problems, moving from analysis to synthesis. Hold on. Wait a minute. We literally just spent three minutes trashing synthesis as a concept. Now, Ackoff is the hero for using it. Fair point. Fair point. But Ackoff is using the term differently here. He is contrasting it with traditional analytical breakdown. Okay. How so?

Well, if you have a broken car engine, you use analysis. You take it apart, look at the spark plugs, the pistons, find the broken piece and replace it. The properties of the engine are basically just the sum of its independent parts. Right. But if you're looking at a hospital, that logic completely falls apart. Exactly. Because a hospital is a complex social system. Yeah. the most important properties don't live in the individual parts. They actually emerge from the interactions between the parts. I see. So, Ackhoff's version of synthesis is about zooming

out to understand that entire interaction structure. Okay. So, if a hospital has terrible readmission rates, the analytical approach would just say, the surgeons are making mistakes. Let's optimize the surgical checklist. You just fix an isolated part. Right. But the systemic approach says the hospital isn't just a checklist. It's the dynamic interaction between the nurses, the doctors, the insurance billing department, the physical layout of the building and, you know, the organizational culture. Exactly. So if you want to change the readmission rate, you have to fundamentally alter that entire interaction structure. Which leads to Ackoff's deepest conceptual insight. He makes this hard distinction between solving a problem and dissolving it.

Dissolving it, like just making it irrelevant. Exactly that. Solving a problem is just treating a symptom within the current flawed system. You have a trader making risky bets. You punish them. You have long wait times. You mandate longer shifts. But dissolving a problem means redesigning the system so the symptom cannot possibly exist in the first place.

Wow. That's a huge shift in perspective. It is. You stop asking, how do we punish this bad behavior? And you start asking what interaction structure would make productive behavior the absolute path of least resistance. I mean, it makes perfect sense on paper. You sit down in a quiet room, outline the ideal outcome, and just map out the feedback leaps to guarantee it. But this is where we turn on the particle accelerator, right?

Because Ackhoff assumes you can just draft this beautiful, pristine design and hand it over to actual humans to implement. And humans are messy. They form institutions. They protect their turf. And that brings us to our first collision, which is the Quigley problem. The Quigley problem? Yeah. Named after historian Carol Quigley and his instrument to obstacle cycle. Wait, how does an instrument become an obstacle?

Well, Quigley observed that when a new methodology like systems thinking genuinely works, it starts out as an instrument. It provides real measurable value. OK, makes sense. But because it provides value, people organize around it. They institutionalize it. It gains prestige, generates massive revenue, and eventually becomes a brand. Ah, I see where this is going. Right.

And eventually, the primary purpose of that institution shifts from solving the original problem to protecting its own brand and its own resources. The rescue itself becomes an obstacle. So if a struggling company hires a massive consulting firm, like, say, a McKinsey or a BCG, to do this deep systemic redesign, the consulting firm itself is the obstacle. In many cases, yes. I mean, they started as instruments bringing analytical rigor. But think about the mechanics of how they operate now. They get brought in to do deep, Ackoff-style redesign. But doing that requires a massive, unpredictable upheaval of the client's culture and power structures.

That is incredibly risky for the consulting firm's brand if it fails. Oh, wow. So instead of actually dissolving the broken system, they just sell a very safe, generic, 14-week cost-saving framework. Because that is what their business model dictates. They practice the exact analytical decomposition, breaking things into parts to trim headcount that Ackoff's methodology was invented to transcend. That is so ironic. It really is. The rescue mission gets captured by the institution hired to deliver it. The leadership thinks they're buying systemic change, but they are really just buying the prestige of the consultant's brand to justify firing people.

That is incredibly frustrating. The tool literally becomes a trap. But, OK, let's say we fire the consultants. We bring the systems thinking in-house. We put our own executives in a room to redesign the interaction structure. We still run into the second collision. We do. The Kuhn problem.

Right. Thomas Kuhn. And this isn't just about business models, is it? This is about how our brains actually process reality. Exactly. Kuhn's work on paradigm shifts escalates the capture from the institution to human epistemology itself. Right.

Ackhoff assumed systems thinking was a neutral tool. Right. Like a hammer that any rational person could just pick up and swing. But Kuhn shows that systems thinking isn't a neutral tool at all. It is a paradigm. It's a way of seeing the world. And humans interpret tools through whatever paradigm they are already trapped inside. So think about a chief financial officer sitting in one of these idealized design sessions.

Their entire professional worldview, their paradigm, is built around maximizing shareholder value. That is how they've survived and thrived their entire career. Precisely. So when you hand that CFO Akoff's tools, they will use all the right vocabulary. They will talk about interaction structures and holistic feedback loops. But the machine they design will still just systematically extract wealth. Because it's not even malicious, right? The CFO isn't secretly plotting to ruin the company.

It's just that their paradigm makes alternative values like community health or employee well-being literally invisible to them as anything other than a financial cost. You nailed it. The tool works perfectly, but the person holding it cannot see outside their own matrix. Every major corporate sustainability initiative of the last 30 years ran into this exact wall. The vocabulary of systems change was just absorbed and used to protect the status quo. Okay, so even if we bypass the consultants, and even if we somehow manage to see past our own deeply ingrained paradigms, aren't we still dealing with the fact that organizational culture eventually just gets tired? That is the perfect transition to the third collision, the Glubb problem. John Glubb studied the life cycles of empires and developed a civilizational clock.

Ackoff's redesign methodology fundamentally relies on something called civic capacity. Meaning the willingness to take a hit for the team. Right. Like you look at the data and say, wow, my department is the bottleneck. We need to reduce my budget and give it to someone else for the good of the whole hospital. Exactly. It requires sacrificing short-term personal interest for long-term systemic health. Akhoff just assumes people will do this if the logic is sound.

Yeah, which is a big assumption. Huge. Yeah. Because Gloves shows that civic capacity is not a constant. It fluctuates based on where a culture is in its life cycle. I see. So in the early days of a startup or the building phase of a civilization, people have that capacity. Everyone is pulling together to survive and create something new.

But in late stage organizations or civilizations, the environment completely changes. The wealth is already built. So the psychological focus shifts from creating new value to defending inherited value. You no longer have a room full of civic minded builders. You have a room full of elites who are exceptionally skilled at managing and protecting their existing advantages. The very mechanism of their success is turf protection. So if you walk into a mature, stagnant school district and ask the administrators to voluntarily give up power for the sake of the students, the human material required to sustain that beautiful redesign simply isn't there.

The culture has totally eroded it. And the final collision proves that even if the culture was healthy, our biology is still actively working against it. Oh, great. Yeah, this is the Kahneman problem, drawing on Daniel Kahneman's behavioral economics. Okay, this is the battle between system one and system two thinking, right? Right. Ackoff's idealized design is the ultimate system two exercise. It assumes deliberate, analytical, rational thought.

It requires you to sit quietly, suppress your biases, and map out complex causal loops. But Kahneman showed our default is system one. We are fast, emotional, deeply loss-averse, and, you know, highly tribal. Now, connect that biological reality to the actual environment of a systemic redesign. When do organizations usually call for an Ackoff-style intervention? When things are falling apart. Exactly. Not when things are going great. They do it during a crisis, a hospital turnaround, a corporate restructuring. Which is a high-stress environment. Jobs are on the line. Budgets are being slashed. People are terrified.

And what happens to the brain in high stress? Yeah. Amygdala takes over. The prefrontal cortex, which is the home of system two analytical thought, literally gets bypassed. Wow. You physically cannot engage in the rational, long-term thinking Ackoff's model demands. System one survival mode just hijacks the entire process. So Ackoff is essentially asking a stressed out middle manager to sit down and play 3D chess, but he's asking them to do it while they are actively running from a bear. That's a perfect way to put it. Because their status and their livelihood are under threat.

Of course, System 1 takes over. You don't optimize the interaction structure. You grab whatever budget you can and you run for the trees. So we've run the particle accelerator. We smashed ACOF's brilliant systems methodology into Quigley's institutional capture, Kuhn's blinding paradigms, Glob's cultural decay, and Kahneman's tribal biology. And looking at all this debris, I mean, it feels bleak. Why even try to fix a broken system if institutions, mindsets, culture, and biology are all conspiring against us?

Because this isn't fatalism. Sparzo calls this a productive paradox. Okay. The despair is actually the payload of the collision. By smashing Akos' somewhat naive view of humanity into these brutal realities, we strip away the fragility of his model. We find out what is actually robust enough to survive in the real world. Okay, so what does survive? Let's sift through the wreckage here.

The core of ACOF's methodology actually survives. The critical distinction between solving a symptom and dissolving the underlying problem is still the most powerful conceptual tool we have. The necessity of focusing on the whole interaction structure survives. But what dies? What dies is the assumption that homo bureaucraticus exists. Homo bureaucraticus. Yeah. The perfectly rational, deeply civic-minded actor who always thinks long-term, possesses unlimited System 2 energy, and never cares about their own ego or status. That fictional person is dead. Well, good riddance. We can't keep designing systems for a species that just doesn't exist. Exactly. And that brings us to Sparzo's ultimate takeaway, which is power-aware design.

You don't design around human nature by assuming better humans will eventually show up. You design for the humans who actually walk into the room. The sweaty, stressed out, highly territorial, paradigm blind humans. Those are the ones. So PowerWare design treats power and self-interest as the main ingredients, not like bugs to be ignored. You have to ask, who is actively fighting to keep the system broken? What resources are they going to deploy to stop you? And how does your new design make that resistance incredibly expensive and exhausting to sustain?

That is the genius that emerges from the collision. If your new institutional design requires everyone to voluntarily act against their own interests, it is a catastrophic design. You have to create an interaction structure where the easiest, laziest, most self-interested thing a person can do just so happens to produce the systemic outcome you want. Which changes everything. I mean, if you're listening to this and you've ever felt like your attempts to fix your team, your community, or your company just keep hitting a brick wall, it's probably not because your technical fix was wrong. Your spreadsheet was likely flawless. As it was. But it's because you were designing for ideal conditions.

You were trying to snap Lego bricks together. But your organization doesn't live in a Lego set. It lives in a sheer zone. Yeah, and once you realize that, you stop being surprised when people resist the change. You expect the resistance. You anticipate the paradigm blindness. And you build the structural defaults to account for it. Which leaves us with a final thought I really want you to mull over.

Now that you know you cannot rely on perfect rationality or pure civic virtue from your team or from yourself, honestly, how does that change the very next meeting you run? That's the real question. What defaults can you put in place tomorrow that require active effort for people to act selfishly rather than just asking them nicely to be better? Next time you find yourself staring at that failing hospital or that stagnant school or that broken process, don't ask why people aren't better. ask how the system can be redesigned so they don't have to be thank you for joining us on this deep dive we'll catch you next time