A case-in-point organisation had grown successfully by doing what most successful organisations eventually learn to do. It had developed a clear strategy, established specialised functions and built processes that allowed people to work with increasing efficiency. Each part of the organisation understood its responsibilities and had become highly capable within its own area. Nothing about the organisation appeared fundamentally disordered.
Leadership nevertheless began noticing a recurring pattern. Decisions that seemed straightforward at the enterprise level often became difficult once they crossed functional boundaries, with each group presenting a compelling reason why its own priority should prevail. Meetings produced agreement in principle, yet the same tensions reappeared when decisions reached implementation. The organisation was functioning effectively in parts while becoming progressively harder to organise as a whole.
The organisation had no obvious performance problem. Sales was focused on growth, operations on reliability, finance on discipline, product on innovation and human resources on capability. Each function had clear measures and accountable leaders, and most leaders could explain exactly what their teams were expected to achieve. The organisation had become very good at making each part work.
The difficulty emerged when those parts had to make choices together. A proposal that looked attractive from one function’s perspective could create consequences elsewhere, requiring another round of discussion before anyone could proceed. The resulting delays were initially attributed to the normal complexity of a growing organisation. The organisation’s parts were becoming more efficient without becoming more coherent with one another.
The pattern became more noticeable as the organisation pursued larger initiatives. Cross-functional decisions required increasing negotiation because different groups were applying different criteria to determine what mattered most. No one was being obstructive, and no one was acting irrationally; each group was simply protecting the priorities it had been built to serve. The organisation was producing reasonable decisions from several different points of view without a clear logic for reconciling them.
Leadership responded by introducing more coordination. Steering committees were formed, approval processes were clarified and senior leaders became more involved in resolving disputes that teams could not settle themselves. These interventions improved individual decisions but did not eliminate the recurring pattern. The organisation was adding mechanisms for coordination without changing the logic that made coordination necessary.
Over time, leaders began to notice that certain choices consistently prevailed. When speed conflicted with control, control usually won; when local opportunity conflicted with enterprise consistency, consistency usually won; and when experimentation created uncertainty, predictability usually received greater protection. None of these preferences had been formally declared as the organisation’s governing philosophy. Yet the same choices kept revealing what the organisation was implicitly organised to protect.
The pattern extended beyond individual decisions. Budgets, approval rights, reporting structures and performance measures all reinforced similar priorities, often without anyone having designed them as parts of one coherent system. A process created for one purpose would strengthen a particular behaviour elsewhere, while an incentive introduced by one function would influence choices in another. The organisation’s different elements were quietly reinforcing the same underlying logic.
The organisation continued to grow, but growth began requiring increasing amounts of coordination. Senior leaders spent more time resolving tensions between functions, while managers became skilled at anticipating which priorities would receive approval and shaping proposals accordingly. People learned how the organisation really worked without anyone explicitly teaching them. The logic of the organisation was becoming embedded in behaviour long before anyone had named it.
This did not mean that the organisation had stopped adapting. It continued launching initiatives, changing processes and adjusting its structure as circumstances required. Yet many of those changes produced variations of the same underlying behaviour because the deeper logic governing how choices were connected remained intact. The organisation was changing its visible arrangements while preserving the logic that organised them.
Leadership eventually questioned whether the structure itself was the problem. Functions were reorganised, reporting lines were adjusted and responsibilities were redistributed in an effort to make collaboration easier. For a while, the new arrangements appeared promising, but the same kinds of tensions gradually returned in different forms. The organisation had changed its architecture without changing the logic through which its parts related to one another.
The same realisation emerged when leaders revisited the strategy. The strategy was not inherently unclear, and most people could describe its major priorities. Yet when those priorities encountered competing demands, different parts of the organisation continued resolving the tension according to assumptions that had developed over time. The strategy described an intended direction, but it did not determine the deeper logic by which the organisation arranged itself around that direction.
The cost became visible in the leadership calendar. More executive time was being spent reconciling competing priorities, reviewing decisions that should have been resolved lower down and creating alignment between functions that were individually performing well. The organisation was not simply spending more time making decisions; it was spending more leadership attention making its parts work together. Organisational complexity was increasingly being paid for with executive judgement.
The cost extended beyond leadership time. Managers learned to optimise for what the organisation was most likely to approve rather than what might create the greatest value across the whole, while teams became increasingly careful about decisions that crossed functional boundaries. The organisation remained capable, but some of that capability was being consumed by navigating the logic of the system rather than advancing its purpose. The invisible cost was not inefficiency alone, but the gradual diversion of decision quality and organisational energy into managing the organisation itself.
The turning point came when leadership stopped asking which function, process or reporting line was creating the problem. Instead, they examined the choices the organisation repeatedly made and the assumptions connecting those choices. A pattern emerged: the organisation consistently arranged resources, authority and attention around protecting internal control and predictability, even when its stated ambitions required greater speed, experimentation and cross-functional integration. The organisation had an organising principle, and it was shaping behaviour whether leadership had consciously chosen it or not.
Seen through that lens, many previously unrelated problems became intelligible. The slow decisions, recurring cross-functional tensions, expanding coordination requirements and growing dependence on executive intervention were not independent failures. They were consequences of the same underlying logic governing how the organisation connected its parts and resolved competing priorities. What had appeared to be a collection of organisational problems was the visible expression of one organising principle.
The organisation had assumed that changing strategy, structure and processes would change how it operated. The case revealed something deeper: those visible elements were themselves being interpreted through an underlying logic that had become embedded in the organisation. As long as that logic remained unchanged, new structures could be absorbed into familiar patterns of behaviour. The organisation could change what it looked like without changing what organised it.
The insight also changed how leaders understood their own role. Their task was no longer simply to design better structures or communicate clearer priorities, but to examine the deeper logic through which the organisation connected choices, resolved tensions and distributed attention. Once that logic became visible, the organisation could begin asking whether its current organising principle still served the future it was trying to create. An organisation changes most deeply when the principle organising its parts changes with it.
What might be happening beneath the visible pattern that is determining how the organisation connects, prioritises and makes sense of its different parts?
Organisations often respond to what they can see: conflicting priorities, slow decisions, functional tensions, duplicated effort or strategies that fail to translate into consistent action. But these patterns may not be separate failures requiring separate interventions. They may be the visible consequences of an underlying organising principle that continues to shape the organisation in ways its leaders have not fully recognised.
Continue exploring the Organising Principle through its companion publications in the Sub-Surface Strategy™ Knowledge Library.
Each explores the same Canonical Concept from a different perspective while remaining within the same Knowledge Set.
Sub-Surface Strategy™ is both a discipline for understanding organisations and a practice for helping leaders navigate the invisible dynamics that shape organisational performance.
I work with organisations facing persistent strategic and organisational challenges that conventional approaches struggle to resolve. Together, we diagnose the invisible dynamics beneath those challenges and restore the conditions for clearer strategic thinking, stronger organisational coherence and more consistent execution.