Cybernetics is not the Banana! (Part 2)

This week’s newsletter brings episode 24 of the Cyb3rSyn Labs Podcast, featuring Benjamin Taylor, Managing Partner of RedQuadrant and a long-time advocate of the insights from systems thinking, complexity and cybernetics.

In this episode, Benjamin begins by noting that "the map is not the territory," and that understanding a situation is always based on one's framing, context, and purpose. The discussion critiques over-reliance on technology and stresses that meaningful work requires judgment, discretion, and established, negotiable boundaries. Benjamin challenges many mainstream assumptions and ultimately advocates for a deeper philosophy of management that balances rigor and freedom.

Through reflections on public sector complexity and the drawbacks of tech-driven solutions, Benjamin offers profound insights into organizational behavior. This episode is rich with practical advice and conceptual frameworks aimed at enhancing leadership and personal effectiveness.

Members of the Cyb3rSyn Community can watch/discuss the podcast episode on the www.cyb3rsynlabs.com portal or the mobile app (iOS and Android).

While the conversation with Benjamin was touching on cybernetics and philosophy, delivered some of the most practical wisdom I’ve heard about organizational life. Benjamin makes a call for radical self-inquiry, reminding us that often, the biggest problems we face aren't technical; they're epistemic.

Here are the key takeaways from my mind-expanding discussion with Benjamin Taylor:

In conversations about leadership, we often hear the classic line: "The map is not the territory." But as Benjamin pointed out, we have to be careful about the metaphor. It implies that if we are smart enough, we can create a better map of the territory, or perhaps even understand the territory itself.

The fundamental, humbling truth is this: You are only ever comparing your map to another map.

This is why we should focus on epistemics (the nature of knowledge, our framings, and how we know things) rather than getting bogged down in ontological arguments (arguments about what fundamentally exists in the real world). I’m reminded of the following quote by Heinz von Foerster

A map is useful only relative to what you are trying to do. Whether we are discussing an engine or an organization, our view of the system is simply our framing of what is happening in the real world. Benjamin goes on to even frame hard systems — like engineering — are just a special, privileged application of soft systems (our worldviews and framings).

Many of us in high-paced environments confuse effort and presence with actual work. Benjamin offered a cybernetic definition of work that cuts right to the heart of the matter: effort to a purpose, using judgment and discretion within boundaries over time.

If you are "just being directed" or are "just a pair of hands," you are not really working; you are slaving. The Czech word robot, after all, comes from "slave". True work requires using your expertise and making your own choices.

However, this discretion needs structure. If you are given too much freedom, it is not productive. This is where boundaries come in—negotiable, consensual boundaries are crucial for defining what your work is, managing context, and allowing coordination.

This paradox—that freedom requires structure—was perfectly illustrated by the story of Buurtzorg, the self-organizing Dutch district nurses. They achieved incredible financial savings and success by removing managers and empowering the nurses. But the untold part of that success is the "buttressing" required: they shared a common sense of mission, were consistently trained, and had strong commonalities and norms (mostly female, mostly Dutch, shared sense of civic duty). They already had common ways of sense-making. Self-organization, as it turns out, requires a great deal of organization and structure to enable it. The underlying cultural context also gets missed.

As we explored practical tools and heuristics, one stood out for its simple, immediate impact: naming the thing.

A hugely powerful thing you can do to increase your authenticity and impact is to state a dynamic that is happening, objectifying something that was previously latent or part of the implicit context.

Consider Peter Block's advice from Flawless Consulting: if a meeting is stuck, the most powerful thing you can do is simply say, "We seem to be stuck". Most of the time, we are in denial of the stuckness, and that denial contributes massively to the problem. Once named, you can ask why or take a break.

This pattern applies everywhere, even in sales. The human instinct is to ignore or skate over objections. Naming the objection, drawing it out, and really trying to understand it is profoundly powerful.

However, here we must return to the map. While naming something feels like breaking through to a "new layer," remember the companion idea: remember there are no things. Naming is not defining reality; it is merely suggesting an alternative, and potentially more useful, map or framing.

How do we break out of locked-in thinking? The insights of second-order cybernetics provide a roadmap, wonderfully summarized by the famous Heinz von Foerster story:

Imagine a chimp in a cage. A banana is on a high shelf, out of reach. There is also a stick. The chimp uses the stick to get the banana. Cybernetics, von Foerster noted, is not about the banana.

Ultimately, the deepest insight requires transcending the paradigm entirely! This aligns perfectly with Donella Meadows’ insights on leverage points: the highest leverage is the ability to transcend paradigms and realize that paradigms are, in fact, just paradigms. For technologists, recognizing that there are infinitely many ways of seeing any given situation allows us to move fluidly between framings without getting locked into one.

Finally, zooming out, Benjamin noted a fundamental flaw in modern organizational life: a "soggy" mainstream management that lacks rigor and accountability because leaders are terrified of being accused of micromanagement. The resulting backlash often defaults to "nasty management" because people fail to grasp what effective management looks like.

What is sorely missing is an actual philosophy of management — a guiding methodology and an overall approach.

Progress relies on "hardness of intent" and accountability, but this must be interwoven with the intention of creating consensual coordination of meaning. This structure gives the space for freedom and coordinated action toward a purpose, recognizing the inherent dilemmas and paradoxes.

For those in the tech community, often navigating great opportunity and immense commercial talent, the closing advice was perhaps the most vital: engage in radical self-inquiry.

Challenge the framing you bring to your own life choices. When money swells to fill your entire worldview, it brings negative second-order implications. While systems, cybernetics, and complexity theory are incredibly powerful and effective, they are also mostly value neutral.

You need your own grounding in ethics, purpose, and meaningfulness alongside these tools, because the practices can be used for good or for ill. Objectify your assumptions, challenge your frames, and you will learn a lot along the way.

Here is a link to Ben’s Reading List for those looking to get into Systems | Complexity | Cybernetics. Watch the podcast to learn about his advice on how to approach this long list…

For premium-tier members, here is a handy table of the books mentioned in the conversation: