Qualitative Coherence Indicators

Why this document exists

Organisations are installing intelligent systems into operating models they have never accurately described to themselves. The system does not inherit the organisation on the org chart. It inherits the organisation as it actually runs.

This creates a measurement problem that existing instruments do not solve. Readiness assessments measure the organisation as it imagines itself, before anything has been tested. Post-implementation reviews measure the aftermath, once the cost has already been paid. Neither captures the period when the useful information actually exists.

This document specifies what Divergent Kind measures and why. It does not publish how the measurement is scored. That distinction is deliberate and is explained in section 7.

1. What organisational coherence means

Organisational coherence is the fit between how an organisation describes itself and how it actually works, tested under load.

Every organisation runs two versions of itself at once. There is the formal version: the strategy, the structure, the documented process, the stated decision rights. And there is the actual version: where decisions really get made, which requests really get prioritised, whose call counts when two functions disagree, what happens when the pressure comes on.

Coherence is the distance between those two versions. High coherence means the description is accurate and holds under load. Low coherence means the organisation is navigating with a map that does not match the ground.

Three things coherence is not:

It is not alignment. Alignment means people agree. An organisation can be in complete agreement about a description of itself that is wrong.

It is not culture. Culture is what it feels like to work somewhere. Coherence is whether the structure holds when tested. A good culture can mask a badly incoherent system for a surprisingly long time, usually because individuals are absorbing the gap personally.

It is not efficiency. An efficient organisation can be efficiently doing work that no longer connects to anything.

2. What a coherence read is read for

Four qualities. Each is read at every level the organisation operates at, from an individual role through to a customer-facing system.

Agency. Can the people closest to the work act on what they can see? Responsibility without authority is the most common and most expensive failure. It looks like accountability on paper and produces paralysis in practice.

Reciprocity. Does the exchange run both ways across each boundary? Where value, information or effort flows in one direction only, the receiving side stops investing and the sending side burns out. Extractive patterns produce fragility. Reciprocal ones produce resilience.

Alignment. Does what people actually do match what the organisation says matters, without needing to be told each time? Alignment is visible in what gets dropped under pressure, not in what gets said in planning.

Signal integrity. Does information survive the journey? What is true at the edge of the organisation has to arrive intact where decisions are made. Signal degrades through distance, through translation, through timezone, through anyone whose position depends on the news being better than it is.

These four are what a read is read for. How each is evidenced, scored, weighted and banded is Divergent Kind's method and is not published.

3. Why the read has to happen during implementation

The strongest argument for in-flight measurement was made recently by someone outside Divergent Kind. Writing about AI implementation, independent AI advisor Stuart Winter-Tear observed that "organisational redesign for intelligent systems belongs firmly in the second category because some of the knowledge needed to redesign an organisation simply does not exist until intelligent systems begin operating inside it."

That is an epistemological claim, and it is correct. It has a hard consequence for measurement.

If some of the knowledge required to design the target operating model does not exist until implementation starts, then any instrument that runs only beforehand is not merely less convenient. It is structurally incapable of capturing the thing that matters most. And any instrument that runs only afterwards is describing a cost that has already been incurred.

A baseline read before implementation is still necessary. It establishes what the organisation believes about itself, which is exactly the claim that implementation goes on to test. But a baseline is not sufficient. The gap between the described organisation and the real one becomes visible precisely when something is asked to operate inside it.

Intelligent systems are unusually good at exposing this, because they inherit process without the human compensations that have been quietly holding it together. People route around a broken handoff without mentioning it. Systems do not. What surfaces as an implementation problem is usually a coherence problem that was already there.

4. What a Coherence Read produces

A Coherence Read produces five outputs.

Absorption. How much change this organisation can take in before coherence degrades. This is a measure of capacity, not willingness. The two are routinely confused, and high willingness paired with low capacity is the most dangerous combination in transformation work.

Composition map. How the organisation is actually put together. Where decisions are genuinely made, where work really crosses between functions, which interfaces depend on a named individual rather than a designed handoff. This is read against the formal structure, and the gap between the two is the finding.

Friction patterns. The recurring places where the system loses energy, named and evidenced. Patterns rather than incidents. An incident is an event. A pattern is a property of the design.

Structural recommendation. What to change, and in what order. Sequencing carries most of the value here, because coherence interventions applied out of order tend to fail in ways that discredit the next one.

Coherence debt. The accumulated cost of the gap, expressed as an annual range with the assumptions stated. Like other forms of organisational debt, it is carried rather than charged, it compounds while it is unaddressed, and it can be paid down. This is an order of magnitude estimate, not an audit figure, and it is presented as a decision denominator: what is the investment being measured against.

5. Cadence

Coherence is not a periodic event. It is a property that moves.

Baseline. Before implementation. Establishes what the organisation believes about itself.

In-flight. At defined intervals during implementation, tied to milestones rather than to the calendar. This is where the knowledge that could not previously exist becomes readable. It is the part of the cadence that most organisations skip and the part that carries the most information.

Closing. After stabilisation. Confirms what moved, what did not, and what the residual gap costs.

The purpose of the in-flight reads is not progress reporting. It is to catch the point at which implementation reveals that the target design was based on a description of the organisation that turned out to be wrong, while there is still time and budget to act on it.

6. What this instrument does not do

It does not diagnose, treat, or cure. Divergent Kind facilitates conditions for agency and coherence. This is not a clinical instrument and carries no clinical claim.

It does not evaluate individuals. The unit of measurement is the system. Coherence findings describe structure, not performance. Any read that produces a list of underperforming people has been used incorrectly.

It does not evaluate the AI system. This is not model evaluation, accuracy testing, or a return on investment calculation for a piece of technology. It measures the organisation the technology has been placed inside.

It does not replace leadership judgement. It makes the invisible visible. Deciding what to do about it remains the work of the people accountable for the organisation.

It is not a survey. Coherence is read from evidence of how the organisation behaves, not from self-report about how it feels. Self-report is one input among several and is never the whole read.

7. What is published and what is held

This specification publishes what is measured and why. It does not publish the scoring architecture, the evidence weighting, the interpretive bands, or the calibration data behind them.

The reasoning is not secrecy for its own sake. A measurement standard has to be publicly definable to be citable, and privately calibrated to be reliable. The definition is more useful in the open. The calibration is only meaningful in the hands of people trained to apply it consistently.

Status and citation

This is version 1.0 of a living specification. Divergent Kind will publish material revisions with version numbers and dates rather than editing silently, so that citations remain stable.