Five Questions That Separate Real ERP Progress From Reported Progress

Oct 14

Written By W Jones

An ERP program can look healthy from the inside. The dashboard is green. Milestones are checked off. The percent-complete bar inches forward. A demonstration works as expected.

Then cutover arrives, and a process that looked ready cannot handle real data, an essential interface struggles under volume, or employees discover that a familiar report no longer reconciles.

This gap between reported progress and real progress is not necessarily a sign of a bad vendor or a careless team. It reflects a structural weakness: activity is easy to report, while readiness takes evidence. For leaders funding a complex ERP project, the question is not whether work is happening. It is whether the organization can verify that the work is producing the capabilities it needs.

Why green dashboards can mislead

Many project dashboards track activity: tasks assigned, meetings held, documents submitted, or milestones marked complete. Those indicators can help teams coordinate, but they do not prove that converted data will reconcile, that interfaces will perform under expected volumes, or that essential business processes will work from start to finish.

There is another human factor. The people reporting status are often responsible for delivering the work. Their optimism may be entirely sincere. But when the messenger and the measured are the same, a status update can reflect confidence and effort more than independent confirmation. That is one reason programs can be surprised at go-live, even when reporting looked consistently positive.

An independent view helps leaders distinguish what a team says is complete from what the available evidence supports. In ERP consulting and broader IT transformation, that distinction can affect decisions about timing, readiness, and where to focus attention next.

Five questions to ask about ERP progress

1. What was actually tested, and with what data?

A configuration walkthrough can show that a screen or process appears to work in a demonstration. It does not necessarily show that the process holds up with realistic data, expected volumes, unusual cases, or errors that require a decision.

Ask what the test was meant to prove and whether the conditions were representative of daily operations. Strong evidence comes from observed results across realistic scenarios, including exceptions and edge cases, not just a successful presentation or a completed testing task.

2. Who signed off, and were they independent of the build?

People who configure or develop a solution have valuable knowledge of what it is intended to do. Their review matters. But if the same team both builds and blesses the result, leadership is hearing a quality opinion from the delivery team, not a separate assurance perspective.

Look for a clear distinction between the team’s status report and an independent view of whether the evidence supports that status. Independent verification and validation (IV&V) provides leadership with a perspective that is not filtered solely through the people responsible for delivery.

3. What breaks if this fails at cutover?

A task list may treat every item as equally important. Operations do not. A delay in a low-impact report is different from a problem that affects payroll, claims, procurement, financial reporting, or aid disbursement.

Ask which services or decisions are affected if a process does not work, and rank concerns by their operational impact. That helps leaders see where unresolved issues could create the greatest disruption, and whether a reassuring overall status is concealing a critical risk.

4. Can the business reconcile the numbers today, before go-live?

A new system cannot create confidence in figures that the organization cannot currently explain. If two reports disagree and a spreadsheet is used to decide which number to trust, the transformation may carry that ambiguity into the future environment.

Evidence of readiness means business leaders can understand the numbers, explain meaningful differences, and make informed decisions about unresolved questions. This is especially important for organizations accountable for public funds, grant activity, or results reported to oversight groups. Rules, thresholds, and award terms can change over time; verify current requirements before treating any single control as evidence of readiness.

5. If key people leave, does the progress survive?

A process may appear ready because one experienced employee knows which spreadsheet to use, whom to contact, or how to resolve an exception. If that knowledge lives only in someone’s head, the organization has a dependency, not durable progress.

Ask whether the people who will operate and support the process can explain how it works, where to find the information they need, and how to handle common issues. Progress is more resilient when it is understood beyond a few key individuals.

Why the stakes vary, and why accountability is shared

The consequences of a weak cutover depend on what an organization does. For a government agency, appropriations cycles and audit findings can leave little room for a quiet rework year. Higher education institutions may see back-office difficulties spill into enrollment processes, delayed aid disbursement, or frustration for faculty and staff. In healthcare, enterprise systems can support supply chain, billing, and clinical operations; a disruption can be felt well beyond the finance office. In manufacturing and logistics, manual workarounds may keep activity moving for a while, but their true cost can become clearer when volume increases.

Across these settings, leaders answer to someone beyond the project: an auditor, board, regulator, funding agency, employee, student, or community. That accountability is why an independent set of eyes can be valuable. It helps leaders understand whether reported readiness is supported by evidence before the consequences of a gap become harder to manage.

Making oversight practical

Oversight does not require turning every update into an audit. It starts with a few clear principles:

Define “done” in evidence terms before the next phase begins. Agree on what must be true (not simply what work must be completed) so expectations are clear while there is still time to respond.
Make accountability visible. As a daily management practice, “the start of the day begins with reviewing Role Based Dashboards with tasks associated with employee responsibility.” Pair those responsibilities with a view of what has been verified, what remains uncertain, and who is addressing the uncertainty.
Separate building from verifying. IV&V exists to give leadership an independent perspective on whether the program is on course and whether reported progress is supported.
Test failure paths, not only the happy path. Consider whether conversion reconciles, integrations perform at expected volume, payroll can be run in parallel where appropriate, and the organization can move from the legacy environment with a clear understanding of risks.
Raise exceptions early. A program that identifies and communicates risks is safer than one that always appears green. Early visibility gives leaders more opportunity to make informed choices.
Connect progress to business capability. When Sprints carry business-process stories, development stays connected to business needs. Progress can then be discussed in terms of capability delivered, not just tasks completed.

These principles are relevant to ERP work across sectors, from business process transformation and government IT compliance concerns to project management for hospitals. The right assessment depends on the organization’s context; a dashboard or a single control should not be treated as a substitute for understanding that context.

Confidence comes from evidence

Independent oversight does not replace a project team or assume that its work is failing. It gives leadership a clearer way to see what is working, where uncertainty remains, and which issues deserve attention. Done well, it does not slow a project down. It helps prevent the project from discovering its most important problems at the worst possible moment: the week the money runs out or the auditor arrives.

An independent set of eyes protects the investment your team is making by helping decision-makers act on a more complete view of progress. Read more about independent verification and oversight for ERP programs, or explore CD&A’s consulting services.

If you lead an ERP transformation, consider an independent conversation about one question: Would your reported progress survive verification? Contact CD&A Consulting Services Inc. to discuss the outcomes an independent perspective could help clarify for your organization.

W Jones https://www.cdaconsultinginc.com