Thank you for this insightful article. You hit the nail on the head regarding the distinction between implementation readiness (technical testing) and operational readiness (validating whether the business can actually function on Day One).

In my advisory practice, I work extensively with public sector clients on major enterprise technology initiatives. In the public sector, large-scale ERP projects typically carry explicit statutory or compliance mandates requiring an independent, third-party Independent Verification and Validation (IV&V) vendor to perform continuous technical and operational oversight throughout the project lifecycle.

Working in this IV&V capacity has given me a front-row seat to how critical independent oversight is to securing successful ERP outcomes. When embedded early, an effective IV&V team serves as an essential partner to leadership by doing the following:

1. Bridging Technical and Operational Readiness: System integrators (SIs) and internal IT teams naturally focus on software delivery and scripted functional milestones. An independent IV&V team actively evaluates whether non-functional benchmarks—such as real-world processing volumes, end-to-end integration flows, and business continuity safeguards—are actually being validated before go-live.

2. Preventing "Self-Certification" and Blind Spots: IV&V provides unbiased, evidence-based verification of vendor progress. This prevents project leadership from relying solely on vendor self-certification or optimistic completion metrics, ensuring that risks in testing, governance, and architecture are surfaced while there is still time to remediate them.

3. Maintaining Traceability and Governance: As cloud ERP implementations introduce continuous updates, IV&V ensures that requirements traceability (from initial business cases through user stories, test scripts, and defect logs) remains intact so operational continuity isn't compromised post-deployment.

Conversely, I have also observed projects where third-party oversight was brought in late in the process—often as a reactive measure after schedule compression, testing failures, or scope drift had already taken hold. In these late-entry scenarios, the implementations were noticeably less successful. When oversight is added late, IV&V is limited to performing "damage control" or auditing architectural decisions that are already locked in. This forces organizations into costly rework, prolonged hybrid operations, or reliance on unvalidated legacy workarounds to hit go-live dates.

Your point that ERP testing should be measured by the operational disruption that never occurs resonates deeply. Independent IV&V oversigh, when engaged early,  is one of the most effective governance tools public sector organizations have to ensure that operational resilience is built into the foundation of an ERP program long before go-live.

Dr. Chris B. Young

www.youconinc.com