TrustGrowth · PHI — Is your project really healthy?

The most expensive trap

A green dashboard can hide a sick project.

Cost looks fineso the dashboard is green

→

Because money is sittingspend is delayed, not saved

→

Because milestones slipsomething underneath has come loose

PHI catches this cycles before your dashboard does.

The five pillars

One score. Built from five.

The present picture

Performance & Forecast

Context — where you are, where you're heading

Cost and schedule against plan, and a Monte Carlo forecast of where the project is actually going. It anchors the four pillars below in the hard numbers of this cycle.

The formal organisation

Governance & Delegation

Decision quality & speed

The people

Skills & Experience

Capability

The work

Workflow & Interfaces

Efficiency

The informal organisation

Culture & Behaviour

Cohesion

What PHI does

It names what's weak — and who must fix it.

01Continuous — refreshed every reporting cycle.

02Names the weak pillar.

03Names who must act, and how — accountability, not just a number.

04Reads your existing reports — no new system, no site visit.

How it works

Your project already speaks. The engine listens.

Set the baseline. Open one mailbox. The engine reads congruence between pillars — and the drift from where you said you'd be.

01

Set up the project. Hand over the baseline.

You provide the foundational documents — approved scope, cost baseline, schedule, risk register, project organisation, RACI, stage-gate plan, the cost & schedule Monte Carlo model. This becomes the should-be against which everything that follows is read.

02

One dedicated project mailbox.

A single email ID for the project — every stakeholder marks it on every exchange. Owner directives, project-manager updates, vendor RFIs, MOMs, escalations, change orders, steering notes. No new tool. No site visits. No extra meetings. Just one address that quietly receives the project's nervous system.

03

The engine reads congruence between pillars.

The engine watches whether the four pillars — Governance, Skills, Workflow, Culture — are pulling in the same direction. Is the Owner overruling the Project Head? Are decisions stuck in committee? Are two teams asking the same vendor the same question? When one pillar drifts out of congruence with the others, the engine catches it cycles before the dashboard does.

04

Drift from baseline is measured.

Performance and forecast are reread against the foundational documents. CPI, SPI, milestone slippage, Monte Carlo cone of where the project is actually heading. The drift number is the honest gap between what the baseline promised and where the project is actually pointing today.

05

A continuous PHI score — every cycle.

Every cycle, the engine produces a single number with the weakest pillar named, the actor identified, and the action to lift it. The reports your team is already writing become the raw material — and you get an independent read on what they actually mean.

What it's based on

The global project standard — and proven organisational science.

PMBOKThe global project-management standard

Nadler–TushmanThe Congruence Model — when the parts fit, the project performs

A project performs when four things fit together. When one is off, the whole shape breaks — and the project drifts, however strong the others are.

Who uses it

The same score, read four ways.

Owners & Boards

Carry, contain, or escalate.

Investors & Lenders

An independent read on the reports you already receive.

Project Heads

Where it's slipping, and who must act.

Project Teams

Today's queries that decide next month's score.

See what your dashboard isn't telling you.

Run your live project through PHI in a working session — off the reports you already produce.

Talk to Harshit →