68% complete. On track. Moving well.
That was the slide. That was what the director saw. Three weeks later, the programme missed SOP by four weeks.
The 68% task completion figure was accurate. Every number on that slide was correct. And it was completely useless as a measure of whether the programme was going to make its date.
Here is why — and what the number that actually matters looks like instead.
Task Count Is a Lie You Tell Yourself
Counting completed tasks feels like measuring progress. It is not. It is measuring activity.
A programme with 100 tasks where 68 are complete looks healthy on a standard dashboard. But if the 32 remaining tasks include the only casting supplier in your supply chain, the PPAP submission, the customer trial run, and the gauge approval — the programme is not 68% healthy. It is in serious trouble.
Task count treats every task as equal. A quality document review completed on time carries the same weight as a sub-supplier forging delivery completed on time. They are not equal. Not even close.
The forging delivery, if it slips, cascades. The document review, if it slips, creates paperwork. A measurement system that cannot tell the difference between these two things is not measuring programme health. It is measuring programme activity.
Activity is what you have done. Velocity is whether you are going to make it. A car that has covered 70% of the distance to its destination might be fine. A car travelling at 41% of the speed it needs to arrive on time is going to be late — whether the driver knows it or not.
What OPV Actually Measures
OPV — Overall Project Velocity — is not a count. It is a ratio.
It measures the proportion of your planned delivery capability that your programme is actually achieving, weighted by the consequence of each task.
Every active task in the programme is measured. Each task is weighted by how long it was planned to take and what type of control you have over it — internal, supplier, or sub-supplier. The system measures whether each task is tracking to its planned date or drifting away from it. And it produces a single number that tells you, without ambiguity, how your programme is actually performing against the plan.
An OPV of 0.9 means the programme is executing at ninety percent of planned velocity. Healthy. An OPV of 0.6 means the programme is executing at sixty percent. That is not a programme that is sixty percent complete. That is a programme consuming time at a rate that makes its planned delivery date unreachable — unless something changes.
Why the Number Cannot Be Gamed
The reason OPV matters is not just what it measures. It is how it is calculated.
OPV is not declared. It is computed.
No programme manager chooses their OPV the way they choose a RAG colour. There is no amber option to hover over before deciding to stay on green. The system looks at every active task, measures whether it is tracking to its planned date or drifting, weights each task by its consequence type, and produces a number.
The number reflects reality. Not the PM's management of reality.
This changes the review meeting in a way that RAG status never could. When the OPV is 0.62, there is no way to explain it away with a confident tone and a revised commitment date. The conversation has to be about what is actually happening — and what is going to change.
When the number is calculated, the conversation shifts from "how do we look?" to "what do we need to fix?" That is the only conversation that matters in a manufacturing review room.
The 70/40 Gap
Here is the scenario that proves why task count misleads and OPV does not.
The programme has burned through seventy percent of its tasks and forty-one percent of its planned execution capability. It is not ahead. It is behind. The 32 remaining tasks include the five highest-consequence items in the programme — all supplier or sub-supplier controlled, all drifting, two of them slipping for the third time.
Task count said green. OPV said crisis.
The programme manager who sees only the task count walks into the customer meeting confident. The programme manager who sees the OPV makes three calls that afternoon.
What a Healthy OPV Looks Like in Practice
OPV is not meant to be perfect throughout a programme. Variance is normal. Manufacturing programmes encounter real-world friction — supplier delays, engineering changes, capacity constraints — that no planning system can predict.
A healthy programme does not have an OPV of 1.0 from start to finish. A healthy programme has an OPV that the team is watching, that never drops below 0.75 without a response, and that the PM can explain with specific corrective actions when it does.
The number is not the goal. The behaviour the number drives is the goal.
When a programme team watches OPV weekly — when it is the first number on the review agenda rather than the last — the conversation changes. Drift is caught in the second week, not the sixth. Recovery actions are taken when the three-week window is still open, not after it has closed.
In Project Perfect, an OPV below 0.75 triggers an automatic risk flag. Not because 0.74 is catastrophic — but because the pattern that produces 0.74 today produces 0.58 next week if nothing changes. The flag is not an alarm. It is the three-week window opening. The PM's job is to act while it is still open.
OPV and the Three-Week Window
OPV and the three-week window are the same idea expressed differently.
The three-week window is the recovery time that exists between when the signal becomes readable and when the damage becomes irreversible. OPV is the metric that tells you the signal is readable.
A programme with a declining OPV — dropping week over week, even slightly — is a programme where the window is opening. It is the system saying: there is still time. The gap between plan and reality is visible. Recovery is still possible.
A programme manager who sees OPV declining and acts has three weeks of options. One who waits for the task count to look bad has three days of damage control.
Task count tells you what you have done. OPV tells you whether you are going to make it. In manufacturing programme management, only one of those questions matters.
Your Projects Don't Have to Fail
This article is based on Book 2 of The Execution Series — five books on manufacturing programme management written from 25 years of experience. OPV, LFV, and the Risk Number are covered in full across the series. All five books are free.
Request the Free Series →OPV — calculated automatically. Every week. Without asking anyone.
Project Perfect computes Overall Project Velocity from live task execution data. No self-declaration. No colour choices. Just the number — so your team always knows where the programme actually stands, and always has time to act.