Skip to content
NarraitiveOperating Intelligence, homeAlpha

The Reading

What we read, and what we say next.

Where your company sits, what each part of it is for, what is holding the result back, and what we'd change. How the company is put together is read from the work itself, never from an org chart.

AI

AI reads your records. People make the decisions.

Scale

Build the operating system once. We keep it running.

Entity one and entity forty get the same reading. You retain authority at every step.

Operations

What we run each week

Each week we update one record of what was decided, what is out of bounds, what is ready, what was certified, what was approved and what was released.

Connect · Form · Find · Fix · Prove

The AI reads. You decide.

  1. 01

    Connect

    What the AI does
    We read the records you permit.
    What you do
    You choose the boundary and the sources.
  2. 02

    Form

    What the AI does
    We form how the company works from those records.
    What you do
    You correct the reading in your own words.
  3. 03

    Find

    What the AI does
    We show what is holding the result back, with its baseline.
    What you do
    You decide whether it matters.
  4. 04

    Fix

    What the AI does
    We propose one change, then carry the approved work and its evidence.
    What you do
    You approve the change and name its owner.
  5. 05

    Prove

    What the AI does
    We compare the result with its baseline and say whether it was kept.
    What you do
    You verify whether it was kept.

How work actually moves

The people, systems and records work actually passes through.

Structure is read from observed flow, not from an org chart.

Detail

Select any part of the picture to read what it is and why it is shown.

We do not score employees or infer personal worth. We show how work moves, where it waits, how calls travel, and what was kept — with its source.

  • Observed
  • Waiting on
  • Stopped on
  • Kept

We do not score employees or infer personal worth. We show how work moves, where it waits, how calls travel, and what was kept — with its source.

Did it work

Read it back, and see what actually changed.

What moved today, the call you made, the work that followed, and whether it showed. No invented figures.

Change movie · OutcomeNeutral sample — no company data

What changed
The outcome was verified and the model updated.
Why
The graph learns from what happened, not from what was planned.
Who was authorized
Verified by a named person, separately from the doer.
Evidence
Verification attached; timing alone is never treated as cause.
Outcome
Verified.
  • Observed
  • Waiting on
  • Stopped on
  • Kept

Installation

Twelve weeks, if you go on to install

This is the shape of an Installation, not a promised outcome.

  1. 01

    Weeks 1–2 · Connect

    Map sources and ownership

    Source map and work inventory

  2. 02

    Weeks 3–4 · Form

    Confirm how the company works

    The story so far, with unknowns

  3. 03

    Weeks 5–8 · Find and Fix

    Name the constraint and design the change

    The Reading and an approved change

  4. 04

    Weeks 9–12 · Prove

    Record completion and verify the result

    Did it work, on the record

Where the method comes from

The questions are fifty years old. The evidence is new.

Find · Fix · Prove runs the focusing steps Eliyahu Goldratt set out in the Theory of Constraints: find the constraint, subordinate everything else to it, act, then look again. Consultants work these steps in workshops, from memory and interviews.

Here, every step must carry its records. A constraint is a count of what the record holds. A conflict is two sources, quoted. A change appears only when its trigger fired and its evidence is held. Nothing advances on our say-so.

Method after Goldratt's Theory of Constraints. The evidence-binding is ours.

The boundary

Bounded is not comprehensive.

A Reading shows what the evidence in front of it supports. It does not show the company.

  1. 01

    Here is what the evidence shows.

  2. 02

    Here is what it does not show.

  3. 03

    Where is this wrong?

Those three lines open every early session. Unconnected activity stays unknown rather than being guessed at, and a correction from someone who was there outranks anything we assembled. Corrections are recorded against the claim they change, and the record only ever grows.

Scale

Then it scales

The Reading on one entity becomes the same Reading on every entity at Installation. The fixed fee is priced per entity.

The next call

Bring one consequential operating question. We will start with the record.

Request a Reading