Two scores — before & during the project. An early-warning and confidence-building system for owners, investors, lenders, and project teams.
Owners decide to carry on without letting the project mature — driven by optimism bias, speed pressure, or skill mismatch. The development reads as "good enough." The numbers say otherwise. PMI catches this.
The organisation built to run the plant cannot deliver the project. The four pillars do not line up. Execution drifts cycle by cycle, and nobody calls it. PHI catches this.
"Learning increases with time — but the ability to economically respond to that learning decreases with time."
That is the central idea behind the MacLeamy Curve.
Thereafter, roughly 9 out of 10 projects run over budget or over schedule — for controllable reasons. The cause is not only poor implementation — it is often poor development.
Project-failure research names the same causes across thousands of jobs. The dark bars are maturity gaps that exist before commitment — PMI catches these. The light bars are execution drift that forms while the project is being delivered — PHI catches these.
If Project Development is poor, Project Implementation cannot cover. But even if Project Development is good, Project Implementation can still disturb the outcome.
16 named causes. Every one is either a development gap (PMI) or an implementation drift (PHI).
PMI measures the maturity of Strategy, Technology, Project Estimate, and Finance — to tell you, before commit, whether the project is ready to start.
PHI builds the context and measures the congruence between Governance, Skills, Workflow, and Culture — to predict whether the project is actually healthy.
Without these two indicators, by the time the numbers tell you the project went bad, it is already too late — the conditions had been incubating for months.
A maturity score that tells you the residual risk you still carry. It is checked at every significant event in the project’s development cycle:
A health score that names what is weak and who must fix it. PHI runs as a third eye on the project. It builds context from the foundational documents, and then continuously reads:
From all of this, PHI forms a view on whether the underlying systems and motivations are aligning with the project’s objectives — or quietly drifting away from them.
Two tools, used in sequence. Not just signals — direction.
PMI does not only measure the residual uncertainty — it also points to the sources of it. That gives the user a choice: accept the risk, or mitigate it.
PHI does not only track present progress — it also reads the softer signals of team alignment and motivation. That is how it surfaces the hidden, incubating incongruences that quietly move outcomes. The user gets a chance to act before they harden.
With both, the user narrows the variability of the project's outcome — instead of waiting to discover it.
PMI is built on
PHI is built on

Run your project through PMI and PHI in a working session — then keep scoring it as you build.