Frameworks · AI Don't Fix Stupidity

Time to Value

Also called three clocks

Time to Value is not a project metric. A project metric asks how long *that* build took. Time to Value asks what the organisation is *capable of*, and it is the leading indicator of every other number in this toolkit.

Clocks

  1. Decision latency
  2. Build latency
  3. Absorption latency

Time to Value is how long the organisation takes to turn a recognised opportunity into value people are actually receiving. It matters more in the AI era because "the opportunity does not sit still". It is measured as three clocks with different owners and different fixes, reported separately and as a sum. Halving it does not make you twice as competitive; it moves you onto a different curve, because you capture more opportunities and each starts from a higher floor. Norvik's first capability took three months, the second three weeks.

Use it on Monday

"Report all three separately and the sum together"