Most SAP projects in trouble don't announce it. The status report stays green, the go-live date holds on paper, and the people closest to the work stop saying what they think. By the time the board hears about it, the budget is gone and go-live has moved twice. If you suspect your project is in that place, the next few weeks matter more than the last few months. This is how to use them.
The signs it's more than a rough patch
Every SAP project has bad weeks. These are the signs of something bigger:
- Go-live has moved more than once, and nobody can say what changed.
- The status report is green, but the steering meeting keeps running long.
- Testing keeps getting squeezed to protect the date.
- Data migration has been "nearly done" for three months.
- Key users have stopped coming to workshops, or come and say nothing.
- The partner's senior people were in the sales meeting and haven't been seen since.
If three or more of these sound familiar, your project is in the same place as many others. SAPinsider research reported by ERP Today found that 55% of organisations have deployed S/4HANA, but only 34% say the move is complete. A lot of programmes are stuck somewhere in between.
Stop and look before you change anything
The instinct in a crisis is to act: fire the partner, add people, push harder. Hold off for two weeks and get an honest picture first.
Ask for an independent review from someone with no stake in the outcome. They should look at four things: the scope today against what was signed, the real state of data migration, the test results rather than the test plan, and who on each side can make decisions. That last one is often where the trouble sits. Projects stall when every question has to travel up two layers and back.
Cut scope to save the date, or move the date to save the scope
Most rescues come down to one trade-off. You can go live on time with less, or go live later with everything. Trying to keep both is how projects get into trouble in the first place.
Going live with less usually works better. Pick the processes the business can't run without, get those stable, and move the rest into a second phase with its own plan. A smaller go-live that holds builds confidence. A full go-live that breaks in the first month burns through whatever confidence was left.
Change the partner, or change how you work with them?
Switching partners mid-project is expensive. The new team has to learn what the old one built, and that takes months you may not have. So be sure the partner is the problem before you replace them.
Keep them if the trouble comes from unclear ownership on your side, scope that kept growing, or decisions that took weeks to make. Fix those first. Replace them if the senior people promised in the pitch never showed up, if the same mistakes come back after you've raised them, or if you no longer believe their status reports.
If you do bring someone new in, start with a fixed-scope assessment, not a long contract. Within a few weeks you'll know whether they can see what went wrong.
What a good rescue team brings
The people who rescue SAP projects well have usually watched a few fail. They read a project plan and know which line will slip. They make decisions in the room instead of sending them back to head office. And they tell you the uncomfortable thing early, because a week of honesty now costs less than a month of rework later.
Sync has delivered more than 50 SAP projects, including some that other providers walked away from. Sync's leadership is in the first conversation, and the people who scope a rescue are the ones who make the calls on it. Fewer layers between the problem and the person who can fix it is what gets a project moving again.
Your next two weeks
- Freeze new scope. Nothing gets added until you know where you stand.
- Get an independent review of scope, data, testing and who makes decisions.
- Make the trade-off: less on time, or everything later.
- Decide on the partner based on the review, not on frustration.
- Tell the business the real plan. People cope with a hard truth better than with a third delay.
If your project is in this place now, Sync's founders can look at where it stands with you before you commit to anything. Book a call with the founders.
