TRC Solutions

Insight Governance

The Watermelon Reporting Problem

When programme reporting stays green while operational pressure has already turned red underneath.

“Green on the outside, red on the inside. The watermelon pattern is one of the most consistent governance failure modes in enterprise transformation — and one of the most expensive to recover from once it surfaces at board level.”

When programme reporting stays green while operational pressure has already turned red underneath.

As an SAP programme moves into delivery and testing, the risk profile changes. The SI’s focus narrows entirely to protecting the go-live date — and the way risk is reported changes with it.

This is when the watermelon metric appears: a status report that is green on the outside, but red on the inside.

When a programme is governed by the delivery team, friction is hidden. Requirements are deferred. Integration failures are reclassified as “post-go-live enhancements.” The board is presented with a narrative of success right up until the moment the system collapses in production.

To prevent this, the board must ask four questions — focusing entirely on delivery integrity and go-live readiness.

The SI Deflection
“We are adopting an agile MVP approach.”

The SI is moving difficult scope into a post-go-live “Phase 2” that you will pay extra for. What the SI calls a Minimum Viable Product is often just failed scope in disguise. If the business cannot operate on the MVP without manual workarounds, it is not viable. It is simply incomplete.

The SI Deflection
“Yes, the system passed all functional tests.”

The system works in a vacuum, but end-to-end integration with legacy systems is failing. SIs often push programmes into User Acceptance Testing (UAT) before the architecture is stable, forcing the business to test a broken system. UAT should be a final validation, not an extended debugging phase.

The SI Deflection
“Yes, we will resolve minor defects during hypercare.”

Going live with known defects is how you end up in a $172M shareholder lawsuit. Hypercare is designed for user adoption and minor stabilisation, not for finishing the build. If the defect backlog is growing as you approach go-live, the date must move. The SI will push to launch to trigger their milestone payment; independent governance will stop them.

The SI Deflection
“Our AMS team will provide seamless support.”

You are locked into a high-margin Application Management Services (AMS) contract because nobody else understands the custom code they built. The SI has created a dependency trap. Independent governance ensures the architecture is standard enough to be supported by the market, not just the firm that built it.

Pattern

The Watermelon Metric — Delivery & Go-Live Readiness

If this pattern is on your programme

If your SI’s answers sound like deflections, you do not have a governance model. You have a reporting exercise.

In the next post, we will move beyond questions and look at the hard data: how to read a programme health report and spot the lies hidden in the metrics.