Skip to content
Method

The diagnostic frame beneath the engagement.

Organizations do not usually fail because nobody noticed the symptom. They fail because different parts of the system assign it different meanings, protect different constraints and act from different versions of reality. The method makes that structure visible enough to examine, challenge and act from.

Dispersed evidence and perspectives pass through one precise point into an ordered structure
Not every signal carries equal weight. The method makes visible which interpretation best survives the available evidence.
Sense → Interpret → Act

Intelligence is a process

Intelligence is not the amount of information an organization possesses. It is its ability to sense what is happening, interpret it accurately and act without losing the meaning between those stages. Failure may occur in any transition.

  • Relevant signals are not sensed
  • Noise is mistaken for signal
  • Different stakeholders interpret the same evidence differently
  • Trade-offs remain unranked
  • Formal decisions are not translated into operative mechanisms
  • The organization does not sense whether the intervention changed the system

The diagnostic follows the same sequence: evidence is sensed, interpretation is made explicit and intervention is tested against whether the system actually changed.

Systemic dissonance

Systemic dissonance is the structural gap between what a system intends, what its participants perceive and what its behavior repeatedly produces.

Dissonance may appear as noise, friction, misalignment, drift or tension. These are system signals—not automatic loop classifications. A form of dissonance becomes a named pattern only when evidence supports assignment to the ClarityOS taxonomy.

NoiseFrictionMisalignmentDriftTension

The Aurion Compass

Four diagnostic domains. A visible process problem may originate upstream in intent, authority, incentives, perception or interpretation. The Compass is a diagnostic frame, not a scoring device—and not every domain is equally responsible in every case.

01

Strategic Intent

What is the system trying to produce, and which priority governs when aims conflict?

02

Processes & Tools

Through what mechanisms, workflows and technologies does the system attempt to act?

03

Behaviour & Psychology

What do people actually do, perceive, avoid, protect or compensate for?

04

Intelligence

How does the system sense, interpret, learn, decide and update?

Declared, perceived and operative reality

Strategies, governance structures and processes describe how the organization intends to work. Decisions, incentives, exceptions and recurring behavior show how it actually works. The diagnostic begins where those versions diverge. Divergence is not automatically dishonesty—it may reflect missing information, incompatible constraints, informal authority, local adaptation, unresolved trade-offs, incentive design or the absence of an enforceable decision mechanism.

Declared · Perceived · Operative
Declared

“We are prioritizing enterprise growth.”

Perceived

Sales hears larger contracts. Product hears governance features. Engineering hears reliability. Finance hears higher margin.

Operative

Customer escalations and founder intervention determine priority.

Structural read

The organization shares an aspiration, but not one operational ranking.

Vantage and observer dependence

Every intake represents a vantage point. No stakeholder observes the whole organization. Different roles see different constraints. Disagreement may reveal missing data rather than resistance. An initial diagnosis may improve through challenge—model revision is part of the method, not evidence that the method failed.

A blind spot is not repaired by pretending the first account contained the whole organization.

Data collection limitation

Relevant evidence or stakeholder perspectives were not yet available.

Reasoning failure

The diagnosis contradicts evidence that was already available and sufficiently represented.

Calibration failure

The interpretation is plausible, but the output states it more strongly than the evidence supports.

Model update

New evidence changes the strongest supported explanation.

From static cause to regenerating mechanism

Aurion does not only ask what caused a condition. It also asks what sequence allows the condition to reproduce itself. A diagnostic may describe a case-specific sequence without assigning a formal loop name. Recurring friction is not always random dysfunction—it may absorb an unresolved trade-off, protect an informal authority, preserve local autonomy or allow incompatible priorities to remain active.

Case mechanism · not a canonical pattern
  1. 01

    Decision declared

  2. 02

    Valid downside surfaces

  3. 03

    The downside reopens the decision

  4. 04

    Execution moves into unresolved dependencies

  5. 05

    The deadline slips

  6. 06

    Executive intervention declares the decision again

Where evidence supports a recurring mechanism that does not fit an active taxonomy category, the diagnosis uses Unclassified rather than forcing a name.

Controlled pattern terminology

Formal ClarityOS pattern names and definitions are controlled terminology. Aurion publishes a term here only when its definition is ready for external use. Case-specific sequences can still describe a mechanism without assigning it an official category.

01 · Unclassified

Unclassified

Evidence supports a recurring mechanism that does not yet fit an active taxonomy category.

Strategic IntentProcesses & ToolsBehaviour & PsychologyIntelligence

Leverage and intervention

Leverage is the change most likely to interrupt the regenerating mechanism—not the most visible symptom, the loudest complaint or the next available tool. Intervention is sequenced against that mechanism. Removing a symptom without understanding its function can move the problem rather than resolve it.

Validation signals are defined so leadership can determine whether the intervention changed the diagnosed mechanism—or whether the read must be revised.

Evidence, uncertainty and provenance

Evidence is labeled by provenance. Observation and interpretation are kept separate. Single-perspective intake is recorded as such. Missing stakeholders are noted as blind spots rather than filled by inference. Uncertainty is stated when the evidence does not support a stronger claim.

ObservedStakeholder-reportedSystem-derivedUnverifiedMissingUnresolved

Agency and challengeability

A structural read is useful only when its evidence, assumptions and limits are visible. Stakeholders must be able to show where it is incomplete, which perspective is missing and what evidence would change the conclusion. The goal is not to make leadership agree with Aurion. It is to give leadership a model precise enough to examine, challenge and act from.

Data

The first account could not see a relevant constraint.

Reasoning

The evidence did not support the initial causal jump.

Calibration

Confidence was too high for the evidence scope.

Update

The diagnosis changes and the earlier read remains traceable.

Disagreement is not automatically resistance. It may be missing evidence.