International Business Central rollouts rarely fail at go-live. The course is set earlier: with the template, with governance, with the question of which localisations a country really needs. This session shows what has to be settled before the project starts.
The recording is a workshop conversation, not a presentation. Three people who have run international rollouts go through the points where projects tip over in practice, and say for each one how to spot it early.
A template needs an owner
You can take a template into a rollout project. But it has to be finished first: hardened, documented, and it must be clear how you test it. Go into the first country with a half-built template and you will finish building it there, and after that it is the template of that one country.
The most important sentence of the whole hour is organisational, not technical: if nobody owns the template, everybody changes it. Without named ownership you get as many variants as countries, and the advantage of having a template is used up before the second wave begins.
Fehlende Governance ist kein Mangel an Terminen
This is not about missing meetings and not about missing documentation. Missing governance means that decisions have no place to happen. At that point there are committees, but none of them is allowed to decide.
You can hear it in recurring sentences: we need to clear that with head office, let us align that with all countries, we will come back to it. Every single one sounds reasonable. Together they postpone decisions until the implementation makes them instead, uncoordinated and differently in every country.
Localisation is not translation
Localisation does not mean the language of the interface. It is about a clear picture of which localisations are needed in which country and how complex each of them is: tax, legal, document processing, reporting obligations.
If one thing quietly destroys an international project, it is localisations discovered too late. Not wrong development, not bad consultants: unknown requirements that only surface in the country. They move deadlines and the order of the rollout waves with them. If you need three months per country instead of one, you are running a different project from the one that was approved.
Die Arbeit liegt vor dem Kickoff
The session closes with a demand, and it is an uncomfortable one because it sounds like delay: actually work through your own checklist, and do it beforehand. Template, country landscape, localisations, decision paths. That is work you finish before the kickoff, not after it.
The reason is simple. After the kickoff each of these questions costs more than an answer: it also costs correcting whatever was built on the wrong assumption in the meantime.
Chapters of the recording
- 12:51 Governance. How to tell that decisions have no home.
- 16:24 The country landscape. Which country becomes the pilot and what decides the order.
- 22:16 Localisation. Why it has nothing to do with language and what it does to the schedule.
- 28:20 Die Checkliste vor dem Kickoff. What must be settled before the project starts.
If you are right in the middle of it
The points above help most before the start. If your rollout is already running and you recognise several of them, that is no reason to start over. It is a reason to record the country landscape and the decision paths cleanly once, before the next wave begins. That is exactly what we do in a review of where you stand, and it takes days, not months.
