Category

F01: Perspective

Definition
The read that is not captured is the read that never happened.
This is the mechanism behind [Informal Instrumentation] and the reason [Reactive Dangers] produces [Static Decline] so reliably. The operator reads the stage, reads the cast, reads the numbers, reads the Guest behavior. The intelligence is real. The signals are there. And then the shift ends, the next production begins, and everything the operator saw evaporates — not because the operator was inattentive but because there was no instrument to hold it. The intelligence existed for the duration of the shift and then it was gone. The next significant decision got made without it.
[The Read Log] is the instrument that closes that gap.
Not a survey. Not a performance review. Not a formal evaluation document. A captain’s log — fast, named, habitual, filled the same way every time. Three fields. Three minutes. Run after any production where the read surfaced something worth naming.
The Three Fields
Problem — what did you observe and what does it name. Not a vague unease. A named problem. Specific enough that someone else reading the log could identify the surface and the signal without additional context. “Guest table 14 waited eleven minutes for first acknowledgment” is a problem. “Service felt slow tonight” is not — it is a feeling that has not yet become evidence.
Evidence — what are the indicators, stage-side and numbers-side both. The stage-side evidence is what the operator observed in real time: the table behavior, the cast response, the kitchen timing, the Guest signal. The numbers-side evidence is what the instruments reported: the turn time, the ticket average, the comp frequency, the return rate in the VoG data. Both sides. Not one or the other. The operator who logs only stage-side evidence is running the read without the lagging confirmation. The operator who logs only numbers-side evidence is running the lagging instrument without the leading signal. Both together produce a read that can survive contact with the gate.
Solution — what does this call for and what test does it generate. Not a to-do item. A testable proposition. “Run a two-week pilot where the lead makes first contact on every table within four minutes of seating and log GX indicator data alongside cover count” is a solution. “Fix the acknowledgment problem” is not — it is an intention that has not yet become a hypothesis.
Why the Completion Is the Discipline
The act of completing all three fields is not filing. It is thinking. The operator cannot log a half-formed read. To name the problem precisely enough to state the evidence, he has to have actually identified the problem — not just felt that something was off. To state the evidence precisely enough to propose a solution, he has to have actually assembled the evidence — not just sensed that something was there. To propose a solution testable enough to become a Step 6 test with declared criteria and a defined window, he has to have actually thought through what the evidence calls for.
The log forces that completion. A vague unease becomes a named problem. A named problem becomes assembled evidence. Assembled evidence becomes a testable proposition. A testable proposition becomes an [R&D Brief] — the formal initiation of a pilot that would otherwise never have run because the informal process never forced the thinking that would have generated it.
The completed log entry is not a record of what happened. It is the initiation of what happens next.
The Compounding Mechanism
A single logged read is useful. A body of logged reads is transformative.
The operator who logs consistently across a full year has something no informal process can produce: a dated, sequenced record of what the operation was actually producing, shift by shift, read by read, signal by signal. When a pattern surfaces in the numbers — a return rate that has moved, a cast retention problem that emerged, a Guest behavior shift that the P&L has not yet caught — the operator with a [Read Log] can trace it. When did this start. What was the stage read that week. What did the cast read show. What test was run and what did it produce. The intelligence that an informal operator destroyed six months ago is sitting in the log, available, connectable, usable.
The Road 1 operator makes decisions on whatever evidence the current moment provides. The Road 2 operator makes decisions on accumulated, logged, compounding intelligence that the Road 1 operator burned. That is not a marginal advantage. It is a structural one — and it compounds with every shift the log runs and every shift the informal process does not.
What Changes Tomorrow
Run the log tonight. One entry. After your next production, before you close out, write three sentences — one for Problem, one for Evidence, one for Solution. Do not wait until you have something significant to log. Log the first notable read the production surfaces, regardless of size. The discipline is in the habit, not in the magnitude of the observation. The operator who logs consistently on small reads builds the capacity to log accurately on significant ones. Start tonight. The compounding begins with the first entry.

Explanation
See Definition.