In the previous articles in this series, I’ve argued that:
Quality is what customers need, not what organisations label as “good.”
Cost reduction is not the same as efficiency; work must be understood before it is changed.
Systems learn when they develop the capacity to sense and adapt.
Coherence is the measure of whether that learning strengthens or drifts.
This article moves from theory to practice: If coherence is the measure, how do organisations design for it?
Most organisations don’t fail because they lack intelligence. They fail because their architecture pulls in contradictory directions.
Coherence is not a mindset shift.
It is an architectural discipline.
Designing for Coherence
Coherence emerges from how purpose, roles, workflows, policies, decision rights, and technology interact under pressure.
When these reinforce one another, systems flex.
When they collide, systems fragment.
To design for coherence, leaders need principles that shape the underlying architecture of the organisation, not slogans, but structural rules which are designed to create choices.
1. Accountabilities are set as far down the organisation as possible to where the expertise lies, or information converges
This principle emphasises vertical decentralisation of decision-making to leverage expertise and situational knowledge. By positioning accountability at lower organisational levels, an organisation empowers those with direct insight and relevant skills to make timely, informed decisions. This reduces bottlenecks, promotes agility, and builds a culture of ownership across teams. It also aligns decision authority with proximity to data and context, leading to more efficient and relevant actions.
2. Standardisation is the default except where there is a demonstrated net benefit at a whole of organisation level
Standardisation supports efficiency, consistency, and scalability across an organisation. This principle ensures that processes, policies and systems remain streamlined, reducing the complexity that comes with custom solutions. However, it allows for exceptions where a compelling, enterprise benefit can be demonstrated, balancing flexibility with efficiency. By establishing standardisation as the norm, resources are conserved, and only high-impact deviations are allowed, ensuring a pragmatic approach to customisation.
3. Activity is grouped for interdependency unless technology can co-ordinate
Grouping interdependent activities strengthens cohesion and optimises workflow by reducing the need for excessive communication and coordination across separate units (e.g. committees, projects, reporting). Where technology can provide effective coordination, however, teams have the flexibility to operate more independently.
Grouping interdependent work further away from one another in an organisation which may be necessary when there is a higher priority interdependency with another group. This principle accounts for necessary trade-offs when considering how work is grouped in the organisation and where technology is best invested, reducing duplication of efforts and enhancing cross-functional alignment.
4. Decisions are prioritised and optimised to deliver and sustain the mission
Prioritising and optimising decision making processes ensures that institutional resources and efforts remain focused on mission critical objectives. Optimised means that the decision is analysed on the basis of maximising return (the risk weighted calculation of benefits minus cost) and prioritised means that decisions in aggregate are analysed for highest return whilst acknowledging that an organisation has finite resources. Benefit refers to the macro, meso and micro societal value generated from a decision in addition to the financial, where latter’s purpose is to be reinvested in order to sustain the mission.
5. Innovation enables distinctiveness. Quality enables scale
This principle recognises that innovation is key in differentiation, fostering unique offerings and enhancing its competitive edge and a focus on quality ensures that scalable solutions maintain high standards, supporting growth without compromising effectiveness. Whilst both are important, they are different but not mutually exclusive concepts, and their application is situation appropriate. The bounding conditions for innovation and quality are that: failure is acceptable in innovation and intolerable with respect to quality; not all innovation is distinctive, but all distinctiveness must be innovative; and not all quality is at scale, but all scale must be at quality.
By positioning innovation as a driver of distinctiveness and quality as the foundation of scalable operations, this principle balances creativity with rigour, supporting both reputation and capacity to operate efficiently at scale.
Why These Principles Matter for Coherence
These principles shape the five coherence dimensions introduced in Article 4:
Alignment: Standardisation, mission-aligned decision optimisation, and accountability near expertise ensure behaviours point in the same direction.
Resonance: Grouping interdependencies and technology-supported coordination improve the flow of information and intent across the system.
Resilience: Quality at scale and standardisation create stability under stress; decentralised accountability distributes adaptive capacity.
Drift Control: Clear decision logic, innovation/quality boundaries, and defined exceptions reduce unintended variation and fragmentation.
Redundancy Reduction: Grouping interdependencies, reducing workarounds, and eliminating bespoke exceptions remove duplicated effort while protecting essential slack.
Coherence is not just the absence of noise.
Coherence is the ability of the system to hold its shape when the noise arrives.
These principles are how that shape is formed.
WorkLattice: Mapping and Measuring Coherence
To design for coherence, leaders must be able to see it. WorkLattice provides this visibility by treating the organisation as a living, evolving graph rather than a static chart.
It uses a GraphRAG architecture (retrieval-augmented generation over a relational graph) rather than over documents. The graph encodes:
work
policies
decision rights
interdependencies
information flows
temporal changes
And drawing from quantum-inspired analytics it runs perturbation tests:
Resilience: how the system behaves when a node or dependency changes
Resonance: how signals propagate
Drift: how behaviour diverges from intended design
Redundancy: where overlap accumulates
Alignment: how purpose links to performance pathways
WorkLattice is not an “AI overlay.”
It is the organisational nervous system:
sensing
interpreting
stress-testing
and reflecting the system back to itself
Every principle above becomes something that can be measured, modelled, and iterated - not abstract aspiration, but operational reality.
Looking Ahead: Decision Systems
If coherence is the architecture of an organisation, decisions are its metabolism.
Article 6 will examine:
how decisions actually propagate across a system
how formal and informal authority collide
how incentives distort alignment
how decision drift becomes the earliest sign of fragmentation
and how systems can help leaders maintain decision discipline without centralising power
Reflection
If coherence is the shape of your organisation, what holds that shape when the pressure hits — deliberate design, or accumulated habit?
