You keep solving the same tensions. They keep returning. - Barry - the Business Architect and Content Creator

Some things don’t resolve. They weren’t meant to.

Every organisation faces two fundamentally different types of challenge: problems that can be solved and paradoxes that must be navigated. Most organisations treat both as problems. That’s why the same tensions keep returning.

A paradox has two valid but opposing demands, both of which the organisation needs. Consistency and responsiveness. Central control and local autonomy. Short-term results and long-term capability. Standardisation and innovation. Exploitation and exploration. These are not problems with a gap to close. They are tensions between two poles, each of which creates value and each of which, pursued alone, creates damage. Consistency without responsiveness becomes rigidity. Responsiveness without consistency becomes chaos. The organisation needs both — simultaneously, permanently, in a proportion that shifts with conditions.

A problem has a gap between what is and what should be. Defects are too high. Delivery is too slow. A process is unstable. The method is familiar: investigate the current condition, find root cause, implement countermeasures, confirm results, standardise. Problems are convergent — they close. A solved problem stays solved, provided the standard is maintained. The seven QC tools, A3 thinking, PDCA — these are problem-solving architectures. They work precisely because problems have solutions.

The navigation discipline is what replaces solving. It begins with recognition — naming the paradox explicitly rather than treating it as a problem to fix. It continues with positioning — choosing deliberately where to sit on the tension given current conditions, rather than defaulting to whichever pole has the louder advocate. It requires instruments: Paradox A3s that map both poles, the forces pulling toward each, and the consequences of over-committing to either. Architectural KPIs that measure position on the tension rather than progress toward a target — readings, not scores. Set-Based Interpretation that holds multiple hypotheses about the right position open until evidence narrows the set, rather than converging prematurely on a single answer.

Navigation also requires a development system — the organisational capability to identify paradoxes early, position on them deliberately, monitor whether the position is still appropriate, and shift when conditions change. This is architectural leadership. Not solving bigger problems. Not making better decisions.

Developing the capacity to hold tensions that don’t resolve, design the organisation to operate within those tensions, and build the collective capability to navigate rather than oscillate. The leader who masters this stops reorganising and starts positioning. The organisation that develops this capability stops oscillating between poles and starts generating energy from the tension between them — because a well-held paradox doesn’t drain energy. It produces it.