Skip to content

Your team is ready for go-live when the people who run your part of the business can do their real jobs in the new system, the data they depend on has been checked by them, and everyone knows what happens if something goes wrong in week one. The delivery partner is responsible for the system working. You are responsible for your team or company being able to operate - and sometimes that is the part that gets left behind.

If you run a business function, the programme will probably ask you for people, time and sign-offs. It will unfortunately also tell you less than you need about what is coming. This countdown is written from your side of that relationship.

Firstly - and just to emphasise the point - your team should have been involved in the programme throughout its life. Design, build, testings, change etc etc. It shouldn't be a surprise as to what is coming - however, work through this countdown just to be sure ;-)

 

Twelve weeks out

If you don't know already, this is the point to find out what is really changing for your team. Ask the programme for the change impacts for your area, role by role. If it does not exist, say so and escalate. A list of changed transactions is a start, but you also need to know what changes in terms of process, reporting, approvals, month-end, and the conversations your team has with customers and suppliers.

Again - this should be in place already, but if not, this is also the moment to name your super users. Pick people your team already goes to for help, rather than whoever happens to be free. Then agree, in writing, how much of their week the programme will consume. A super user who is still doing a full day job will not be ready, however willing they are.

Jayne Mather, who leads change work at Limelight, wrote the book Super User Networks for Software Projects. 

Superusers are the most powerful and effective way to create business adoption that the business 'truely owns.'

 

Six weeks out

By now your team should have been through training. The useful question is whether they can do the job, rather than whether they attended. Ask for a small number of your people to process real work in the test system, with real exceptions to standard processes: an invoice that does not match, an order with a missing price, the return with no receipt etc.

This is also when the data matters. Your team should see their own data in the new system before go-live. Finance should check opening balances. Supply chain should look at migrated stock and open orders. Sales should check customer records and pricing. If your people have not seen it, they will find the problems on day one, with customers waiting.

At this point the programme should be running regular readiness assessments. These should be both subjective and objective, with the goal of temperature checking the business. You need to be checking hard facts, as well as opinions and hearsay. Adoption is often lead by informal networks - so be sure to be influencing them. 

 

Two weeks out

Go-live criteria for your functional area should be agreed by now, before anyone is under pressure to hit the date. Make sure they are documented in the cutover plan. Work out what the close down tasks are and what cutover tests should be transacted to 'prove go-live'. What do you need to test in the PRD instance before you turn the system on? For instance: Can the team raise, approve and pay a supplier invoice? Can they take, fulfil and bill an order? Can they close a day's trading? Depending on the industry and sector these will vary. If the answer to any of these is no, that could stop the go-live - rather than cripple the business. 

Check the cutover plan for your area line by line. Know when the old system stops, what your team does in the gap, and who decides if something has to be rolled back. Cutover is often planned by IT, and the business steps that sit inside it are easy to miss.

At this stage, warning signs are worth taking seriously. Serious flags include: Training being reported by attendance alone. Super users are still fitting the programme around their day job. Cutover decisions are being made without your functional team in the room. Nobody on your team can say what they would do if payments failed to run on day one.

Escalate concerns if you feel at all uncomfortable - your business will thank you for highlighting problems before they realise.

 

The first week

Plan for it to be slow. Every new system is slower in its first week and the business needs to know that is expected. Agree with your own leadership which work comes first if the team falls behind. Paying suppliers and shipping orders usually matter more than tidy reports.

Make sure your super users are free to help, and that issues have one clear route into the support team. A quick daily check-in with your team leads catches problems while they are still small.

 

The first month

Most of the cost of a difficult go-live arrives after the first week. Backlogs build. Workarounds appear. People start keeping their own spreadsheets because they do not trust the new reports yet.

Ask for support to stay in place for the whole of the first month, including the first month-end. Track how the system is being used, rather than how many tickets are open. Also, agree who will clear the backlog and importantly who is responsible for it.

 

Where Limelight fits

We work on the client side of SAP programmes, leading business change, readiness and cutover alongside the delivery partner. Our part is making sure the business can run on day one. We use sophisticated custom tooling to ensure these event are successful - but the principles remain. 

If go-live is on your horizon and you would like a second view of your team's readiness, book a Readiness Review. It is a 45-minute conversation with one of our directors.

Neil How

About the author

Neil How

Neil ran his first SAP transformation programme in his early twenties. He spent the next 21 years working both client side and for various consultancies running numerous SAP programmes. After successfully completing over 15 full lifecycles he took a senior leadership/board position and his work moved onto creating the same success for others.

More about Neil

© 2026 Limelight Consulting