Project Health Measurement: Beyond Red, Amber, and Green (part 1)
This article is by our long-time collaborator and musician. Steve Lauck. Over the years, I have collaborated with so many people to produce things. I can genuinely say that I have enjoyed these exchanges. However, this work with Steve is one of my favorites. For a number of reasons. We have written magazine articles, books, and blog posts together, but we have also had interesting chats on project management and, perhaps more importantly, music. He has interesting perspectives that don’t look like my own – that makes the perspective interesting. If you are looking for a talented project manager or business coach for your team or work efforts, you should connect with him on LinkedIn and start a conversation.
This is the first of a four-part series from this exceptional person.
This article is the first of a series on report of Project Health.
The Problem with Subjective Status Ratings
A project status color is often an opinion presented as a measurement. Two project managers can review the same schedule variance, budget position, and open risks yet assign different ratings.
One may report Green because the project is still forecast to meet its completion date. Another may report Amber because critical assumptions remain unverified. Both judgments may be reasonable, but leadership needs a method that is more consistent than individual interpretation.
A Better Approach: Measure Project Health
The solution is not simply a better color-coding scheme. It is a project health measurement system.
Each rating should be:
- Measurable and repeatable
- Supported by evidence
- Forward-looking
- Tied to the project’s intended outcome
Separate the dimensions of project health
Green, Amber, and Red are useful communication tools, but they don’t tell us what is being measured. Schedule, cost, quality, risk, and outcome are different dimensions of performance. Combining them too early can hide important information.
Define the colors using explicit decision rules
Define each color based on whether the project can still achieve its approved commitments, not on whether the team feels comfortable with its progress.
Here is a starting model. The numerical thresholds are illustrative, not universal standards; calibrate them to the project’s risk tolerance, complexity, and business consequences.
| Rating | Quantitative and qualitative criteria | Required response |
| Green | Forecast remains within approved tolerances. Critical milestones are achievable. No unresolved condition threatens the intended outcome. | Continue execution and monitor. |
| Amber | A measurable variance or credible threat exists. The approved outcome remains achievable, but corrective action, mitigation, or management decisions are needed. | Name the threat, assign an owner, and set a deadline and recovery test. |
| Red | A commitment has been or is forecast to be breached beyond tolerance, a critical requirement is unlikely to be met, or no credible recovery path exists under the current plan. | Escalate, present options, and obtain a decision on recovery, scope, funding, timing, or continuation. |
This aligns with the broader principle that RAG criteria should be established in advance and that status should drive an appropriate management response.
One important distinction: Amber does not simply mean “there is a problem.” Every project has problems. Amber means a defined threshold has been crossed or a credible threat requires intervention. Red means the consequences are beyond routine management tolerance or a critical condition has failed.
Quantify each dimension separately
I recommend using measurable indicators within each dimension, with project-specific thresholds agreed upon during planning. Here is an example of how that could work.
| Dimension | Green | Amber | Red |
| Schedule | Forecast finish within approved tolerance; critical milestones achievable | Milestone at risk; recovery actions required | Forecast milestone breach beyond tolerance or no credible recovery |
| Cost | Estimate at completion within budget tolerance | Forecast overrun is recoverable within agreed authority | Forecast exceeds authorized funding or recovery requires executive approval |
| Quality | Acceptance criteria met; no critical defects | Significant defects or verification gaps with a credible closure plan | Critical acceptance criterion failed or deliverable is not fit for intended use |
| Risk | No unresolved exposure exceeds the project’s accepted risk limits | Exposure exceeds a trigger but can be mitigated within the available time and authority | Risk has materialized or exposure exceeds accepted limits without a credible response |
| Scope | Requirements baselined and controlled | Unresolved changes or requirements threaten commitments | Essential scope cannot be delivered, or requirements cannot be satisfied under the current authorization |
| Resources and dependencies | Required resources and inputs available when needed | A critical dependency is threatened, with a plausible workaround | A critical dependency is unavailable and blocks delivery |
| Outcome | Evidence supports the intended business result | Outcome depends on unresolved assumptions or a decision | Intended outcome is no longer achievable or its fundamental justification has failed |
Calibrate Thresholds to Consequence
Green and Amber should not be separated by a universal threshold such as a five-percent schedule variance. Context determines significance: five percent of a two-week task is not equivalent to five percent of a regulatory deadline or a production-line installation window.
The same principle applies to project events and requirements:
- Capital equipment: Missing a supplier’s factory acceptance test may be far more consequential than an equivalent delay in a noncritical document.
- Automotive programs: Failure of a safety-critical requirement must trigger appropriate escalation; strong performance elsewhere cannot offset it.
Thresholds should therefore reflect the consequence of the variance, not merely its numerical size.
In the next article, we will establish a scoring method behind the colors.
For more information, contact us:
The Value Transformation LLC store.
Follow us on social media at:
Amazon Author Central https://www.amazon.com/-/e/B002A56N5E
Follow us on LinkedIn: https://www.linkedin.com/in/jonmquigley/
https://www.linkedin.com/company/value-transformation-llc
Follow us on Google Scholar: https://scholar.google.com/citations?user=dAApL1kAAAAJ


