Project Status Is Green. So Why Am I Losing Sleep?
Updated: Oct 1
A Program Director's Field Guide to Reading Past the Dashboard
A five-lens model for giving the CIO an honest view of delivery health before a weak signal becomes an executive surprise.
ARUNAVA CHAKRAVARTY
Independent Consultant and Strategic Advisor | Program and Delivery Advisory | PMO and COE Design | Program Recovery
Prefer to watch instead?
Project Status Is Green. So Why Am I Losing Sleep?
The executive view
THE PROBLEM Five status tiles can each be accurate and green while the conditions the program needs to deliver are quietly weakening underneath them. | THE PROGRAM VALUE A five-lens model separates current position, forecast and confidence, surfacing governance, technical, commercial, people and benefits health a RAG colour can't answer alone. | THE DECISION Move to an integrated scorecard. Report status and forecast separately, reward evidence-based amber, and put one question on the agenda: will this still deliver? |
My guiding principle
A green dashboard is not a verdict. It tells us that a defined measure is within tolerance at a single moment. A Program Director's responsibility is not to defend the colour on the page, but to give the CIO early visibility of the conditions that could change the outcome while leadership still has choices.
1 Why green dashboards mislead in complex programs
Fifteen minutes before a steering committee meeting, every tile read green: schedule, cost, scope, quality, vendor SLAs. Contingency was down to single digits with two quarters of runway left. Three cross-workstream decisions had sat with no owner for a month. A workaround that protected last quarter's milestone had quietly become permanent. None of that showed up as a colour on the page — it showed up in what the colours didn't ask about.
The paradox isn't a lie — that's what makes it dangerous
No single report in that meeting was false. Schedule really was on track. Cost really was within budget. Every function reported accurately inside its own boundary. The failure lived in the aggregation — nobody's job was to ask whether five accurate, green, well-intentioned reports still added up to a program that would deliver its outcome.
Outputs are not outcomes
The definition of project success has itself moved. The Project Management Institute now frames success around value delivered relative to effort and expense, explicitly moving the goalposts beyond scope, schedule and cost compliance alone (PMI, Project Success Definition and Key Drivers). An on-time platform that nobody adopts, cannot be operated sustainably, or fails to release the benefit it was funded for, has not automatically succeeded — no matter how green its dashboard looked on the way there.
What a status report should actually reveal
Trajectory, not just position. Whether the forecast outcome and confidence behind today's number are improving or eroding.
Decision health. Whether material choices are being made while they are still cheap, not after the window has closed.
Technical sustainability. Whether workarounds and debt are visible, owned and reflected in the forecast rather than inherited silently.
Commercial exposure. The credible cost to complete, not just the budget consumed so far.
Organizational readiness. Evidence of behaviour — adoption, capacity, sponsorship — not attendance and activity.
Benefit realism. Whether the original outcome is still achievable and still worth the remaining spend.
2 Run governance as a two-sided compact
Reading past green works only when authority and accountability are explicit on both sides. Five connected lenses tell me whether schedule, cost and quality controls still add up to a credible outcome — none of the five replaces those controls; together they explain what a single colour can't.
Lens | What it must reveal | Leading signals for the CIO |
1. Governance and delivery | Control of scope, plan, dependencies, decisions and forecast. | Decision age; critical-path float; contingency burn; dependency closure; forecast confidence. |
2. Technology and operational readiness | Integrity, integration, security, resilience and operability. | Technical debt; exception ageing; end-to-end test evidence; resilience gaps; support readiness. |
3. Financial and commercial health | True cost to complete and protection of commercial value. | Estimate at completion; claims; change exposure; invoice disputes; service-credit recovery. |
4. People and organizational readiness | Capacity, sponsorship, trust, adoption and change saturation. | Critical-role attrition; adoption evidence; sponsor actions; change load; escalation quality. |
5. Strategic value and benefits | Continuing relevance and realizability of the business outcome. | Benefit forecast; assumption changes; legacy retirement; value-owner commitment; time to value. |
The accountability rule
I don't ask a steering committee to look past green for free — the compact runs both ways. Here is the version I put in writing with every CIO I work with.
What I commit to as Program Director
1. Separate current status from forecast outcome, and state my confidence in both.
2. Escalate material uncertainty early, with options, consequences and a recommended decision — not just a warning.
3. Report cross-workstream dependencies and enterprise trade-offs, not only tower-level progress.
4. Show plainly where a green result is being sustained by contingency consumption, technical debt or unsustainable effort.
5. Maintain one integrated view of delivery, technology, commercial exposure, readiness and benefits.
6. Challenge whether the business case remains valid, and whether benefit owners are actually positioned to deliver it.
What I need from the CIO and steering committee
1. Clear decision rights, with named executives who can resolve issues across functions.
2. Fast decisions when delay will remove viable options.
3. Tolerance for evidence-based amber and red reporting, without penalizing the messenger.
4. Protection of critical resources and alignment across business, technology, finance, procurement and operations.
5. Explicit acceptance of residual risk at major investment and go-live gates.
6. Ownership of value realization after technical delivery is complete.
The steering committee scorecard
The purpose of the five lenses is not a bigger dashboard; it is a smaller set of better signals. The governance and delivery lens supplies the first five scorecard dimensions: current performance, forecast outcome, confidence, exposure and decision health. The other four lenses appear directly as technical, commercial, organizational and benefits health. Every line carries a position, trend, evidence, owner and any executive action required.
Dimension | Core executive question | Minimum evidence |
Current performance | Where are we now? | Actual versus approved baseline and tolerance. |
Forecast outcome | Where are we likely to finish? | Latest integrated forecast and assumptions. |
Confidence | How reliable is that forecast? | Range, scenario or confidence rating with rationale. |
Exposure | What can materially change the outcome? | Top threats and opportunities, triggers and response capacity. |
Decision health | Are we deciding while choices remain useful? | Decision log, last responsible dates and impact of delay. |
Technical health | Are we creating a sustainable service? | Debt, exceptions, integration and non-functional evidence. |
Commercial health | Are cost and contracts aligned with delivery? | Estimate at completion, claims, leakage and obligations. |
Organizational readiness | Can the enterprise absorb and adopt the change? | Behavioural readiness, capacity, sponsorship and adoption. |
Benefits health | Will the investment still create sufficient value? | Current benefit forecast, owners and refreshed assumptions. |
The nine dimensions belong on one page, but they are not interchangeable. Current performance records where the program is now; forecast outcome estimates where it will finish; confidence explains how much trust to place in that estimate. The remaining dimensions show what could change it and whether the intended value remains achievable.
CURRENT POSITION Where we are Actual versus baseline, right now — a fact, not a prediction. | FORECAST OUTCOME Where we'll land The credible estimate at completion given everything known today. | CONFIDENCE LEVEL How sure we are The range or rationale behind the forecast — the number that keeps the other two honest. |
3 What can defeat a green status
A green tile is a true statement about a narrow, well-defined measure — and a poor proxy for the larger question a CIO actually needs answered. The table below is what I now put in front of every steering committee: what a green tile usually means, what it can be quietly hiding, and the question that tells the difference.
Reported green | Potential hidden deterioration | Executive test |
Schedule | Float exhausted, testing compressed, dependencies unresolved. | What is the probability of the final outcome, not just the next milestone? |
Cost | Claims, unapproved changes, delayed invoices, contingency burn. | What is the credible estimate at completion and the remaining exposure? |
Quality | Weak coverage, accepted defects, workarounds, poor operability. | Is the service fit for purpose under realistic operating conditions? |
Risk | Documented risks without funded responses or useful triggers. | Do we still have time, authority and resources to act? |
Change | Training completed but adoption, capacity or leadership commitment weak. | Will people use the new capability and retire the old way of working? |
Benefits | Outputs delivered while assumptions and value drivers have changed. | Is the original outcome still achievable and worth the remaining spend? |
Due diligence before trusting a green status
Before accepting a green tile without challenge, a Program Director should require six things: current position separated from forecast, a stated confidence rationale, a decision log with named owners and dates, quantified response capacity behind material risks, visible and owned technical debt, and a benefit owner outside the delivery team. If one is missing, the colour warrants a second question, not a pass.
4 The case for changing how the CIO measures the program
A Program Director should not ask a steering committee to distrust its dashboard merely because aggregation blindness is a recognised concern. The case for change should be evidence-based: the operational risk, the proposed model, the supporting evidence and the exact executive decision required.
What a Program Director should put forward | What the Steering Committee should understand |
Current problem and evidence | Decision latency, contingency burn, workaround accumulation and cross-vendor interface risk that a status colour alone won't surface. |
Why RAG tiles alone are insufficient | Each function reports accurately within its own boundary; the customer experiences one service, and no tile owns the aggregation. |
What is proposed | A five-lens scorecard reporting current position, forecast and confidence separately, alongside exposure, decision health, technical, commercial, organizational and benefits health. |
Evidence supporting the change | PMI reports that nearly 45% of projects that ultimately succeeded were perceived as at risk at some point. Early communication, reassessment, adaptation and access to resources were among the actions associated with improved outcomes. |
Controls and ownership | Named owners for cross-workstream interfaces and decisions; sponsor actions tracked as evidence; explicit acceptance of residual risk at gates. |
Success measures | Decision age, forecast confidence, technical debt trend, estimate at completion, adoption evidence and benefit-owner commitment. |
Decision required | Adopt the scorecard and the two-sided operating compact; commit to rewarding evidence-based amber and red reporting, not penalizing the messenger. |
The decision a Program Director should ask the committee to make
Agree the compact and the scorecard before the next reporting cycle. Don't wait for a green dashboard to be proven wrong before asking what it isn't telling you — by then the response window is usually the thing that's already closed.
Context, not the verdict
The direction of travel is clear across the industry, but that context should inform judgment, not substitute for it. The read on any single program still rests on its own evidence, its own scorecard, and its own steering committee's tolerance for uncomfortable colour.
PMI SUCCESS REDEFINITION Value, not just RAG PMI now defines success around value delivered relative to effort and expense, not scope, schedule and cost compliance alone. | CONTRACT VALUE EROSION8.6%WorldCC reports average value erosion - defined as deviation from expected results - of 8.6%, showing why commercial health must remain visible throughout delivery. | EARLY RISK VISIBILITYNearly 45%PMI reports that nearly 45% of projects that ultimately succeeded were perceived as at risk at some point, reinforcing the value of surfacing weak signals early. |
My bottom line
Green is a status, not a verdict. It confirms that a defined measure is within tolerance now; it does not establish that the forecast is credible, the service sustainable, the commercial position protected, the organization ready or the expected benefit realizable. The Program Director's obligation is to expose those conditions while leadership still has choices.
Executive takeaway
Separate status from forecast. State confidence explicitly. Reward evidence-based amber. Treat interfaces as deliverables. Keep the business case current. Ask whether the remaining investment would still be approved today.
I help CIOs and steering committees test programs that look healthy on paper but carry multi-vendor complexity, ageing decisions or hidden delivery strain. A focused program health diagnostic applies the five lenses to the integrated plan, decision log, technical and commercial exposures, readiness evidence and benefits forecast, then converts the findings into executive actions with named owners.
Arunava Chakravarty | Independent Consultant & Stragic Advisory
Sources
Project Management Institute. (2026, January 27). “Project Success: What It Means Today—and How Project Professionals Deliver Value.” https://www.pmi.org/blog/project-success
Project Management Institute. (2024). “Maximizing Project Success.” https://www.pmi.org/learning/thought-leadership/project-success
World Commerce & Contracting. (2025, August). “Contract Management: An Overlooked Driver of Business Agility and Financial Performance.” https://info.worldcc.com/contract-management-aug-2025
Comments