Straight answer

Are we ready to go live on our new system?

Only if the go-live conditions were agreed in advance and the evidence shows each one has been met. Readiness is not a feeling or a date on the plan. If the business, not the project team, cannot sign off that it can trade, pay people and close the books on the new system, you are not ready.

How can the board tell whether it is under control?

Signs it is under control

  • A go or no-go checklist was agreed before testing ended and has not been rewritten to fit the date.
  • A full rehearsal of the data migration has run, and the results are reported in plain numbers.
  • A tested plan exists for going back before the point of no return, and for keeping the business trading after it, with a named person who can call it.

Signs it is not

  • The criteria are being softened as the date approaches, with open issues reclassified as “post go-live”.
  • Business users have not run their own end-to-end tests of daily work.
  • Nobody can describe what happens in the first week if invoices, orders or payroll fail.

What is the one question to ask?

Ask at the next meeting

Who in the business has signed to say their area is ready, and what did they check before signing?

A strong answer

Named business owners for each area, each confirming specific tests, data checks and staff training, with any open issues listed alongside a workaround and an owner.

A weak answer

“The implementation partner has confirmed we are ready.”

What does ready actually mean?

Go-live is the moment the company stops using its old systems for core work such as orders, invoicing, stock and payroll, and starts relying on the new one. Ready means four things together. The data has been moved and checked. The processes have been tested end to end by the people who will use them. Staff are trained and know where to get help. And there is a plan for the first weeks, including how to fall back if something important breaks.

Each of these should have a measurable condition agreed in advance. The go or no-go meeting is then a check against those conditions, not a debate about whether the team feels confident.

What might the board be getting wrong?

The board may have made the date the thing that matters. If a launch date has been announced to customers, lenders or staff, or tied to a bonus, the pressure to go live regardless becomes very strong. Directors may also treat a delay at this stage as a failure, when a late, deliberate “not yet” is often the best decision available. If management fear the board’s reaction more than a bad go-live, they will go live. Make it clear, in advance, that the board will back a decision to wait if the evidence calls for it.

What should the board ask for?

Ask to see the go or no-go criteria now, before the decision meeting, and ask what has changed in them since they were first written. Ask for the results of the last migration rehearsal and the outstanding defects, grouped by how badly they would hurt the business. Ask who can stop the go-live, and whether they have actually been told they can. Ask how the business will know in the first days that cash, orders and pay are flowing. If those answers come with evidence the board can see, not only assurances, the team is probably ready, even if some issues remain open.

Where to go from here