The 90% Syndrome

A reporting gap can make a busy project look healthier than it is. Clear completion rules, evidence and consistent calculations help managers see what still needs attention.

“We’re 90% complete. The first three phases are finished.”

The project manager finishes her update. The director nods. “Good progress. Let’s bring the site engineer into the call and confirm the next phase.”

His answer changes the mood.

“The installation is finished, but inspections are still open. And the client hasn’t approved the handover.”

The project manager looks back at her slide. There is an uncomfortable pause.

“This is based on the latest report I received.”

It is. Several tasks are marked 100%. The work has been carried out, but checks and client acceptance are still outstanding. Those remaining steps have disappeared from the picture presented to management.

After the call, the manager and engineer look through the records together. Photos are in the group chat. Inspection requests are in emails. The spreadsheet records installation as finished. Each record describes part of the job, but none gives the complete answer the director needs.

The question is no longer simply whether the report is up to date. It is what the report means by “complete.”

Two familiar patterns behind the reporting gap

The 90% syndrome describes work that appears close to completion and then remains “almost finished” much longer than expected. The remaining effort may include corrections, testing, integration or approval. Sometimes the only thing moving forward is the date on the report.

Sometimes the only thing moving forward is the date on the report.

It is more than a problem with reporting. Research by David Ford and John Sterman examines how unexpected rework and responses to schedule pressure can prolong projects. Better visibility helps reveal the remaining work; the team still has to resolve it. [1]

The watermelon project describes a different problem: the report is green while the underlying situation is red. PMI uses the term for projects presented as healthy when they are actually in trouble. [2]

The two can occur together, but they are not interchangeable. One concerns getting stuck near the finish. The other concerns a reassuring status that hides problems. An approval that is planned and visible is ordinary unfinished work; hiding it behind “complete” creates the reporting gap.

One concerns getting stuck near the finish. The other concerns a reassuring status that hides problems.

What does 100 percent actually mean

An installation can be physically complete before it has passed inspection. It can pass inspection before the client has accepted it. These are different facts, and each matters to a different decision.

Physical progress answers how much physical work has been completed. Verification establishes whether the required checks passed. Acceptance records whether the person authorised to accept the deliverable has done so.

These are different facts, and each matters to a different decision.

A pending approval does not erase work already performed. It does mean that the deliverable or phase should remain open if that approval is required for completion.

Agree the criteria before work begins. A delivery may require receipt and quantity checks; an installation may require testing; a handover may require client acceptance. Put the approval at the level where it belongs. Every small task does not need a client signature.

A PMI conference paper by Marco Negri recommends objective completion criteria and explicitly planning production, review, correction and approval. It is a useful practical approach, rather than a claim that one percentage rule fits every project. [3]

Three practical ways to measure progress

Choose the measurement method to match the work, and label what it measures. The following calculations use illustrative values, not results from a customer implementation.

Count comparable units

For repeated work of similar size, count units that meet the chosen criteria. If 30 of 40 comparable installations have passed the agreed checks, checked-unit progress is:

Checked-unit progress = 30 / 40 = 75%

Specify whether you are counting installed, inspected or accepted units. Those counts may differ. The U.S. Department of Energy describes units-complete measurement for similar units with equal budget value; counting unrelated tasks as though each represents the same amount of work can mislead. [4]

Weight work packages of different sizes

Finishing nine small tasks does not necessarily mean 90% of the project is complete when the tenth task contains most of the work. Give each package a planned weight based on a consistent measure, such as estimated effort or budgeted value.

For this example, the team divides 100 points between the packages according to their estimated effort. Physical completion comes from measurable execution, such as quantities installed, rather than hours spent. Half the comparable electrical connections have been made, so that package is 50% physically complete.

For the separate accepted-progress measure, each package receives its full weight only after all its agreed acceptance requirements are satisfied. This is an all-or-nothing reporting choice for accepted scope, not a statement that unfinished packages contain no useful work.

The equipment installation still needs inspection and client acceptance. The electrical package still has physical work to finish. The other packages have satisfied their required acceptance criteria.

To calculate physical points, multiply each package’s weight by its physical completion. The electrical package contributes 20 × 50% = 10 points. Add the contributions, divide by total weight, and express the result as a percentage:

Physical progress = (10 + 15 + 25 + 10 + 30) / 100 = 90%

For accepted progress, add the weights of the accepted packages:

Accepted progress = (10 + 15 + 30) / 100 = 55%

The project is 90% physically complete and 55% accepted. Both figures are correct. Presenting either as an unexplained “project completion” number is what creates confusion.

The project is 90% physically complete and 55% accepted. Both figures are correct.

The 35-point difference is not entirely a missing-approval problem. It contains 25 points of physically finished installation awaiting acceptance, plus 10 points of execution inside the unfinished electrical package.

