Chapter 7 · Self-Understanding and the Formal Core

What we discuss in this chapter: Organizational self-understanding by no means arises from piling up more documents, but through a precise consolidation semantics that makes contradictions between cross-source bodies of knowledge visible and deliberately decidable. The formal claims model, the conflict_record, the decision procedure of the Four-Zone Review, the identified gap (gap_record), and a fully worked-through calculation at Muster AG give this layer its operational sharpness.

Your leverage as a decision-maker: Your organization already contradicts itself in countless places invisible to management—until a strategic decision, an internal audit, or an operational failure painfully exposes these conflicts. Formal conflict semantics transform blind spots into a manageable backlog. This shifts self-understanding from a vague cultural debate into a concrete infrastructure task with a prioritized backlog.

---

7.1 The Weick Connection: Sensemaking as Model and Tension

Karl Weick provided the authoritative scientific description of how organizations arrive at a picture of themselves: through sensemaking—the retrospective structuring of experienced practice into plausible narratives. This perspective brilliantly explains the phenomena we observed in Chapter 1. It clarifies why three different functional departments describe the exact same core process completely differently, each believing its version to be the only plausible one. That organizational self-understanding is constructed rather than pre-existing as objective truth is Weick's central insight, and this theoretical heritage is explicitly acknowledged in our model.

At the same time, Weick's sensemaking approach introduces a fundamental tension for management.

Human sensemaking strives primarily for plausibility, not mathematical precision.

People in organizations require a viable narrative that provides orientation, not a sterile database. An operational infrastructure for self-understanding must neither deny nor mimic this human characteristic.

It does not deny it, because it acknowledges that every source in the body of knowledge represents a perspective interpretation rather than neutral absolute truth. Nor does it mimic it, because it delivers precisely the capability that narrative sensemaking fundamentally lacks: placing differing versions side by side in a structured manner and explicitly highlighting discrepancies. The formal core in this chapter is engineered specifically for this purpose: not as an automated truth machine, but as an uncompromising detector of contradictions.

This chapter describes the semantics of an Organizational Intelligence System: what must be logically maintained for self-understanding to emerge. It describes no technical implementation. Which databases, pipelines, and interfaces a platform uses to implement this semantics remains a vendor decision and belongs in the reference architecture (Chapter 13).

7.2 The Smallest Unit: The Claim

To make self-understanding operational, existing knowledge must be decomposed into testable building blocks:

Definition 7.1 — Claim (Knowledge Unit).

A Claim is the smallest independently testable statement an organization makes about itself, maintained with at least four attributes: Content (what is asserted), Source (where the statement originates), Context (where it applies), and Validity (status and approval state).

Based on: van der Aalst 2016 (formalization as a prerequisite for analysis; methodological model from process mining research for event data). Boundary of source: Process mining formalizes observed behavior from event logs; declared statements regarding responsibilities, intentions, and formal rules lie outside its scope.

Necessary extension, our position: The same formal rigor is applied to declarative self-knowledge rather than mere technical process traces.

Source: Case B (Ch. 11): Decomposition of a process architecture into testable units; corpus size, benchmark value from ongoing initiatives: approximately 1,400 process elements.

The technical representation of a Claim can be illustrated using a concrete example from Muster AG's repository:

claim MA-0412
  content:    "Class B complaints are decided by site QA."
  source:     QM Manual, Section 8.3 (2021 Version)
  context:    North and South Sites, Series Production
  validity:   approved; last audit 2023

This decomposition into clean individual Claims appears unspectacular at first glance. Its strategic leverage unfolds in the next step, when different source systems addressing the same operational issue are consolidated.

7.3 Consolidation Across Sources: Three Outcomes — and a Fourth Finding That Cuts Across Them

When two or more source systems are consolidated into the same body of knowledge, three logical outcomes of the source comparison emerge for each individual matter.

First: the versions at hand are congruent. In this case, organizational confidence in the statement rises, because several independent sources support the same practice.

Second: the versions diverge in substance. Here, an explicit conflict object is instantiated, remaining managed within the knowledge base until an authorized decision is rendered.

Third: a matter is documented in only a single source. This immediately makes the existing gap in the remaining systems transparent. This third outcome deliberately creates no clarification object of its own: the statement itself is present, only its confirmation by further sources is missing, and this thin evidence base is tracked as an attribute of the Claim. Only when a requirement mandates that the statement also be maintained in a specific additional source—such as a work instruction also appearing in the QM manual—does the missing proof turn into an expected but missing statement in the sense of the fourth finding below.

