Go-live is often treated like a celebration.

Slides are polished. Defects are trending down.
The room wants to move forward.

But go-live is not a celebration.
It is a transfer of risk.

Up to that point, problems belong to the project.
After that point, they belong to Finance, Operations, Audit — and ultimately to the executive team.

The difference between a smooth transition and months of instability rarely comes down to configuration quality.

It comes down to whether the sponsor asked the right questions before saying yes.

1. Are We Validating Readiness — or Just Reporting Progress?

Most go-live decks focus on progress:

• % configuration complete
• Test cases executed
• Defects closed
• Training delivered

Those metrics measure effort.

They do not measure operational capability.

Readiness means something different:

• Can critical processes run end-to-end without hidden workarounds?
• Can users operate without the project team constantly intervening?
• Are remaining risks clearly documented and owned?

If your decision is based mainly on activity metrics, you are approving momentum — not readiness.

This distinction is foundational to sound ERP governance.
(See: https://www.fitgapfinance.com/erp-governance-model-roles-decision-rights/)

2. What Manual Work Is Being Pushed Into Day 1?

Every ERP implementation contains compromises. That is normal.

What becomes dangerous is when those compromises are invisible.

Typical examples:

• Excel reconciliations replacing incomplete integrations
• Temporary journals used to bridge configuration gaps
• Controls deferred “just for the first close”
• Manual approval flows because workflows were postponed

Before approving go-live, force clarity:

• What manual steps will exist on Day 1?
• Who owns each one?
• How long are they acceptable?
• What is the remediation timeline?

If this discussion does not happen, the organization is not going live with a system.

It is going live with operational debt.

Many of these risks originate in earlier shortcuts — especially in data migration and design decisions.
(See: https://www.fitgapfinance.com/tag/data-en/)

3. Can Finance Close — Realistically — Within the First Two Cycles?

The first close after go-live is not symbolic.

It is a stress event.

Sponsors should ask directly:

• Has a full close simulation been executed with realistic data volumes?
• Do controllers understand posting logic and data origins in the new system?
• Are reconciliations defined, assigned, and time-bound?
• Are executive reports validated against expectations?

A system can technically “work” and still fail to support a credible close.

Once Finance loses confidence, the damage is not technical — it becomes reputational.

And reputational recovery takes much longer than fixing configuration.

4. Do We Explicitly Know What Is Not Ready?

Silence in a steering committee does not mean alignment.

It often means discomfort.

Responsible go-live governance requires:

• A short, explicit list of known gaps
• Clear articulation of operational and financial impact
• Documented acceptance of residual risk

Healthy approvals contain tension.

If approval feels frictionless, ask why.

Sponsors are not there to protect the schedule.
They are there to protect the institution.

5. If Something Breaks, Who Decides — and How Fast?

Post go-live instability is common.

What determines impact is not whether issues arise — but how quickly decisions are made.

Before go-live, sponsors should confirm:

• Who holds production decision authority?
• What triggers executive escalation?
• What can be resolved immediately vs escalated?
• Is hypercare structured with defined accountability?

Governance defined during a crisis is governance under pressure.

Governance defined before go-live is resilience.

Go-Live Is a Leadership Decision

Approving go-live is not a reward for effort.

It is a conscious assumption of accountability.

Strong sponsors do not ask:

“Are we on track?”

They ask:

“Are we prepared to absorb the consequences?”

The quality of that decision often defines the credibility of the entire transformation.

Practical Use

If you are approaching a go-live decision, use these five questions as a forcing mechanism:

• In your steering committee
• In your executive pre-read
• In your private alignment conversations with Finance leadership

If answers are vague, politically softened, or overly optimistic, pause.

A delayed go-live with clarity is recoverable.

A rushed go-live without clarity creates institutional drag that can last years.

Continue Exploring

If this topic resonates, you may also find useful:

• ERP Governance: Why Structure Fails Without Accountability
  https://www.fitgapfinance.com/tag/implementation-governance-en/
• Data Migration in ERP Projects: The Risks Nobody Mentions
  https://www.fitgapfinance.com/tag/data-en/
• ERP Psychological Resistance: What Leaders Miss
  https://www.fitgapfinance.com/erp-psychological-resistance/

This article is part of the FitGap Finance series — a business-first perspective on ERP governance, decision-making, and control beyond go-live.

🇫🇷 Version française: https://www.fitgapfinance.com/mise-en-production-erp-questions-sponsor/