The speech vs. the scoreboard · one sitting

The
Coherence
Check

Every organization tells you what it values twice: once in the speech leadership gives, and once on the scoreboard it actually keeps, in dashboards, minutes, and reply threads. This check measures the distance between them. It takes about forty-five minutes, because most questions ask you to open a document before you answer.

How to take it honestly

One rule governs every question: the evidence must be something you did not author. Your own memos say what you transmitted; only the org's documents say what was received. Fetch the artifact, then file what it says into a bin. The page never sees your documents: you do the reading, it only records which bin you picked. Answering from memory turns this into the conversation you've already had.

Leadership describes the operating model as...
The receipt: Write down the success metric of your biggest current bet. Now search last quarter's exec-level documents: the quarterly review deck, the board update, the staff-meeting minutes, the shared dashboards. Where does that metric appear?
The receipt: Open the dashboard or tracker the exec team actually looks at. Not the one you wish they looked at. The rows for product initiatives are judged by...
The receipt: Find where the last flat or negative lagging indicator landed: the thread, the meeting notes, the channel. The first reply from outside your own org was closest to...
The receipt: Check the last three things celebrated in company-wide forums: all-hands, newsletters, the kudos channel. They were...
The receipt: Search your inbox and chat for the last time another exec sent your org a problem without a solution attached. When was it?
The receipt: Recall the last date that slipped while its metric moved, and the last date that held while its metric stayed flat. If the threads exist, open them. Which drew the exec attention?
The receipt: Open last quarter's planning commitment. Not your memo about it: the artifact other execs would point to if asked what your org owes them. It lists...
The receipt: No documents for this one, and it's the one answer you author. Treat it as a prediction, and check it against the next real kill. You announce at exec staff: “We killed the quarter's biggest bet in week two. The signal was bad. It cost us $40k instead of $400k.” The most likely first reply from outside your own org is...
Last one, and it's a registered prediction, not a receipt. Ask each exec at your table for the quarter's bookings number and they'll have it. How many could also name, unprompted, the metric your biggest bet must move?
1 / 10
What this measures, and what it doesn't

A distance has no rung

It's tempting to read this as the nine-stage curve at executive altitude, and the temptation is half right. The behaviors on the scoreboard side of this check are the demand side of the upper rungs: problems handed over instead of solutions, a flat indicator read as signal instead of failure. That's the same phenomenon the curve measures, seen from the exec floor.

In fact the scoreboard side does map onto the curve, as a wide band: four levels here instead of nine rungs there, because an exec's reading should be coarser than a builder's. What can't be placed is the check's actual finding: the distance between that band and the model leadership states. Two organizations can sit at the identical rung where one knows it and one believes it's somewhere else. The curve can't tell them apart, and the difference decides everything, because an org that believes it already runs on problems and bets will spend nothing to become what it thinks it is.

So read the two instruments together. The curve locates the work and names the seam that holds the ceiling. This page measures whether leadership can see the ceiling at all. When one function's rung outruns the org around it, that gap has a name too: the velocity wall.