Friction, beauty, breakthrough: what Steve Jobs knew about systems thinking

Part one of this series made the case that look-alike business teams are structurally unable to evaluate systems-level change. Same schools, same frameworks, same blind spots. The problem isn't bad faith. It's the way they are trained to think.

Here is what the alternative looks like. Not in theory. In practice, across five centuries and multiple continents.

Because the pattern that produces breakthrough thinking has been with us for a long time. We've just stopped recognising it.

Steve Jobs and the musicians who happened to code

In conversations about the Macintosh team, Steve Jobs described something that most business leaders still do not fully grasp. He didn't build a team of engineers. He built a team of musicians, poets, artists, zoologists, and historians who happened to be computer scientists.

Not despite those backgrounds. Because of them.

The Macintosh wasn't produced by people who thought like computer scientists. It was produced by people who thought like calligraphers and musicians and painters. And also happened to understand code. The intersection is where the breakthrough lived.

Jobs called it the Rock Tumbler Theory. Walter Isaacson's biography of Jobs documents this philosophy in depth, the deliberate mixing of people whose thinking came from entirely different places, whose friction produced what no single discipline could have reached alone. You throw in a collection of sharp, ugly rocks. You add grit. You turn on the motor and let them smash against each other. The friction is not a problem to manage. The friction is the mechanism. What comes out is something polished and beautiful that none of those rocks could have become on their own.

That is not a metaphor for chaos. It is a methodology. And once you see it, you start noticing it everywhere.

The Renaissance precedent we forgot

Josh Harrison, whose parents Helen and Newton spent five decades applying exactly this methodology to planetary-scale problems, puts the historical context in a way I found genuinely clarifying.

We tend to think of Leonardo da Vinci and Michelangelo as polymaths. People who could do anything. But Josh reframes them differently: they were talent integrators. Exceptionally skilled at marshalling the resources of a large community of artisans, engineers, and manufacturers toward a single vision.

Michelangelo didn't paint the Sistine Chapel by lying on his back alone for four years. He held the vision, managed an exceptionally difficult client (a pope who kept changing his mind) and kept a large team of diverse contributors moving in a coherent direction. That is a leadership and integration skill, not just an artistic one.

What made this possible was the Renaissance's refusal to separate disciplines. Architecture, natural history, hydraulics, portraiture, and military engineering. These were not different fields requiring different specialists. They were different lenses through which a single integrated mind could examine a single problem. From a business perspective, I believe we took that integration apart. We sorted knowledge into silos. We hired for depth in one lane and called it expertise. And we lost something essential in the process.

What the Harrisons understood about impossible problems

Helen and Newton Harrison spent the last four decades of their lives under a commitment that reframed everything they did. Treat the planet as the client. Not a stakeholder. Not a consideration. The primary client, with all the obligations that that relationship implies.

From the late 1970s until the end of their lives, Josh told me, their working test for any project was simple: does this work do no harm to the environment? Not to minimise harm. To do no harm.

That commitment changed the questions they asked. And different questions open entirely different solution spaces.

The conventional framework asks: how do we achieve our goals while managing environmental impact? The Harrison framework asked, "What does this system need to thrive?" And how do we design human activity around that? Same landscape. Same constraints. Completely different starting point. Completely different outcomes.

What is a happy crab?

The most vivid illustration of what different questions produce came early in the Harrisons' ecological work. They had begun growing things, plants, and then catfish, in gallery and laboratory settings. Then a colleague suggested something nobody had attempted. Grow crabs in captivity.

The technical question would have been: what are the biological requirements for crab survival in a controlled environment? That is the expert question. Inputs, outputs, parameters, optimisation.

The Harrisons asked something else entirely: what is a happy crab?

Josh walked me through what followed. If you want a crab to reproduce, it needs to be happy. When are crabs happy in the wild? These particular crabs, a hardy lagoon species from Sri Lanka, reproduce after the monsoon season. So what would happen if you induced an artificial monsoon in a laboratory setting?

It is a dead obvious question in retrospect. Nobody had thought to ask it before.

They took a garden hose, dropped the salinity, and poured two hours of fresh water. The crabs started acting frisky. Months later, the first captive-bred crabs existed. The Harrisons became the first artists ever to receive a sea grant, and the work they did laid the foundation for aquaculture practices still in use today.

The breakthrough didn't come from deeper expertise in marine biology. It came from asking a question that marine biologists weren't positioned to ask. That is what different thinking produces.

Improvisational teams, not permanent staff

One of the things Josh described about his parents' methodology is that they didn't build a permanent team of specialists. They assembled whoever they needed for the specific problem in front of them.

Josh called it putting teams together improvisationally and situationally. For the Holland housing crisis, they brought in local urban planners, researchers who knew the region, and people who understood the political dynamics and environmental constraints. For the Sava River project, a different team entirely. People who knew that specific watershed, those communities, and those ecosystems.

This runs counter to how most organisations build expertise. We hire permanent staff. We develop institutional knowledge within fixed teams. We protect those teams from disruption because disruption feels like inefficiency.

In most cases, what we actually protect is sameness. The team that solves this problem well is not necessarily the team equipped to see the next problem clearly. The Harrisons' approach asked a prior question. Who needs to be in the room for this specific challenge? Not who do we have, but who do we need?

Why traditional expertise gets stuck

Here is what I have observed across decades of working with leadership teams. Experts ask expert questions. That sounds obvious, but follow the implication.

An expert in a given domain has been trained to see certain things clearly and to ask certain questions well. That training is genuinely valuable. It is also constraining. The deeper the expertise, the more automatic the frame.

"How do we grow crabs?" is a marine biology question. It looks for solutions within the domain of what marine biologists know. "What is a happy crab?" breaks the frame. It looks for solutions in a completely different register. Behavioural, ecological, and even empathetic.

In my experience, most sustainability challenges are happy-crab problems. They require reframing, not optimisation. They require questions that no one inside the current system is positioned to ask. They require people whose way of thinking doesn't default to the familiar frame. You cannot hire your way to that from within the same pool. You cannot build it with teams selected for culture fit. You cannot produce it from organisations that have sorted their expertise into separate silos and stopped the cross-pollination.

The grit is the point

I want to be clear about what Rock Tumbler Theory actually requires, because I think it gets romanticised in the telling.

Friction is uncomfortable. A room where someone turns the maps upside down and says everything you've done is wrong is not a comfortable room. A team that genuinely thinks differently will slow you down initially. The disagreements are real. The discomfort is real. The temptation to resolve the friction by returning to familiar thinking is constant.

Jobs understood this. The Harrisons understood this. The friction is not a side effect to be tolerated. It is the mechanism of transformation. Remove the friction, and you get speed, smoothness, and predictability. You also get incremental results from teams with identical blind spots.

The organisations that have produced genuine breakthroughs on systems problems, or on the kinds of civilisational questions that sustainability represents, have found ways to make the friction productive rather than destructive. That is a leadership and structural challenge, not just a hiring challenge.

illuminem Voices is a democratic space presenting the thoughts and opinions of leading Sustainability & Energy Thought Leaders, their opinions do not necessarily represent those of illuminem.

Track the real-world impact behind the sustainability headlines. illuminem's Data Hub™ offers transparent performance data and climate targets of companies driving the transition.