All three outcomes yield valuable insights; however, the second outcome provides by far the most powerful leverage.

It highlights for management precisely those areas where the organization contradicts itself before severe missteps, audit non-conformities, or quality incidents quietly occur. Edwin Hutchins' research on Distributed Cognition supplies the theoretical vocabulary: the overall system's knowledge exceeds the sum of individual repositories precisely because structured synthesis exposes productive discrepancies invisible within any isolated single source. This requires no magic, only disciplined accounting.

A fourth finding cuts across these three outcomes, because comparing sources does not bring it to light on its own: the blank spot. What is meant is the area of the organization that is documented in none of the connected sources — the not-yet-organized organization. Such gaps do not become apparent because two versions collide, but because an expected statement is missing. How that expectation comes about determines the stage at which the gap becomes visible in the first place, and two levels of detection must therefore be distinguished:

• Schema-induced gap. An already existing reference framework expects a claim that is missing from the body of knowledge: a process reference model names a step for which no statement exists; an organizational chart lists a unit whose workflows the body of knowledge is silent about; a catalog of standards demands evidence that nobody has filed. This check is a pure target-actual comparison against a given schema. It therefore belongs to building Self-Understanding and can already be accomplished at that stage.
• Intelligence-induced gap. The expectation itself is new: the system derives it from patterns within its own body of knowledge, from scenarios played through, or from external reference knowledge — for instance, that a unit of comparable scope elsewhere maintains an escalation rule that is missing here. No existing schema demands this statement; the expectation is generated. This is an achievement of Organizational Intelligence (Chapter 8) and presupposes the preceding stages.

In both cases, reference frameworks enter the reconciliation as expectation providers, not as an additional source of Claims: a standards catalog documents what ought to be regulated, not how the organization actually operates. Only with this distinction does the concept of the white spot remain free of contradiction—the expected statement is documented in no connected source, even if the expectation itself exists in writing.

Both levels lead into the same object. Section 7.6 introduces it; the derivation of the expectation is carried along within it, so that it remains recognizable what the gap rests on.

A Factor of 4.45 Between Two Teams

What happens when two sources implicitly assert incompatible rules in the same context without an institutionalized check was demonstrated with tragic clarity in space exploration in 1999. The ground software from contractor Lockheed Martin calculated thrust data for the Mars Climate Orbiter in imperial pound-force seconds; NASA's navigation software expected metric Newton-seconds according to the interface specification. Both teams performed flawlessly for months—except using figures that differed by a factor of 4.45. On September 23, 1999, the spacecraft plunged too deep into the Martian atmosphere and disintegrated; the orbiter and lander program had cost $327.6 million in total. The investigation report's takeaway: the authoritative specification had existed all along; there was simply no procedure that systematically reconciled the declared assumptions of the parties involved. Exactly this unspectacular check is delivered by a conflict object. The alternative is letting physics perform the review.

— NASA Mars Climate Orbiter Mishap Investigation Board, Phase I Report (1999)

7.4 The Conflict Object

For the targeted management of contradictions, the conflict_record is introduced as a dedicated analysis object:

Definition 7.2 — conflict_record.

A conflict_record is the normalized state of two or more Claims asserting incompatible content in the same context; it captures the involved Claims, discrepancy type, decision status, and, post-decision, the approved version alongside its rationale.

Based on: van der Aalst 2016 (conformance checking as a model: deviation as an analysis object in its own right). Boundary of source: Conformance checking compares target process models with actual logs; the direct comparison of declared target rules against each other, and their resolution under named decision accountability, fall outside this method.

Necessary extension, our position: The contradiction turns from an ephemeral finding into a permanently managed object with a defined lifecycle (open, under review, decided, obsolete).

Source: Case C (Ch. 11): conflict density per 100 claims between two system landscapes, indicative value from ongoing initiatives: 19.

The fully defined lifecycle represents the crucial advancement over traditional consistency checks. An identified conflict does not quietly vanish by being overwritten; it is resolved exclusively through a documented management decision. The historically superseded version remains traceable in the version history. This exact characteristic guarantees total auditability of the knowledge base.

7.5 The Decision-Making Process: The Four-Zone Review

