Velocity
Velocity is estimated Atomic Units divided by actual Atomic Units consumed. It measures how effectively a person, team, or firm converts standard work into finished output.
Formula
Velocity = Estimated Units ÷ Actual Units Consumed
Both sides are Atomic Units, and the estimate comes from the shared library rather than from the person doing the work.
Reading it
| Velocity | Reading |
|---|---|
| 1.0 | Delivering at the calibrated standard. |
| Above 1.0 | Faster than standard, usually through tooling, skill, or scope discipline. |
| Below 1.0 | Consuming more than standard: a skill gap, unclear scope, or a bad estimate. |
Why it matters now
The labor market prices people on hours and titles. Margin comes from units delivered. That mismatch is a live arbitrage, and it is wide right now.
In Moneyball terms, scouts were buying batting average when wins came from on-base percentage. Payroll is buying hours when margin comes from velocity.
How it rolls up
Individual velocity aggregates to team, and team to firm. Firm velocity feeds back into the Labor Effectiveness Ratio and makes that ratio diagnostic again, because you can finally separate "we have too many people" from "our people are not leveraged."
That separation is the point. Those two findings have opposite remedies, and guessing between them is how firms cut the wrong headcount.
Common mistake
Using velocity as an individual performance score in isolation. Velocity is heavily influenced by scope clarity and tooling access, and both of those are management's responsibility. A low-velocity team is usually a management finding before it is a people finding.
The first conversation is the CFO Huddle™. $850, 45 minutes, one finding, and what we'd do about it.
Knowing the number is the easy half. The Huddle is where a CFO looks at your actual financials and tells you what this one is saying about your business.
The Measure discipline of the MEASURE × HACK™ Method.
Published