Go / no-go: five questions, 48 hours before go-live
In 2018, switching on its new software cost Revlon around $64 million in sales it could not ship, by its own estimates. Go-live day is often decided by the schedule. I prefer to decide it on five answers, 48 hours ahead: five yeses, you go; a single no, you postpone.
Author
Tudor HilcuFounder & CEO, THG Conseil
Published
Reading time
9 min
Topics
Projects, Go-live, Committees
Contents8
In February 2018, Revlon switched on new management software in the United States, an ERP system from SAP. Its plant in Oxford, North Carolina, had trouble manufacturing some finished goods and shipping orders to several large US retailers. In its annual report, Revlon estimated that the launch left it unable to ship around $64 million of sales in 2018, and cost it $53.6 million in additional charges, mainly to restore service to its customers.
Two months later, in the UK, TSB, a bank with 5.2 million customers, moved its data onto a new IT platform. Problems started almost at once, and it took the bank until December to get back to normal.
Go-live day is often decided by the schedule: the date has been announced, the teams are booked, the supplier is waiting for its milestone. I prefer to decide it on five answers, asked 48 hours ahead. This is tool no. 01 in my “One minute, one tool” series, published on LinkedIn on 7 October 2026. Here is the full version: what “yes” means for each question, how to run the meeting, and a sheet you can reuse.
The five questions
Has the last full test run, from order to invoice, passed?
Are the key people trained, and available on the day?
Do your biggest customers have stock in hand?
Is the rollback ready, and until when does it stay available?
Who can call a halt?
Five yeses, you go. A single no, you postpone, and you tell your customers before they notice.
Why 48 hours ahead? A week before, the answers are still promises: the last test run hasn’t happened yet. The night before, nobody dares say no any more, and it is too late to warn customers properly. Forty-eight hours leaves time to postpone without alarming anyone.
What “yes” means, question by question
1. The last full test run has passed
A full test run follows a real order from end to end: order entry, picking, shipping, invoice, payment received, then the entry in the accounts. On your real data, not on a test set. “Passed” means done and successful. “Planned for tomorrow” or “nearly passed” is a no.
Testing is often what gets cut when the schedule slips. At TSB, according to the UK prudential regulator, the PRA, the programme quickly fell behind its new schedule, to the point that critical testing plans and principles had to be departed from to hold the date.
2. The key people are trained, and available
Write down the names: who enters orders, who unblocks a stuck order, who invoices, who answers customers on the phone. For each, two boxes: trained on the new tool, present on the day and the week after. Someone who is trained but on leave counts as a no.
Revlon acknowledged a gap of this kind in its annual report: it did not have enough trained people, in the operations affected by the new software, to run its internal controls over financial reporting. The measures it announced include training staff and bringing in extra people.
3. Your biggest customers have stock in hand
The first to see a failed switchover are not the IT team: they are the customers whose deliveries don’t arrive. For your ten biggest customers, deliver a few days’ or a few weeks’ worth of stock ahead of the switchover, and tell them the date.
At Revlon, the plant was back to normal capacity by April 2018. Yet in its annual report, the company wrote that at 31 December 2018 it was still refilling inventories across its retail partners, particularly internationally, and it listed expedited shipping fees among its unplanned expenses. Stock takes longer to come back than the plant does.
If you sell services rather than products, the question becomes: are the week’s important deliveries and invoices done before the switchover, or pushed back until after, and do your customers know?
4. The rollback is ready, and you know until when
Three things to write down: how you go back to the old tool, how long it takes, and until when it is possible. Past a certain point, orders entered in the new tool would have to be keyed in again in the old one, and going back costs more than pressing on. You need to know that point before you start, not on day three.
It can even come before go-live day. At TSB, on 10 April 2018, less than two weeks before the switchover, the board met to decide whether to commit the bank to the migration for good. The notice went out on 12 April, and with it went the other exit route the bank had kept open: a back-up option in which a new provider would have run a copy of the old platform. As for rolling back after the migration, the PRA says it was, technically, all but impossible.
5. Someone can call a halt
A name, written down, known to everyone. That person can stop the go-live without having to justify it for weeks afterwards, and decides on facts, not on intentions.
This is the clearest lesson from the TSB case. According to the PRA, the paper recommending go-live ran to 972 pages; it went to the board on 18 April 2018. The letter in which the main IT supplier confirmed it was ready was not in it: the board relied on a single paragraph in the attestation of the bank’s chief information officer. And the confirmations from the supplier and its subcontractors were, to some extent, statements of intention rather than of fact; all but one still flagged tasks or tests yet to be completed.
Revlon, for its part, announced that it would strengthen its review and sign-off procedures for IT implementations.
Postponing is not always enough
TSB had already postponed once. The switchover was planned for 5 November 2017. At the end of September 2017, the bank pushed it back to the first quarter of 2018, and the date was then set for 22 April. Postponing was not enough: it was to hold that new date that critical testing plans had to be departed from.
The migration took place over the weekend of 20 to 22 April 2018. The data moved across, but the failures came almost at once: online, telephone and mobile banking, branch technology, and problems with card payments. All 550 branches were affected, along with a significant share of customers. In December 2022, the two UK regulators, the FCA and the PRA, fined TSB a total of £48.65 million; the bank had also paid £32.7 million in redress to its customers.
The rule I draw from it: you postpone so that the five answers become yes, not to buy a few weeks on the schedule. A new date only counts if the five questions are asked again 48 hours before it.
How to run the go / no-go meeting
When. 48 hours before go-live, in everyone’s diary as soon as the switchover date is set.
Who. You, the project manager, someone responsible for each department affected (sales, logistics, finance) and the supplier.
How. One answer per question, yes or no, with the evidence to back it: the test run report, the list of people with the days they will be in, the list of customers delivered in advance, the rollback procedure and its cut-off date, the name of the person who can call a halt.
No “yes, but”. A full checklist leaves room for written reservations on minor points. These five questions do not.
The decision goes in writing. Go or postpone, the date, the signatures. If you postpone: the date of the next go / no-go meeting, and the message to customers, sent the same day.
Thirty minutes is enough when the evidence is ready. When it is not, you already have your answer.
Fictitious example: the go / no-go sheet of a distribution SME, 48 hours before it changes its management software
Question
Answer
Evidence
1. Full test run
Yes
A real order traced from entry to the accounts, on Tuesday
2. Key people
Yes
6 people trained, all present until the following Friday
3. Stock in hand
No
3 of the 5 biggest customers delivered in advance, 2 still waiting
4. Rollback
Yes
Procedure tried on Monday, possible until Wednesday noon
5. Who calls a halt
Yes
The operations director, named in writing
Decision: postponed by a week. The two customers concerned are called the same day and delivered in advance; the new go / no-go meeting is set for the following Tuesday.
Four yeses are not enough. Question 3 would have cost dearly in the first week, and the customers would have been the ones to find out.
What I learnt
For TotalEnergies, since 2025, I have been in charge of the go-live of critical projects: a daily steering committee, sign-off of critical tests, a checklist, a rollback plan ready, and a support team for the days after go-live. For The Walt Disney Company, on an ERP and WMS (warehouse management system) programme, I also ran live operations once the system was in service, including remediation plans after major incidents.
What I keep from it is a simple conviction: a critical go-live is decided before the day. Criteria written in advance, a rollback plan ready, a daily committee in place. The five questions are the short version, the one a business leader can ask in person.
The limits of these cases
Revlon’s figures are its own estimates, published in its reports to the SEC, the US market regulator. They measure sales it could not ship and additional charges, not the cost of the project. Its reports do not say what Revlon had checked before go-live: I do not claim these five questions would have prevented everything.
For TSB, the facts come from the two UK regulators. The PRA acknowledges that the bank and its chief information officer believed, throughout the programme, that no migration would take place until everything was ready. It attributes the failures themselves mainly to configuration, capacity and coding problems.
Finally, five questions replace neither testing nor a full checklist: they are there to help you decide. If your switchover affects your accounts or your contracts, prepare it with your lawyer and your accountant.
Where to start this week
Note the date of your next switchover, however far off: management software, till system, invoicing, online shop, warehouse.
Copy the five questions onto one page, and write next to each one who will answer it and what evidence you expect.
Name, in writing, the person who will be able to call a halt, and tell the whole team.
Book the go / no-go meeting in everyone’s diary today, 48 hours before the date.
Write the message to your customers now, in case you have to postpone. On the day you need it, you won’t have time to get it right.
One page and one meeting: go-live day will no longer be decided by the schedule.