A green dashboard doesn’t mean a healthy project, it often means you’re measuring the wrong things, or rewarding the wrong behaviours. This episode explains why status reporting drifts toward “green” when red is punished, when RAG ratings are subjective, and when teams report activity (tasks closed, documents delivered) instead of readiness (integration, testability, verified capability). Using a realistic programme example, we show how projects can look stable for months while risk quietly compounds until integration or verification exposes the truth and recovery becomes expensive. The fix isn’t prettier reporting; it’s clearer thresholds for green/amber/red, stronger leading indicators (rework, defect trends, requirements churn, integration readiness), and leadership that makes early escalation safe and useful. Key takeaway: a green dashboard without evidence isn’t reassurance, it’s risk.

Key references:

• PMI, PMBOK® Guide (risk management, governance, reporting principles)

• ISO 31000, Risk Management — Guidelines (risk framing, decision-making under uncertainty)

• Barry Boehm, “Software Risk Management” (early risk identification and mitigation thinking)

• Eliyahu M. Goldratt, Critical Chain (buffers, critical path logic, behaviour around reporting)

• W. Edwards Deming, principles on measurement systems & incentives (how targets distort behaviour)

• Amy Edmondson, The Fearless Organization (psychological safety and truthful escalation)

• Bent Flyvbjerg (research on optimism bias / strategic misrepresentation in major projects)