Project Performance: Data, Information and Judgement

Most project managers have sat through a review in which every line of the status report was green and still left the room uneasy. The milestones had been met, spend was close to plan and the risk register had barely changed in a month. Yet something about the project did not add up. That unease is rarely intuition in any mysterious sense. More often it is an experienced project manager noticing signals the report was never designed to carry.

This is why the question of what to monitor for overall project performance is harder than it first appears. The natural answer is a list of measures: schedule variance, cost performance, open risks, approved changes. Those all matter, but overall performance is not simply their sum. A project can sit within tolerance on every individual measure and still be drifting away from the outcome it exists to deliver. Understanding performance means watching a small number of things across both delivery and value, reading them together, and deciding what they mean.

Why overall performance is more than progress against plan

Progress tells you where the project stands relative to its plan. Overall performance asks a wider question: is this project likely to achieve what it was authorised to achieve, at an acceptable cost and level of risk, in a form its stakeholders will actually accept? The two can diverge. A project can hit its baseline and still fail to create the value that justified it. A project running behind its original dates can be in good health if the delay reflects an informed decision to protect the outcome. The 2026 PMP® Examination Content Outline draws on PMI research that treats schedule, budget and scope as the starting point for judging success rather than the whole of it, and adds stakeholder value and intended outcomes to the picture.

The Eighth Edition of the PMBOK® Guide makes a structural point here that is easy to overlook. Scope, schedule and finance each have their own monitoring processes within their performance domains. Monitor and Control Project Performance, however, sits in Section 2.1.6, within the Governance Performance Domain. A useful way to read that placement is that project-level performance monitoring exists to support decisions about direction, authority and escalation. The report matters, but it is the vehicle that carries the resulting judgement to the people who need it, not the purpose of the exercise.

Four questions that give you the overall picture

A practical way to structure performance monitoring is to ask four questions at every review point, whatever the size of the project or the approach it uses. They are a working device of our own rather than a PMI framework, but they reflect the concerns that sit behind project-level control.

The first is where are we against what we committed to? On a predictive project this means milestones, the schedule and cost baselines, and earned value measures such as the cost and schedule performance indices where the organisation uses them. On adaptive work it means increments completed and accepted, and progress towards a release or product goal, often shown on a burn-up chart. This is the question most reports answer well, and it is also the most backward-looking of the four.

The second is where are we heading? Position is a snapshot; trajectory is what governance needs. Forecast completion dates and costs belong here. So do the rate at which float or contingency is being consumed and whether overall risk exposure is rising or falling. A small variance that grows every reporting period usually deserves more attention than a larger one that has held steady for months.

The third is what is producing that result? Schedule and cost are lagging signals. The conditions that generate them tend to move first: team capacity and turnover, the reliability of dependencies and suppliers, the volume of rework, how long decisions wait for an answer, and whether key stakeholders are still engaged. When a project goes wrong quietly, this is usually where the early evidence was.

The fourth is is the outcome still achievable, and still wanted? This means checking whether the assumptions in the business case still hold and whether the benefits remain realistic. It also means checking whether sponsors and end users still regard the work as worth completing. External change belongs here too, whether that is new regulation, a shift in organisational priorities or a competitor moving first.

A project manager who can answer all four with evidence understands the project's performance. One who can answer only the first is reporting progress. The same logic keeps monitoring proportionate, because every measure should earn its place by informing a decision someone might need to make. If nobody would act differently when a figure changed, it is decoration rather than control.

Turning data into information, and information into judgement

Monitoring starts with data: hours booked, tickets closed, invoices paid, defects raised, deliverables signed off. Data becomes information only when it is interpreted in context and compared with something meaningful, such as a baseline, a forecast, a tolerance or an objective. Judgement is the step after that, and it is the one most often skipped. It means deciding what the information actually indicates, whether action is needed, and whose action it should be.

A cost performance index of 0.92 is information. It tells you that the value of the work completed is lower than the amount spent achieving it. It does not tell you what caused the gap. The cause could be a one-off procurement cost, a systematic estimating error or a productivity problem in one workstream, and each of those calls for a different response. Treating the index as a diagnosis rather than a prompt to investigate is how projects end up with confident corrective action aimed at the wrong problem.

A few habits make that judgement more reliable. Look hardest when signals disagree, because disagreement is often where the real story sits. A schedule holding steady while quality slips can mean the dates are being protected by pushing defects downstream. Prefer trends to snapshots, and leading indicators to lagging ones. Above all, be clear about tolerances before anything goes wrong. Agreed thresholds decide what the project manager handles directly and what needs to reach the sponsor or a steering group. The Business Environment domain of the current exam outline explicitly includes setting out governance escalation paths and thresholds. Performance inside tolerance is normally the project manager's to manage. A credible forecast that tolerance will be breached is information governance needs early, while options still exist.

