In our previous discussion on Watermelon Status, we identified the "silent killer" of large-scale technology initiatives: the tendency for projects to appear green on the outside while being deep red on the inside.
But identifying the problem is only half the battle. If you are a CIO, CTO, or a Transformation Head, you don't just need a diagnosis, you need a cure. Most "false-green" reporting isn't the result of intentional deception; it’s a symptom of broken delivery governance.
When governance is treated as an administrative overhead rather than a strategic steering mechanism, it creates a vacuum where risks are buried, decisions are delayed, and "green" becomes the default setting for survival.
Here are the seven most common delivery governance mistakes we see in enterprise environments, and the practical steps to fix them through effective programme rescue consulting.
1. Governance "Theatre" vs. Real Control
The most common mistake is confusing activity with progress. We see programmes with dozens of weekly meetings, 100-page slide decks, and complex gate processes, yet no one can answer who is actually empowered to make a decision when things go wrong.
This is governance theatre. It’s a performance of control without the substance of it.
- The Fix: Strip governance back to its core purpose: making decisions and removing blockers. If a forum doesn't have the authority to reallocate budget, change scope, or shift resources, it shouldn’t be a decision-making body.
2. Unclear Decision Rights (The "Bouncing" Decision)
We often see change requests bounce between a Steering Committee, a Design Authority, and a Programme Board like a hot potato. Each group assumes the other has the final say, or worse, they require unanimous approval across all three. This paralysis forces teams to continue working on outdated assumptions, keeping the RAG status "green" simply because there is no official decision to change it.
- The Fix: Map your decision rights. Use a simple RACI model, but focus specifically on the "A" (Accountable). There should only be one person or body accountable for any single decision type.
3. Disconnected Information (The Lagging Indicator Trap)
If your delivery governance relies on reports that are two weeks old, you aren't steering the ship; you're reading the wake. Most "false-green" reporting happens because the data being presented is a lagging indicator, milestones that were "supposed" to be met, rather than leading indicators like technical debt, open defects, or resource utilization.
- The Fix: Shift to real-time, objective data. At Dark Consultancy, our delivery governance consulting approach prioritizes "Definition of Done" evidence over subjective status updates. If it isn't tested and integrated, it isn't green.
4. Passive Sponsorship
A Steering Committee is not an audience; it is an active participant in the delivery lifecycle. When sponsors attend meetings but fail to challenge reporting or own difficult trade-offs, they signal to the delivery team that "no news is good news." This culture is the primary driver of false-green reporting.
- The Fix: Re-engage your sponsors. They must be the ones to explicitly own the trade-offs between scope, time, and budget. If a sponsor isn't asking "Why is this still green when we missed the integration date?", they aren't sponsoring, they're spectating.
5. Governance Models That Don't Evolve
A governance structure designed for the initial design phase is rarely fit for the build, test, or cutover phases. Yet, many enterprises leave their models unchanged for the entire multi-year lifecycle. This leads to a mismatch where the key risks (e.g., technical debt or deployment defects) are ignored because the governance "checklist" is still looking for high-level design documents.
- The Fix: Governance must be dynamic. We recommend a Delivery Diagnostic at every major phase shift to ensure the forums, metrics, and decision rights are aligned with the current risks of the programme.
6. Lack of Psychological Safety (The "Shoot the Messenger" Culture)
If the last person who reported an "Amber" status was grilled for two hours while the "Green" reporters were ignored, your organization has incentivized false-green reporting. In high-pressure enterprise environments, reporting "Red" is often seen as a personal failure rather than a responsible management action.
- The Fix: Reward the "Early Warning." A core pillar of IT programme rescue is resetting the reporting culture. Leadership must explicitly state that an "Amber" raised today is an opportunity to fix a problem, while a "Red" raised on the eve of go-live is a catastrophe.
7. Overlapping Forums (Death by Meeting)
When the same group of senior leaders meets three times a week under different names (PMO Sync, Portfolio Review, Digital Board), the signal-to-noise ratio drops to zero. Decisions get diluted across multiple forums, and accountability disappears.
- The Fix: Consolidate. If two forums have more than 70% overlap in attendance or agenda, merge them. A streamlined governance path is much harder to hide "watermelon" statuses in because there are fewer places for the truth to get lost.
The Programme Rescue Playbook: How to Fix "False-Green"
If you suspect your current programme is a "Watermelon," you don't need another status meeting. You need an intervention. Our approach to programme rescue consulting follows a proven three-step model:
Step 1: The Delivery Diagnostic
We don't look at the slide decks; we look at the code, the Jira boards, and the people. We conduct a fast-track assessment to find the real critical path and surface the "hidden red" risks.
Step 2: Define Objective RAG Rules
We replace "I feel this is green" with "This is green because [Evidence A, B, and C]." We establish hard variance thresholds, if a milestone is missed by more than 5%, it’s automatic Amber. If it’s on the critical path and missed, it’s Red. No exceptions.
Step 3: Create the Execution Roadmap
Once the truth is out, we don't just point at the problem. We build an Execution Roadmap that re-baselines the scope, schedule, and resources to something that is actually achievable.
Conclusion: Stop Measuring, Start Steering
Governance is not about reporting history; it is about shaping the future. By fixing these seven mistakes, you transform governance from a bureaucratic burden into a powerful tool for delivery certainty.
If your high-stakes initiative feels like it’s drifting, or if your gut tells you the "Green" status on your dashboard isn't the whole story, it’s time to move beyond reporting.
Is your transformation at risk?
Don't wait for the "Watermelon" to burst. Schedule a Delivery Diagnostic with Dark Consultancy today and get your programme back on the path to execution.
FAQ: Delivery Governance & Programme Rescue
What is the difference between project management and delivery governance?
Project management is about the "how", the day-to-day execution. Delivery governance is about the "should", ensuring the project remains aligned with business goals, managing strategic risks, and providing the authority to make critical trade-off decisions.
How do I know if my reporting is "False-Green"?
Look for the "RAG Cliff." If your project stays green for 90% of its duration and then suddenly drops to red in the final weeks, you have a false-green reporting problem. Other signs include vague status updates ("Progressing well") and a lack of evidence-based reporting.
Why is programme rescue consulting better than internal audits?
Internal audits often focus on compliance with process. Programme rescue focus on the reality of delivery. We bring an external, execution-first mindset that isn't afraid to challenge internal politics or the "status quo" that allowed the project to stall in the first place.
Can a "Red" project actually be saved?
Yes: but rarely by the same team and governance structure that turned it red. Saving a project requires a total reset: a new baseline, simplified governance, and a clear Execution Roadmap that prioritizes the most critical business outcomes.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia ; ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn