A projected score is a plan, not a result.
A projection shows where an organization would land if a set of declared actions were carried out. It is a legitimate and useful prioritization tool. It becomes a false claim the instant someone presents it as the current state.
What the projection does
The governance roadmap takes a set of actions the organization declares it intends to carry out and computes each one's effect on the result, on the same ruler. The useful output is not the final number. It is the order: which actions return most per unit of effort, which depend on others to be worth anything, and where marginal gain stops justifying cost.
The projection uses the same calculation mode as today's score (public, or complete when there is a declaration), with current state and projected state on the same ruler. That is not an implementation detail: comparing a public current state with a complete projected one would produce a delta mixing instrument change with action effect, precisely the error a constant ruler avoids.
What it does not do
The projection observes nothing. It does not know whether the action was carried out, whether it was carried out as described, whether it survived the first operational incident, or whether it was rolled back the following week. It answers a conditional question, and the condition is supplied by whoever fills in the declaration.
That makes it useless as proof and valuable as a plan. Demonstrating that an action happened requires the path described in the other text in this series: record the prior state, execute, re-collect under the same conditions, and compare with everything declared. The projection is what you use to choose which action enters that path first.
Can I present the projected score as the program's result?
What this supports
- Using projection to sequence the program and measurement to prove it, never the other way round.
- Explicitly labeling every projection that reaches executive material, with the declared actions beside it.
- Asking, of any improvement figure, whether it was observed or estimated.
See what is outside the scope of this text
- The projection depends on the quality of what was declared. The engine consumes the declaration, it does not audit it.
- Projected gain is no guarantee of observed gain. Real execution meets constraints the declaration does not describe.