Paradox Identification and Mapping Workshop

For leaders ready to work above the problem-solving level

Every organisation solves problems. The good ones solve them quickly, thoroughly, and with discipline. But some challenges refuse to stay solved. You restructure for agility and lose coordination. You standardise for efficiency and kill innovation. You decentralise for speed and fragment strategy. These aren’t failures of execution. They’re paradoxes — and they require a fundamentally different capability than problem-solving.

The returning problem. If an issue has been “solved” multiple times by competent people and keeps coming back, it probably isn’t a problem. It’s one pole of a paradox temporarily suppressing the other. Reorganisations are the classic example: centralise, then decentralise, then centralise again, each time believing this structure will finally be right.

The inverse KPI. When your KPI tree reveals that improving one measure consistently degrades another, you’re looking at a paradox expressed in data. Improving delivery speed erodes quality margins. Increasing utilisation reduces responsiveness. Lifting standardisation scores weakens adaptive capacity. These aren’t measurement failures — they’re the organisation’s management architecture making a paradox visible. The KPI tree becomes a diagnostic instrument, revealing tensions that no single optimisation can resolve.

The permanent debate. When the same strategic argument recurs across leadership meetings — innovation versus exploitation, global consistency versus local adaptation, short-term performance versus long-term capability — the persistence of the debate is itself the signal. Smart people on both sides, neither winning permanently, because both are right.

Problems vs Paradoxes – A problem has a solution. Once you find it, the problem goes away. A paradox is a persistent tension between two things that are both true, both necessary, and apparently contradictory. It doesn’t resolve — it requires ongoing navigation. The distinction matters because applying problem-solving logic to a paradox doesn’t just fail: it creates an oscillation cycle where the organisation swings between poles, each “solution” generating the next crisis.

How to Spot a Paradox – Three diagnostic patterns reliably surface paradoxes hiding inside what looks like ordinary operational frustration.

Working with AI as a Paradox Mapping Partner – This workshop introduces a purpose-built AI thinking partner designed to help leaders structure paradoxes rather than collapse them. The AI applies a disciplined sequence: distinguishing problems from paradoxes, naming the poles in tension, mapping the costs of collapse in either direction, and generating questions that keep the tension productive. Critically, it resists the human pull toward premature resolution — asking what would be lost if the tension were dissolved, and which pole is being quietly abandoned in any proposed synthesis.

The AI doesn’t replace leadership judgment. It structures thinking so that judgment operates on the right challenge at the right level.

Workshop Outcome

Participants leave able to identify paradoxes in their own organisations, distinguish them from solvable problems, read their KPI architecture for paradox signals, and use AI-assisted navigation to hold tensions that generate energy rather than drain it.

This is Level 3 leadership capability — not solving harder problems, but developing the capacity to navigate challenges that don’t have solutions.

Course Themes

This is part of the Organising Architecture Fellowship

session

1

Strategy — Why Paradoxes Matter to Leadership

This session establishes the fundamental distinction between problems that can be solved and paradoxes that must be navigated, and why confusing the two produces the reorganisation cycle that drains organisational energy. Leaders examine where their organisation has been applying problem-solving logic to persistent tensions — and what that misdiagnosis has cost in wasted effort, lost capability, and repeated structural change.

session

2

Planning — Identifying Paradoxes in Your Organisation

Participants learn three diagnostic methods for surfacing paradoxes: the returning problem pattern, inverse relationships within KPI trees where improving one measure degrades another, and the permanent debate that recurs across leadership meetings despite smart people on both sides. Each participant maps at least one live paradox from their own organisation, names both poles, and identifies what each pole protects that matters.

session

3

Follow-Up — Working with the AI Paradox Mapping Partner

Participants are introduced to the configured AI thinking partner and its disciplined five-move sequence — from problem-or-paradox distinction through naming poles, mapping collapse costs, generating holding questions, and resisting premature resolution. Each leader works their identified paradox through the AI partner in a live session, experiencing how it challenges their habitual pull toward one pole and holds the tension they instinctively want to resolve.

session

4

Results Analysis — Reading the Costs of Collapse

TThis session develops the diagnostic discipline of recognising when an organisation has collapsed to one pole — reading the signals in KPI data, in recurring operational failures, and in the pattern of complaints that surface from the neglected side. Participants analyse historical examples from their own organisations where apparent solutions created the opposite problem, and map those episodes onto the paradox structure they identified in Session 2.

sesion

5

Discovery — Finding the Generative Questions

The shift from mapping paradoxes to navigating them productively, focused on identifying the questions that, asked regularly, keep a tension generating energy rather than confusion. Participants develop early warning indicators for when their organisation’s balance has shifted too far toward either pole, and design the sensing mechanisms — in reviews, in KPI rhythms, in leadership conversations — that would make the shift visible before it becomes a crisis.

session

6

Capability Development — Embedding Paradox Navigation in the Management System

Installing paradox awareness as an ongoing organisational capability rather than a one-off workshop insight — designing where paradox review sits in the management rhythm, how the AI thinking partner supports ongoing navigation between sessions, and how the Paradox A3 becomes a living instrument. Participants build a three-month practice plan that connects paradox navigation to their existing management routines and develops the collective capability to hold tensions that problem-solving cannot resolve.