August in review: the platform now checks its own numbers against what your plant actually did.
A quiet week, so this is a look back at the month instead. Read as a list, August was about thirty separate changes. Read as one thing, it was about a single idea, and it is the idea we would most like to highlight today.
Before August, we could tell you what an improvement program was worth. The question worth asking is what happens when someone checks. Most of what shipped in August exists so that you can.
Assessments now have a date on them, and two of them begin a trend.
Assessments are organised into named rounds, like "2026 Q2". A company's reports read one round at a time, so a maturity number finally answers "as of when". That sounds like bookkeeping, and it is the foundation for everything below: until a number has a date, nothing can be compared to it.
Close a second round and the maturity dashboard gains a trend. A headline figure for the organisation, then each department ordered by movement with the biggest decline first, and each department's practices underneath. Each column holds one round's answers, not everyone's latest, so someone who never retook does not read as movement. Respondent counts sit beside every score, since real cohorts are not matched and people leaving should not read as regression.
A scope selector drops from the whole company to a single site. That matters more here than anywhere else: a corporate average across five plants can sit almost still while the one plant that actually did the work moved half a point.
An improvement program now says what it will make you able to do, not only what it is worth.
Until August every figure on a program was money. The assessment that sized the opportunity was only ever an input, so a program could tell you its return but not what it would change about how the plant runs.
Each program now projects where the areas it addresses should sit on the same 1 to 5 scale your teams answered against: once every solution is live and adopted, and how much of that should have landed by now. Underneath sits the detail. Each area, where the assessment put it, where it should end up, and what share of that this program's solutions actually deliver. The rest needs work the program does not include, which is worth knowing before the work starts rather than a year in.
Two of the assumptions behind it cannot be derived from your data, so they are printed on the page rather than buried. A fully adopted program is assumed to reach world class rather than a flawless score, because no plant sustains a perfect five. And practice maturity is assumed to take around three years to fully land after a system goes live, because capability moves when people change how they work, which is slower than installing anything.
Then the program gets marked against that projection.
This is the part we care about most. A program that has been started, and whose plant has completed an assessment since, gains a section putting the two side by side: what it projected for the areas it targets, and what your own people then measured.
A projection nobody ever checks is marketing. One that gets checked every quarter is a model. The whole point is that it can come out badly.
Getting the comparison fair is most of the difficulty, and three things make it so. A program is graded on how much of it had actually gone live by the day that assessment closed, not on its finished promise, so a program five months into a two-year plan is measured against five months of work. Both sides name their round, so a projection is never compared against a blend of whoever happened to answer most recently. And alongside every result sits what the areas the program does not touch did over the same two assessments, because plants improve anyway: a program that moves its targets half a point in a company drifting up half a point everywhere has demonstrated nothing.
The first rounds we have to check this against have already told us something. The projection runs ahead of reality early and behind it later, which is what a straight line does against adoption that starts slowly and picks up. Two rounds is not enough to change the assumption on, so it is recorded and left alone rather than tuned until it flatters the model.
The figures start from your numbers.
You can enter your own current KPI levels on a baseline. Impact is then estimated against what you actually run today rather than against a generic move, the outputs lead with the measures you told us matter, and where a level is recorded the result reads as "from X to Y" rather than as a percentage floating free of anything.
And it all lives in one place.
ValueMaps is now part of the platform. Baselines, assumptions, scenarios, the audit walk, comparison, the investment plan and program creation all sit in the company workspace alongside the assessment that feeds them, under one navigation. Existing valuemaps.com links continue to work. The practical difference is that the chain from "our people rated this a 2.4" to "here is what closing it is worth and what we would fund first" is now one path rather than three products.
See it without signing up
The worked example is open to anyone: mfgvalueplatform.com/demo/exampleco. It is the real product on a fictional five-plant manufacturer, including the two in-progress programs and the assessment history they are marked against, so the predicted-versus-actual section is there to read rather than described. If you would rather start with a single number, the value calculator needs no account either.