To process open conflict objects efficiently without time-consuming, endless political debates, a structured evaluation process is applied:

Definition 7.3 — Four-Zone Review.

A review procedure assigning every open conflict_record to exactly one of four zones: Zone 1: trivial discrepancy, resolvable editorially; Zone 2: genuine substantive divergence, subject-matter decision required; Zone 3: justified variance, both versions hold in distinct contexts; Zone 4: resolution impossible or uneconomical, conflict is retained as an explicit risk.

Based on: Argyris/Schön 1978 (distinction between espoused theory vs. theory-in-use as a model for Zones 2 and 3). Boundary of source: Chris Argyris and Donald Schön masterfully diagnose the gap between stated and practiced routines, but offer no operational procedure to decide case by case.

Necessary extension, our position: A repeatable operational procedure featuring clear zones, defined roles, and mandatory approval obligations.

Source: Case B (Ch. 11): Four-Zone Review of program variants with domain owners; zone distribution. Benchmark value from ongoing initiatives: 32% Zone 1, 21% Zone 2, 43% Zone 3, 4% Zone 4.

For the Four-Zone Review to function reliably in corporate practice, the workflow is meticulously structured around roles, decisions, and versioning:

Who sits at the table? The review panel comprises the respective Decision Owner (process owner or quality manager with formal decision-making authority), the domain experts from the affected source systems, and the Governance Lead (architect of the knowledge layer). This panel convenes in fixed cadences. If no Decision Owner has yet been designated for a conflict — for instance because it cuts across established responsibilities — then designating one is the panel's first decision and is documented like any other.

What is concretely decided across the four zones?

• Zone 1 (Trivial Discrepancy): The Governance Lead resolves linguistic or syntactic differences directly through editorial updates without involving domain leads.
• Zone 2 (Genuine Substantive Divergence): The Decision-Owner makes a binding domain decision favoring one of the variants.
• Zone 3 (Justified Variance): The Decision-Owner confirms that both rules are fully justified, but strictly segregates their applicable contexts (e.g., by facility, product line, or regulatory jurisdiction).
• Zone 4 (Managed Conflict): If a conflict cannot be resolved immediately due to economic or political constraints, it remains in the system as an explicitly flagged risk rather than being concealed.

What is versioned? Every review outcome generates an immutable Decision Record. This logs the selected target Claim, archived former Claims, the Decision-Owner's rationale, effective dates, and sunset clauses for temporary exemptions.

Zone 3 warrants special attention, because it protects management from the knee-jerk error of "harmonization mania." Not every deviation between two sites is a mistake. Many discrepancies turn out to be highly justified local adaptations. The procedure forces the organization to document this difference explicitly instead of bulldozing it in the course of blanket centralization initiatives.

7.6 The Identified Gap: the gap_record

The blank spot from Section 7.3 receives, as a third class of object alongside claim and conflict, an object of its own that is maintained permanently:

Definition 7.4 — gap_record (identified gap).

A gap_record is the managed record of a statement an organization would be expected to make about itself but that is documented in none of the connected sources; it carries the expected subject matter, the level of detection (schema-induced or intelligence-induced), the derivation of the expectation, the clarification status and, where designated, the organizational responsibility.

Based on: Wilensky 1967 (information pathologies: what is not collected as a management risk in its own right). Boundary of source: Wilensky diagnoses the blind spots of organizational information gathering, but supplies no procedure for systematically generating, managing, and deciding them.

Necessary extension, our position: The gap is framed, analogously to the conflict_record, as a managed object with a lifecycle (open, under clarification, closed through documentation or through a justified decision not to regulate).

Indicators: (1) gap rate — the share of expected but unevidenced statements per reference framework; (2) closure rate — the share of opened gap_records that are closed within one approval cycle through documentation or a justified decision not to regulate.

Source: open — here this definition deliberately departs from the others. There is no case anchor from Chapter 11: in Cases A through D, consolidation started from the source comparison, and gaps were not collected there as a distinct class of object. Both indicators are therefore constructed and not empirically calibrated. They are carried as research metrics (Challenge H1, Chapter 18) and are not part of the measurement catalog of the six collected key figures (Chapter 10).