When the report is green and the trajectory is not

The following situation is fictional, but the pattern will be familiar. A hospital trust is refurbishing its day-surgery unit, which is due to reopen to patients in eight weeks. Every milestone to date has been met, spend is slightly under plan, and the risk register has not materially changed for a month. The monthly report is green throughout.

Three things are not on that report. The snag list from the commissioning walk-rounds has grown for three consecutive weeks, with items being raised faster than they are closed. The supplier of the recovery-bay monitoring equipment has moved its delivery date twice, each time within the remaining float. And the senior theatre nurse whose sign-off is needed for clinical readiness has missed the last two walk-rounds. The snag list is the kind of measure that rarely appears on a status report, and yet in the final weeks of a fit-out it often says more about the opening date than the milestone chart does.

Each of these sits within tolerance on its own. Together they describe a project whose position is green and whose trajectory is not. The reopening date depends on snag closure, equipment arrival and clinical sign-off all coming together in the final fortnight, and all three are moving the wrong way.

Two responses would be premature. One is to tell the sponsor the project is in trouble before understanding why these signals are moving. The other is to keep reporting green because no single measure has breached a threshold. The competent response sits between them. The project manager finds out why snags are accumulating, which may turn out to be late equipment specifications forcing rework in the bays. They speak to the theatre nurse to understand whether the missed walk-rounds reflect rota pressure or a loss of confidence in the unit. They re-forecast the reopening date using the actual closure rate rather than the planned one. The next report then shows current status as green against baseline and the reopening forecast as amber. It also sets out the decision the sponsor may need to take within three weeks, such as reopening in phases. Governance receives the problem while there is still time to choose a response.

Reading performance across predictive, adaptive and hybrid work

The four questions apply whatever the development approach, but the evidence changes. On predictive work, baselines and earned value give a strong, structured picture of position and trajectory. Practitioners from governance-heavy environments are often very good at reading them. The discipline to add is the third and fourth questions, because a baseline cannot tell you whether the conditions producing the work are deteriorating or whether the outcome is still wanted.

On adaptive work, performance is visible in working product: what has been delivered, whether stakeholders accepted it at review, and whether it is being used. Throughput and velocity help with forecasting, but they are planning aids rather than targets, and a team pressed to increase velocity will usually find a way to do so on paper. The questions about value are often easier to answer here, because frequent delivery produces frequent evidence.

Hybrid projects carry a particular trap. The project reports milestone status for one part of the work and backlog progress for another, then leaves the steering group to work out how the two relate. The project manager's job is to translate both into a single view of whether the intended outcome will be delivered when it is needed.

For a PMP candidate, this connects directly to the Process domain of the 2026 outline, which accounts for 41 per cent of exam items. That domain includes a task on evaluating project status, covering the development of metrics, the assessment of current progress and the communication of status. The outline also states that predictive, adaptive and hybrid approaches appear across all three domains rather than being confined to one. A performance situation may therefore involve milestone data, a burn-up chart or both. The useful preparation habit is to treat a figure in a scenario as a prompt to analyse rather than a trigger for action: what does this signal tell you, what does it leave out, and whose decision does it affect? That habit carries straight back into the workplace. It is one we develop deliberately in PMP® Exam Preparation, where performance situations are worked through alongside governance, risk and stakeholder judgement rather than as isolated calculations.

Whether or not an exam is on the horizon, the practical value is the same. A project manager who watches position, trajectory, conditions and value, and reads them together, sees trouble while it can still be managed. The status report still matters, because governance depends on it. It is where the thinking ends up, not a substitute for doing it.

Andre Malowney

Interested in going further?

Reading performance well depends less on knowing the measures than on deciding what they mean and who needs to know. Structured PMP preparation gives you repeated practice at that judgement across predictive, adaptive and hybrid situations, where the right response depends on context rather than on a single figure.

For the full picture of how performance monitoring connects governance to the other six performance domains, the PMBOK® Guide Eighth Edition is the reference to keep on the desk.

Ad · Amazon affiliate link.

References

A090: Project Governance Explained: Who Decides What, and Why
A091: Project Governance vs Organisational Governance: What’s the Difference?
A092: How Projects Create Value Through Governance
A093: Choosing a Project Governance Model
A094: Governance Metrics That Actually Tell You Something

PMP and PMBOK are registered marks of the Project Management Institute, Inc.