In the first article, I drew a clear line between problems to solve and polarities to manage. Problems yield to choice: you pick A, reject B, and implement. Polarities refuse that tidy ending. They are pairs of interdependencies—tensions in which either pole becomes destructive when pursued as a total victory.
This second piece is the practical companion: how you actually build a polarity map, how you avoid the two most common failure modes (moralising the poles and hiding behind them), and how to turn a neat-looking diagram into something that changes behaviour—especially in context of the perennial agile tension between Planning ↔ Adaptation.
The goal is not to make you more tolerant of ambiguity. It is to help you make better decisions under ambiguity, with enough structure to prevent the debate collapsing into an ideological tug of war.
The Polarity Map is not a Compromise
Barry Johnson's foundational thought was to treat certain organisational tensions not as puzzles to be solved, but as systems to be managed over time—akin to breathing in and breathing out: you don't pick one and banish the other; you stay alive by cycling well. That's why his method insists on two things: (1) naming the upsides you're trying to get from each pole, and (2) naming the downsides you will trigger when you over-invest in one side.
This fits neatly with what organisational scholars later formalised as a paradox lens: persistent, interrelated tensions that intensify over time and require ongoing responses rather than final resolutions. When either/or responses are sought they tend to become reinforcing cycles—something of a self-fulfilling prophecy. This contrasts with what sustainable performance requires, a kind of dynamic equilibrium—an ability to keep both demands in play rather than suppressing one.
If you've ever watched an executive team argue about agile, you've seen this dynamic. Someone says, "We need more planning," and someone else hears "waterfall". Someone says, "We need more autonomy", and someone else hears "chaos". The polarity map is a way of stopping those translation errors long enough to ask a better question:
What would it look like to get the best of both, while detecting—early—when we're sliding into the worst of either?
That word early matters. A polarity map, properly used, is less like a philosophy and more like a leading-indicator dashboard: it is designed to reveal drift before drift becomes damage.
Step 1: Name the Polarity in Positive Language
The first error people make is to name the poles as virtues versus vices (e.g., "discipline vs recklessness" or "policies vs innovation"), which rigs the exercise from the start. If one pole is already framed as a negative pathology, you don't have a polarity; you have a sermon.
