World 1 of Projects, level 4: what holds the platforms up
Money spent isn't work done. How to measure a project's real progress, read the S-curve, deal with variance and write the right report for whoever decides.
Part 4 of 5 of the series World 1 of Projects.

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).
World 1 of Projects series — level 4 of 5: World 1-1 · World 1-2 · World 1-3 · World 1-4 · World 1-5
Some Super Mario levels have balance lifts: two platforms hanging from the same rope. Step on one and it starts to drop while the other rises. Leave your weight on the same side for too long and the whole thing gives way. Whoever crosses them doesn’t trust them to hold: they watch them the whole time and get off before they reach the end.
In a project, control is that watching. Measuring what actually happened, comparing it with the snapshot from World 1-3 and acting on the difference before the platform hits the bottom.
You can’t manage what you don’t measure. You can’t measure what you don’t define. And you can’t define what you don’t understand. The previous levels dealt with understanding and defining, and this one deals with measuring.
Physical or financial progress: which one counts?
Both count, and each tells you something different.
Financial progress tells you how much money has gone out, while physical progress tells you how much work is finished. A project can have spent 70% of its budget and have 40% of the work done. And the financial report, on its own, will say everything is “on track”.
Money spent isn’t work done. That’s why control measures physical progress in the units of the WBS from World 1-2: pieces assembled, deliverables accepted, modules tested. And only then crosses it with what it cost.
What is the S-curve, and what does it show?
When you accumulate a project’s progress over time, the shape almost always comes out as an S: a slow start (mobilisation, preparation), a fast middle (everyone producing) and an end that slows down (finishing touches, tests, snagging) [1].
The planned S-curve is the baseline drawn out. The actual S-curve gets drawn on top of it, week after week. What matters is the distance between the two, and whether that distance is growing or shrinking.
An actual curve that pulls away early, in the slow part, is the cheapest warning a project will ever get. Whoever waits for the middle of the curve to react is already paying the price of the fast part.
What is variance, and what do you do with it?
Variance is the difference between what the baseline said and what happened. In itself, it’s just information.
With a variance in hand, there are only three honest responses:
- Explain: why it happened, and whether it will happen again.
- Act: what changes from tomorrow so that the actual curve gets back against the planned one.
- Change the agreement: when reality shows the plan was impossible, and the change is approved by whoever has the authority (see World 1-3).
The dishonest response is the fourth, and it’s the most common: hiding the variance until it’s too big to hide.
And there’s a mistake that comes before all of these: deciding on what things look like, ignoring what control shows.
I worked on a project where the client had a person who walked around the project site making his own notes. At one point, he noted that a set of works was finished. I don’t blame him: from the outside, it really did look that way; the project’s control, however, had the reality. It wasn’t finished. Several small components were still missing, and they still required us to use that space.
On the strength of that note, he set things in motion for another company, which in the sequence would come after us, to start its work. Chaos broke out. We needed to finish; they needed to start. And nobody was working.
Guesswork has no place in a project. Only good control reports what really happened.
A report for whoever decides, or for whoever does the work?
They’re two reports, and mixing them spoils both.
A report for whoever decides usually says when and how much: when the project finishes, against the baseline, and how much it will cost. And it ends with the decision it’s asking of the reader.
A report for whoever does the work usually says what and how: which piece, which front, what’s missing, what has to be ready tomorrow and in what way.
The same data serves both, each in its own form. Quality information depends on who’s consuming it.
Quick questions
What’s the difference between physical and financial progress? Financial progress measures the money that has gone out; physical progress, the work that’s finished. Only physical progress tells you whether the project will reach the end.
What is an S-curve in project management? Progress accumulated over time. It starts slowly, speeds up in the middle and slows down at the end, and what you track is the gap between the planned curve and the actual one.
What do you do with project variance? Explain it, act on it or formally change the agreement. Hiding it is never an option, and it’s the most common one.
What should a management report contain? When and how much: the date and the cost against the baseline, and the decision being asked of the reader. The detail of what and how belongs in the report for the people doing the work.
References
- Murmis, G. M. (1997). “S” curves for monitoring project progress. PMI Learning Library. https://www.pmi.org/learning/library/s-curves-monitoring-project-progress-5386 — accessed 2026-09-25.