Scoreboard
What state are you trying to reach — and how do you know if you're getting there?
Three concepts. One loop. Applies to a person, a team, a venture, an organisation.
The Universal Loop
PRIORITIES → DECISIONS → INSTRUMENTS
(intended state) (change state) (bearing + position vs intention)
↑___________________________________|
| Concept | Question | Without It |
|---|---|---|
| Priorities | What state am I trying to reach? | Decisions without direction |
| Decisions | What actions change state toward intention? | Intentions without mechanism |
| Instruments | Where am I now — bearing and position vs intention? | Activity without feedback |
You can't make a decision without knowing what state you're trying to reach. You can't verify a decision worked without instruments that read the gap between intended state and actual state.
Settlement Integrity
The loop above tells you WHAT to measure. Settlement integrity tells you WHETHER what arrived matched what was promised. Three bearings — each one a different boundary where trust can break.
| Bearing | Question | What Breaks Without It |
|---|---|---|
| Internal | Do components settle cleanly between agents? | Engineering velocity without integration |
| Hemisphere | Does what's built match what's dreamed? | Spec says one thing, system does another |
| External | Does what's promised work for a stranger? | Product demos break, users bounce |
Each bearing maps to a game loop level:
| Bearing | Game Loop | Timescale | Instrument |
|---|---|---|---|
| Internal | Rendering + Gameplay | Milliseconds–Seconds | Commissioning L-levels, type checks, hook pass rates |
| Hemisphere | Core | Minutes | Feature matrix drift — spec vs reality delta |
| Velocity | Core | Weeks | Factory velocity — run rate, forecast accuracy, acceleration |
| External | Meta | Days–Years | SaaS metrics, activation rates, churn |
The VVFL only compounds when settlement reads true at ALL three boundaries. Engineering velocity with stale specs is an extractive loop — faster production of the wrong thing. The Agent Platform (Phase 4) wires autonomous verification between dream and build.
Business Names
At the business level the three concepts get specific names:
| Universal | Business Name | Question |
|---|---|---|
| Priorities | Strategy | Where are we competing? What state are we trying to reach? |
| Decisions | Pricing | What does the market say our decisions are worth? |
| Instruments | Reality | Do the instruments confirm the intended state was reached? |
Strategy without reality is wishful thinking. Reality without strategy is rearview driving. Pricing forces the question — it is the market's instrument reading on whether your strategic decisions were right.
Standards calibrate the instruments. Without them, strategy is opinion, pricing is guesswork, and reality is vanity metrics.
Fractal Loop
The same loop runs fractally — same structure, different resolution:
| Scale | Priorities | Decisions | Instruments |
|---|---|---|---|
| Individual | Where am I going? What matters? | How do I allocate time and attention? | Am I moving toward intention? |
| Team | What state are we building toward? | What work changes state? | Are we progressing or drifting? |
| Venture | Which market position? | What BD, growth, operational moves? | Does the scoreboard confirm the bet? |
| Organisation | What is our competitive thesis? | How do we execute and price? | Do instruments confirm strategy? |
The fractal is the framework. The same instruments that tell a person their bearing tell an organisation its position.
Tight Five Scorecard
The balanced scorecard asks: are we healthy across all dimensions, not just financials? Ours uses two Tight Fives scoring the same five rows from different angles: Priority (should we?) and Preparedness (can we?).
| # | Priority (should we?) | Preparedness (can we?) |
|---|---|---|
| 1 | Pain — What's broken? | Principles — Do we understand the truth? |
| 2 | Demand — What is needed? | Performance — Can we measure success? |
| 3 | Edge — What is everyone missing? | Platform — Do we have the assets? |
| 4 | Trend — Where is this heading? | Protocols — Do we know how to execute? |
| 5 | Conversion — Who needs convincing? | Players — Who does the work? |
Priority scores from the Scoring Arc: Problems → Purpose → Perspective → Predictions → Persuasion. Preparedness scores from the 5P Commissioning: Principles → Performance → Platform → Protocols → Players.
Position emerges where Priority and Preparedness intersect — where you compete is determined by what matters most AND what you're most prepared to deliver.
Priority Score = Pain x Demand x Edge x Trend x Conversion (each 1–5, max 3125). Preparedness is a profile — it shows WHERE the gaps are, not a single number.
Position Formula
| Quadrant | Priority | Preparedness | Action |
|---|---|---|---|
| Ship Now | High | High | Build and deploy — position is clear |
| Invest | High | Low | Close capability gaps before positioning |
| Harvest | Low | High | Extract value, don't expand |
| Cut | Low | Low | Stop spending attention |
Where It Lives
Every PRD carries both scores in frontmatter. The mycelium index orders by priority. The commissioning dashboard tracks preparedness. The scoreboard closes the loop between them.
Way of Being
The scoreboard measures artifacts. But the deepest metric is a way of being.
A team that flows will produce good scores. But chasing the scores doesn't produce flow. It produces anxiety, gaming, and hollow metrics. The arrow only goes one direction:
Way of being (flow) → Quality of output → Scores on the board
Never reverse it. Never optimise for the scoreboard at the expense of the state. Flow — spirit and intent meeting capability to execute — is the meta-metric that predicts everything else. Not "did the try get scored" but "was the state right when you played?"
Flow doesn't mean perfection. Flow means the spirit is right, the tools are sharp, and you're learning even when you fail. Failures inside flow are experiments, not defeats. The loop is alive. What kills agency isn't failure — it's the absence of spirit that makes failure feel like a verdict instead of data.
| Signal | What It Reveals |
|---|---|
| Time to first flow | How quickly did the session lock in? |
| Flow duration | How long before friction broke it? |
| Drift events | How many times did you lose the thread? |
| Effortless coordination | Did anyone have to explain themselves twice? |
| Close energy | Did the session end with energy or depletion? |
These aren't KPIs to optimise. They're awareness instruments. You don't chase them. You notice them. The noticing IS the practice. The practice IS the product. The quality of the loop IS the quality of the life.
This applies at every scale — a person in deep work, a team in collective flow, a human and an agent building together. Same pattern, different substrate.
Glory vs Collision
Every domain has two kinds of metrics. Glory metrics are the scoreboard — tries scored, revenue earned, users acquired. Collision metrics are the unseen work that shapes reality — breakdown speed, work rate, how fast you get off the ground.
| Type | What It Measures | Controllable | Example |
|---|---|---|---|
| Glory | Outcomes | Partly luck | Tries scored, revenue, market share |
| Collision | Effort quality | Directly | Breakdown speed, commit frequency, response time |
Dave Rennie transformed the Chiefs from last in their conference to back-to-back Super Rugby champions by ignoring the glory metrics and measuring what nobody else tracked — work rate, speed off the ground, breakdown intensity. The forwards' job was "hunting ribs," not scoring tries. The tries followed because the collisions were won.
The insight: You cannot control the scoreboard. You can control the collisions. Measure the collisions. The scoreboard moves as a consequence.
Micro-Moments
The scoreboard is an output. You move it by winning micro-moments — collisions where a standard gets followed, a threshold gets checked, a decision gets made right. Enough collisions compound and the scoreboard shifts.
COLLISION WON → POSITION GAINED → VIRTUES VALIDATED → GOODWILL SPREADS
↑ │
└────────────────────────────────────────────────────────┘
| Failure | Pattern |
|---|---|
| Optimizing the score directly | Goodhart's Law — the metric becomes the target |
| Tracking what's easy to measure | Convenience over truth |
| Treating the proxy as truth | The metric drifts from the reality it measures |
| Metrics without feedback path | The loop never closes |
| Watching the scoreboard instead of playing | Anxiety replaces agency |
KPI: the key word is indicator. It is part of the big picture of "what good looks like." The scoreboard reflects reality imperfectly and after a delay. It tells you where you are — it cannot tell you where to point. That requires first principles. Obstacles shift your bearing temporarily. The northstar stays fixed.
In positive-sum games, the collisions create value for both sides. The scoreboard reflects whether you're playing the right game, not just whether you're winning.
The Learning Collision
Every collision worth winning is a Zone of Proximal Development moment. The More Knowledgeable Other isn't always the same person — in a positive-sum collision, both sides stretch. You cannot coach without learning. You cannot teach without growing. The Tight Five says be positive, go first — but going first requires deep work to engineer pictures worth striving for. Dreams cost sweat. The collision is where that investment pays out.
| Collision Type | One Side Gains | Both Sides Gain |
|---|---|---|
| Extractive | Sale closed | Nothing learned |
| Transactional | Service delivered | Polite exchange |
| Positive-sum | Problem solved | MKO shifts — both grow |
The prompt deck berley's the collision. The deep work earns the right to show up. The scoreboard measures whether the collision compounded.
Dig Deeper
- The North Star — The fixed reference point that makes correction possible
- Strategy — Where are we competing and what state are we trying to reach?
- Reality — Do the instruments confirm the intended state was reached?
Context
- Deterministic vs Probabilistic — Measurement is deterministic verification of probabilistic predictions
- Flow — The state that predicts everything the scoreboard measures
- Collective Wisdom — When the team flows as one — the mastermind
- Priorities — Defining intended state before making decisions
- Standards — Calibrate the instruments so everyone reads the same number
- Value System — What you measure reveals what you value
- Belief System — Where priorities become direction
- VVFL — The feedback loop that compounds when instruments read true
- The North Star — The fixed setpoint the loop corrects toward
- Commissioning — The builder never validates their own work
- Pricing — The market's instrument reading on your decisions
- Control System — PID mechanics: how the correction signal works
- Game Loops — Four nested loops: rendering, gameplay, core, meta
- Agent Platform — Wiring autonomous settlement between dream and build
- Factory Velocity — Run rate, delivery forecasts, and acceleration metrics
- Work Charts — Leading indicator of AI's impact on work
- Coach Archetype — Ask, don't tell: the MKO-ZPD discipline that makes collisions positive-sum
Questions
When your instruments say one thing and your priorities say another — which do you trust, and what does your answer reveal?
- What is the difference between knowing your position and knowing your bearing?
- Which of your decisions produced a measurable state change — and which only felt like progress?
- If an obstacle forces you off course today, what is the mechanism that returns you to the northstar — and does it exist yet?