part four · value declaration
Value Declaration
Estimating the worth of the intended change — before the cycle runs, in writing.
Value declaration is the act of writing down, in advance, what the team believes this initiative is worth if it works. It is not a forecast. It is not a guarantee. It is a number — usually a range — recorded so that the chain can later check whether the change produced what was promised.
A team that does not declare value cannot read its VRI (Volume V Part 9). A team that cannot read its VRI cannot make portfolio decisions. The declaration is the spine of the financial chain.
Three ways to declare V
Pick the form that fits the initiative.
| Form | When | Example |
|---|---|---|
| Time saved | Internal-tool, productivity, workflow initiatives | 32 hours per Gal per week, ~$X/year per grader, ~$Y/year across the customer's team |
| Revenue named | Sales, conversion, retention, expansion | 5% lift in renewal rate translates to ~$X over 12 months at current ACV |
| Cost avoided | Reliability, compliance, risk reduction | Avoiding one hour of P0 downtime per quarter is worth ~$X — current rate is one per six weeks |
The form matters because it determines what the check in Volume V will look like. Time saved checks against measured time. Revenue named checks against the revenue ledger. Cost avoided checks against the avoided-incident count.
Value as a range
A single number invites false precision. The corpus pattern: declare a range, with a most-likely value and the assumptions underneath.
Initiative: Grading Flow v2
Person: Gal (and ~120 graders across customer base)
Form: Time saved
Range: $180k – $720k / year
Most-likely: $360k / year
Assumptions: (1) Grading is 40% of grader time today.
(2) New flow saves at minimum half of that.
(3) The customer count holds.
(4) Compliance overhead is unchanged.The assumptions are the part that matters. They are what Volume II witnesses. They are what Volume V checks. A V range whose assumptions are not listed is a guess.
V as the discovery budget
V is the ceiling on what it makes sense to spend learning. The corpus pattern: discovery investment is bounded by V.
A practical rule: spend up to 5% of declared V on Discovery before deciding whether to scope. If after that the discovery questions are not answered, the initiative goes back to the portfolio for a re-decision — do we invest more in learning, or do we kill?
This is unusual. Most organisations treat Discovery as overhead. The corpus treats it as the activity that determines whether the rest of the spend will produce value or rework. A 5% discovery budget that prevents 50% of execution rework is the cheapest investment the chain makes.
V as the kill condition
A declared V also names what not enough looks like. If by the second cycle's check, the measured value is below 25% of V, the initiative is a candidate for kill review at the next portfolio meeting (Volume V Part 9).
The threshold is per-initiative — some initiatives have long curves, some have steep ones. The discipline is that the threshold is named in advance, not invented in the kill conversation.
V and rework
Volume V's VRI uses V as its numerator. To make that math honest, V needs to be:
- Written before the cycle. Not back-fitted after.
- Read at the cycle check. Did we deliver in the range?
- Adjusted explicitly. If V is moved, the move is recorded with rationale. Quiet adjustments destroy the signal.
A V that is moved without record is the corpus's version of dishonesty. The chain can survive a wrong V. It cannot survive a hidden one.
What this produces for the rest of the chain
| Volume | What it inherits |
|---|---|
| II | The discovery budget. The list of assumptions to witness. |
| III | The slicing question — which slice unlocks the largest fraction of V earliest? |
| IV | The cost ceiling — execution that exceeds 0.5×V should trigger a portfolio conversation, not a quiet over-spend. |
| V | The check value. The VRI input. The kill threshold. |