Every leader knows the A3. The single-page discipline for structured thinking — define the problem, analyse the current state, identify root cause, design countermeasures, confirm results. It is one of the most powerful management tools ever developed, and it works superbly for problems. The difficulty is that not everything leaders face is a problem.

The method begins with mapping the two poles — not as good versus bad, but as two genuine goods in tension. What does each pole protect that matters? What would be lost if either pole won completely? This steelmanning discipline is essential because most organisations have a preferred pole they’ve quietly declared correct and an opposing pole they’ve labelled as the problem. The Paradox A3 forces both poles to be taken seriously before any navigation begins.
From there, the instrument locates the organisation’s current position on the continuum between poles, designs navigation moves that hold both poles rather than collapsing to one, and establishes the indicators that signal when drift has gone too far in either direction. The sensing architecture is what makes this a living practice rather than a one-time exercise. Without indicators, leaders discover they’ve collapsed to one pole only when the crisis arrives from the neglected side.

When a tension persists despite repeated competent intervention — when centralisation solves coordination but kills responsiveness, when the fix for that creates fragmentation, when the reorganisation cycle repeats every three years with smart people on each side of the argument — the standard A3 becomes the wrong instrument. Not because the discipline is flawed, but because the underlying logic assumes closure. Find the root cause, implement the countermeasure, confirm the result, close the A3. Paradoxes don’t close. They require a different instrument built on a different logic.
The Paradox A3 modifies the A3 format for challenges that persist. Where the standard A3 follows a Plan-Do-Check-Act cycle that moves toward resolution, the Paradox A3 follows a Position-Navigate-Sense-Develop cycle that moves toward sustained navigation. The difference is structural, not cosmetic. PDCA assumes you can find the right answer. PNSD assumes you must find a viable position between two answers that are both right and apparently contradictory.

This programme develops Paradox A3 capability through six sessions that move from understanding why paradoxes need their own instrument, through building and navigating live Paradox A3s on real organisational tensions, to embedding paradox review in the management rhythm as a permanent leadership practice. A purpose-built AI thinking partner plays a specific role: it resists the human pull toward premature resolution, challenging proposed moves that look like synthesis but are actually one pole dressed up as balance.
The programme requires Set-Based Interpretation as a prerequisite. You cannot navigate a paradox you haven’t correctly identified, and you cannot correctly identify a paradox without the observation discipline that distinguishes it from a problem. The Paradox A3 takes what Set-Based Interpretation surfaces and gives it structure, turning insight into sustained organisational navigation.
Programme
This programme is part of the Organising Architecture and Culture Fellowship, for individuals, teams and organisations – reach out if you are interested in additional information as to content and scheduling.
session
1
Strategy — Why Paradoxes Need Their Own Instrument
The standard A3 is designed for problems that close — you find the root cause, implement the countermeasure, confirm the result, and move on. This session establishes why applying that logic to paradoxes produces the oscillation cycle, and why the modified PNSD cycle — Position, Navigate, Sense, Develop — is structurally different from PDCA in ways that matter for how leaders think about their work.
session
2
Planning — Mapping the Poles and Locating Your Position
Participants take a paradox identified through Set-Based Interpretation and build the first sections of their Paradox A3: naming the two poles, articulating what each pole protects that genuinely matters, mapping the costs of collapse in either direction, and locating where their organisation currently sits on the continuum. The discipline here is ensuring both poles are steelmanned as genuine goods — if one pole is secretly the villain, it’s a problem, not a paradox.
session
3
Follow-Up — Designing Navigation Moves That Hold Both Poles
The critical shift from mapping to action, where participants design interventions that hold the tension rather than resolve it. Each navigation move is tested against the question: does this action serve both poles, or does it quietly abandon one while claiming balance? The AI thinking partner plays a specific role here, challenging proposed moves that look like synthesis but are actually one pole dressed up as integration.
session
4
Results Analysis — Sensing Drift and Reading the Indicators
Participants develop the indicators that signal when their organisation’s position has shifted too far toward either pole — reading the signs in KPI data, in the pattern of operational complaints, and in the recurring arguments that surface in leadership meetings. This session builds the sensing architecture that makes paradox navigation an ongoing practice rather than a one-time positioning exercise.
session
5
Discovery — Working the PNSD Cycle on a Second Paradox
With one Paradox A3 now in active navigation, participants apply the full method to a second paradox, moving through the cycle with greater fluency and beginning to notice how different paradoxes interact with each other. This is where the need for the Architectural Linkage Diagram begins to emerge naturally — participants sense that their paradox positions connect but don’t yet have the instrument to make those connections visible.
session
6
Capability Development — Embedding Paradox Navigation in the Management Rhythm
Installing the Paradox A3 as a living document that sits alongside the organisation’s existing A3 practice and management review cycle. Participants design where paradox review belongs in their leadership rhythm, how the AI thinking partner sustains navigation discipline between reviews, and how they will develop this capability in others through coaching rather than instruction — because paradox navigation cannot be taught from slides.