The decisive difference from the conflict object lies in the question of responsibility. With a conflict, at least the parties involved can be named with certainty: the contradicting claims and their sources. Who decides between them is not thereby settled — assigning a Decision Owner can itself be a matter for governance work. With a gap, even this starting point is regularly missing, because a gap arises precisely where the organization has so far entrusted nobody with the subject matter. In both cases, therefore, the same rule applies: if no responsibility can be named, assigning it is the first step toward clarification and is documented as such in the object. Only then can the organization decide whether the gap is closed through documentation or carried, with justification, as a deliberate decision not to regulate. Both are legitimate outcomes; what the gap must not do is remain undetected.

A second difference is technical in nature. A Claim describes a fact about the organization; a gap_record describes the result of a reconciliation as of a specific date. It is therefore re-evaluated whenever the body of knowledge changes: if the expected statement appears later—through new documentation or a newly connected source—the gap closes with a reference to the new Claim. A justified non-regulation, by contrast, remains as a documented decision until its foundation changes.

7.7 Muster AG, Worked Through in Full

Let us trace the procedure step by step through a concrete walkthrough at Muster AG.

Step 1: Capture of Contradictory Claims. Muster AG's QM manual specifies in Section 8.3: Class B complaints are decided by site Quality Assurance (Claim MA-0412). Conversely, the newer process wiki asserts under Quality: Since the 2024 reorganization, these are decided exclusively by the central Quality Board (Claim MA-1873). Both assertions claim validity within the exact same operational context (series production) and are mutually exclusive.

Step 2: Automated Generation of the Conflict Object. Reconciling both source systems, the formal core detects the incompatible content and automatically creates the object conflict_record CR-0087 with status open.

Step 3: Categorization in the Four-Zone Review. During the review session with the VP of Quality and site QA leads, the case is evaluated. Fact-finding reveals: at the North facility, the central board decides; at the South facility, local QA continues to decide. This is not a linguistic discrepancy, but genuine substantive divergence (Zone 2).

Step 4: Decision and Context Mapping. Quality leadership mandates that the central board rule serves as the company-wide standard. However, a temporary exception is granted for the West facility, which performs custom manufacturing.

Step 5: Versioned Storage in Memory. The knowledge base subsequently stores three elements:

1. The approved standard Claim MA-1873 (validity: enterprise-wide).
2. A new exception Claim MA-1874 with explicit context West Facility, Custom Manufacturing and a twelve-month sunset clause.
3. The historical Claim MA-0412, archived as obsolete (replaced by CR-0087).

To the opening question from Chapter 5 regarding how a complaint at the South facility is actually processed, an unambiguous, verifiable answer now exists—complete with clear status and an assigned Decision-Owner. This is precisely what this theory defines as organizational self-understanding: not metaphysical contemplation, but verifiable information capability in previously contested areas.

Case Study — Case B: A global rolling stock manufacturer operates its modeled process architecture across multiple vehicle programs in countless variants whose actual validity is understood by only a few key individuals. Systematic consolidation with automated conflict detection and subsequent Four-Zone Review transforms paralyzed political harmonization debates into a rapidly actionable backlog. → detailed in Chapter 11.

7.8 Boundaries of the Formal Core

Two essential boundaries of the formal core must be emphasized in conclusion: they are integral components of the theory, by no means deficiencies. First, automated Claim extraction from unstructured repositories using modern AI does not achieve flawless accuracy today. Final human verification therefore remains constitutive (current research on this is synthesized in Chapter 18).

Second, the formal core itself makes no domain decisions whatsoever. It merely renders decision-worthy points unmistakably visible and makes enacted decisions permanently durable. Who holds authority to decide within the enterprise, under what legitimacy, and within what timelines is a question of governance, addressed in Chapter 14 and Chapter 15. Only on this secure foundation can we meaningfully address the third rung: what it concretely means when an organization decides intelligently.

💡 What We Discussed

Organizational Self-Understanding requires a precise structure that decomposes declared rule knowledge into testable building blocks and sharply contrasts divergent assertions.

Using structured records, the procedure turns unnoticed friction losses into manageable objects that are resolved in an orderly way through a four-zone scheme; the absence of expected statements is likewise carried as an identified gap instead of being overlooked.

This establishes binding decisions with an unalterable history, allowing your leadership team to base complex process decisions on verifiable foundations.

On this secure foundation, the following chapter clarifies how the qualities of Intelligence and Capabilities unfold in daily operations based on reliable self-knowledge.