When the installation passes inspection and receives the required acceptance, accepted progress rises from 55% to 80%. Physical progress stays at 90%. When the remaining electrical work is performed, physical progress reaches 100%, but accepted progress remains 80% until that package’s required checks and acceptance are complete.

For large packages, use smaller measurable units or agreed acceptance milestones if an all-or-nothing accepted measure would hide useful intermediate progress.

Give credit for completed milestones

A longer deliverable can also be measured through agreed stages. Suppose its reporting rules allocate the following credit:

The 80/10/10 split is an example chosen for explanation, not an industry standard. Agree suitable stages and weights before reporting starts. DOE describes weighted milestones as one recognised measurement approach. [4]

Under these rules, a physically finished installation awaiting inspection earns 80% of its milestone credit. Label that figure as milestone credit, because it answers a different question from physical progress or final acceptance.

Under these rules, a physically finished installation awaiting inspection earns 80% of its milestone credit.

Calculate the package’s credit first, then apply its share of the project weight. A package worth 25 points with 80% credit contributes 20 points to that measure. Do not add those 20 points to its physical-progress contribution; they are different ways of describing the same work.

Keep the calculation consistent at every level

The reporting gap can reappear when task updates are combined into phases, sites and the overall project. A simple average gives every site the same influence, even when their workloads differ.

Consider a separate example with two sites:

Project progress = (80% × 100%) + (20% × 50%) = 90%

A simple average of 100% and 50% gives 75%. That result treats the sites as equally large, which they are not.

A simple average of 100% and 50% gives 75%. That result treats the sites as equally large, which they are not.

Use the same underlying weights at each level. A parent’s weight is the combined weight of its children. Whether sites sit inside phases or phases sit inside sites, each summary should remain traceable to the underlying work.

Count each task once in the overall calculation. A phase total already summarises its tasks; adding both would count the same work twice. Keep weights stable unless an approved scope change requires an update, and explain changes to the denominator.

GAO’s Schedule Assessment Guide supports reporting by people directly managing or performing the work and maintaining consistent information between detailed and summary schedules. A presentation should reflect the same underlying records. [5]

A percentage still needs a decision beside it

A project at 90% is not necessarily on schedule. The remaining 10% may include an approval or dependency that determines the finish date. GAO distinguishes elapsed time from work accomplished and emphasises realistic estimates of remaining work and duration. [5]

Keep required checks visible even when they carry little or no calculation weight. A rounded percentage must not hide an open acceptance condition.

Managers should be able to ask what remains, who owns the next action and which decision is blocking progress. Finance also needs the agreed billing conditions: physical progress, acceptance and permission to invoice are related, but they are not automatically the same.

How ApprovedFlow connects the work to the review

ApprovedFlow supports this approach by bringing task ownership, updates, evidence and approvals into the same working context. Phases and sites can be organised as sub-projects. Team members record their own progress, and those updates feed into the wider project view.

The task owner supplies the update and evidence. The responsible reviewer checks the work. Where client acceptance is required, that decision belongs with the deliverable or phase it approves. Managers and finance can follow the work and the decisions still outstanding.

The task owner supplies the update and evidence. The responsible reviewer checks the work.

The calculation methods above are choices a team can use to define its reporting. The operational principle stays the same: make the meaning of each status clear and keep it connected to current evidence.

Leaders have a part to play. When an engineer reports a problem, the response should help resolve it. Reporting early needs to lead to support and decisions; otherwise, people have little reason to keep sharing uncomfortable news.

Return to the meeting

Using the worked example, the next update becomes more useful:

“Physical progress is 90%. Accepted progress is 55%. The installation needs inspection and client acceptance. Electrical connections are halfway through. We need to confirm the inspection date and who will follow up the client’s decision.”

The director can now act on the remaining work. The manager can explain the figures. The engineer can see that the report reflects the site.

If your site engineer joined the next project review, would the dashboard and the site tell the same story?

The ApprovedFlow Project Operations Assessment helps you examine how progress is recorded, where decisions get delayed and which changes would improve the process.

Start the assessment

The opening scene is a representative workplace vignette. All calculation values are illustrative.

References

1. David N. Ford and John D. Sterman. Overcoming the 90% Syndrome: Iteration Management in Concurrent Development Projects. Author-hosted abstract.

2. Project Management Institute. Promise: Make All Work and Workflow Visible. Disciplined Agile guidance.

3. Marco Negri. Managing outsourced projects: the good, the bad, and the savvy. PMI Global Congress, 2012; see the discussion of the review cycle and objective completion criteria.

4. U.S. Department of Energy. Earned Value Management Tutorial, Module 5: EVMS Concepts and Methods. See fixed-formula, milestone-weighting and units-complete methods.

5. U.S. Government Accountability Office. Schedule Assessment Guide: Best Practices for Project Schedules. GAO-16-89G, December 2015; Best Practices 5 and 9.