The meeting began the way these meetings often begin: with conviction.
"We need to give teams autonomy," said the Head of Product. "That's the whole point of becoming more Agile."
"We can't," replied the Head of Risk. "We're a regulated business. Governance is non‑negotiable."
Someone else tries to rescue the spiralling situation: "Maybe we just need clearer guardrails."
By the end of the hour you can feel the organisational whiplash forming. Six months from now someone will declare the current model "too bureaucratic" and swing hard toward empowerment. Six months after that, an incident, a failed audit, or a major customer miss will swing everyone back toward tighter control. Both camps will insist the other side "doesn't get it", and each swing will be justified as the solution.
If you've encountered category errors before, you've probably recognised a cousin of that mistake here. Sometimes leaders really are making a category mistake—arguing as if two things belong in the same conceptual bucket when they don't. But there's another, subtler pattern: leaders correctly identify a genuine tension—then treat it as if it has a once‑and‑for‑all answer.
This is the terrain of polarity mapping (also called polarity management): a structured way of working with interdependent opposites—pairs that look like a conflict but are, in fact, mutually necessary over time.
The core premise is disarmingly simple:
- Problems can be solved (choose A or B; implement; move on).
- Polarities can't be solved—only managed. If you choose A and eliminate B, you eventually trigger the downsides of A; the system then lurches back toward B.
Research on organisational paradox helps explain why these swings are so predictable. Contradictions generate discomfort and defensiveness; leaders simplify into either/or positions, then react when the costs of that position become undeniable. The more mature response is not a vague call for balance, but a kind of dynamic equilibrium: ongoing, cyclical responses that allow performance now without undermining performance later.
Polarity mapping doesn't abolish strategic choices. It helps you stop treating enduring interdependencies as if they were one‑time decisions.
Three Kinds of Tensions Leaders Confuse
A practical way to reduce leadership confusion is to separate three different categories that frequently get blended in one heated conversation:
1) Problems to Solve
Problems have solutions that hold once implemented—at least until conditions change. A payroll system that can't handle overtime rules is a problem. Fix it. Ronald Heifetz's distinction between technical problems and adaptive challenges is useful here: technical problems have known solutions (or can be solved by expertise), while adaptive challenges require shifts in values, habits, and relationships.
2) Trade-offs to Decide
Trade-offs are strategic choices with real opportunity costs. You cannot pursue every strategic position simultaneously without becoming blurred, incoherent, and easy to imitate. This is Michael Porter's enduring point: strategy requires choices about what not to do; otherwise operational improvement becomes a substitute for strategy.
3) Polarities to Manage
Polarities are pairs of goods (or two necessary orientations) that are interdependent over time. You don't win by choosing one. You manage the oscillation so you can consistently access the upsides of both poles while avoiding the predictable downsides of over‑privileging either one.
A classic example from the research literature is exploration versus exploitation. Exploration produces variation, learning, and new options; exploitation refines and harvests what you already know. Too much exploitation and you stagnate; too much exploration and you never cash in. That is not a debate you can settle permanently. It's a capability you must build.
Likewise, the "Competing Values" tradition shows why organisations repeatedly swing between control and flexibility, internal integration and external positioning. Many organisational virtues are paired and cannot be maximised simultaneously without active management. In other words: the tension is often structural, not a leadership personality defect.
A Quick Diagnostic: Polarity or Problem?
When a leadership team is stuck in a recurring A‑vs‑B argument, ask five questions:
- Does this keep coming back—even after we've solved it?
If the argument resurfaces every year under a new label, it is often a polarity. - Are both poles genuinely valuable in their healthy form?
Autonomy and governance. Stability and change. Standardisation and innovation. If one side is always cast as a vice, you may be dealing with ideology rather than analysis. - Do the benefits and costs play out over time, with a delay?
Polarities are time‑structured: upsides are usually immediate; downsides are often delayed. That delayed downside is what triggers overcorrection and swinging. - What happens if we "win" decisively on one side?
If eliminating the other pole reliably creates a future failure mode, you're not looking at a simple problem. You're looking at an interdependence. - Are there hard constraints that weight one pole?
In regulated or high‑reliability environments, governance and safety are not optional. You may still have a polarity, but you manage it within prescribed guardrails.
That last question matters because polarity language can be used to blur moral and legal clarity. For example: fraud is not a polarity; a compliance breach is not a polarity. In those cases, leadership is decision, enforcement, and repair—not oscillation.
The Map that Makes the Cycle Visible
Once you diagnose a polarity, the method is straightforward.
A polarity map is a quadrant grid:
- Top left: Upsides of Pole A
- Bottom left: Downsides of Pole A (when overused)
- Top right: Upsides of Pole B
- Bottom right: Downsides of Pole B (when overused)
The discipline that makes the map operational is what comes next: leaders identify early warning signs that indicate drift into a downside, and action steps that keep the organisation in (or return it to) the upsides.
This is where polarity mapping becomes more than both/and rhetoric. It turns a philosophical stance into a management practice: observable signals, agreed responses, and a shared language for correction—before the system lurches into the ditch.
In an Agile setting, the planning versus adaptation debate is an easy example. Planning has genuine upsides—predictability, stakeholder confidence, resource clarity. But overdone, it becomes bureaucracy and analysis paralysis. Adaptation has genuine upsides—responsiveness, learning, customer alignment. But overdone, it becomes chaos: scope drift, burnout, and architectural erosion. Mature Agile leadership does not abolish planning. It designs a cadence: what is planned, at what level, with what review rhythm, and with what explicit permission to adapt.
This logic is not limited to Agile. It is a general organisational capability aligned with the ambidexterity literature: sustained performance often comes from building contexts and routines that support both alignment and adaptability, rather than forcing a permanent choice.
Two Cautions Senior Leaders Should Hear Early
First: Polarity Mapping is not an Excuse to Avoid Hard Choices.
There are moments when leadership is precisely the willingness to choose and to disappoint someone. Strategy requires trade-offs; refusing to choose often produces drift disguised as sophistication.
This is also where managerial cultures can get into trouble: frameworks start replacing judgement, and process becomes a substitute for reasoned authority. My esteemed PhD supervisor, Professor Robert Spillane's critique of managerialism is relevant here: managerialism tends to inflate technique and control while eroding the authority that comes from argument, expertise, and reasoned elaboration.
Second: balance is Rarely 50/50.
In high‑reliability contexts (healthcare, aviation, critical infrastructure), certain constraints are non‑negotiable. You can still manage polarities—autonomy within safety standards; innovation within architecture guardrails—but the oscillation must occur within boundaries.
A practical warning sign: if your polarity conversation never names constraints, it's not maturity—it's denial.
Where the Rest of This Series is Going
This first article is about diagnosis: learning to spot when your organisation is caught in a polarity cycle rather than a solvable problem or a strategic trade‑off.
In the next pieces I'll get more concrete:
- how to build a polarity map quickly with an executive team (without turning it into therapy).
- how to design the oscillation as an operating rhythm (metrics, reviews, decision rights) so you don't rely on swings, crises, or charismatic intervention.
- how to avoid the two classic failure modes: using polarity mapping to dodge decisions, and treating polarities as if splitting the difference is leadership.
The aim is not harmony. It is organisational adulthood: fewer adolescent debates about which virtue should win, and more disciplined governance about how to institutionalise both—deliberately, visibly, and over time.
Good night, and good luck.
Tableau I, 192 by Piet Mondrian (1872–1944) is licensed under Public Domain.
