Who actually controls your Business Central project when it gets tough?

Governance in a Business Central transformation is a discipline of its own, not a by-product of the project plan. It decides scope, prioritisation and data ownership. Concretely it comes down to three things: clear decision paths, a named target picture, and one person who decides bindingly when goals conflict, for example deadline against data quality against scope. Without the third, the first two have no effect, because nobody resolves the conflict. Otherwise, in BC projects, steering quietly shifts to the implementer, because that is where the detailed knowledge sits. This happens without bad intent; it follows from decisions being made where the knowledge is. The price is control over scope and roadmap. In most projects nobody fills this role at a senior enough level, and that is exactly where the expensive course corrections originate later.

What does governance mean in concrete terms?

Governance is one of those terms that mean a lot and say little. Concretely it comes down to three things: clear decision paths, a named target picture and one person who decides conflicts of goals with authority. If the third is missing, the first two stay ineffective, because then nobody resolves the conflict.

• Governance means: clear decision paths, a defined target state and someone who decides bindingly in conflicts of goals (schedule versus data quality versus scope), not the implementation partner on the side.
• In BC projects, control otherwise drifts quietly to the implementation partner, because that is where the detailed knowledge sits. That costs you control over scope and roadmap.

This shift happens without bad intent. It follows from the fact that decisions are made where the knowledge sits, and detailed knowledge inevitably migrates towards the implementer over the course of the project.

By which artefacts do you recognise governance?

Governance cannot be asserted, only shown through artefacts. Four are enough as a test, and you can inspect all four in one meeting without needing technical detail knowledge.

• Concrete artefacts: a decision log, a backlog prioritised by business value, defined acceptance criteria per module, a data owner per master-data domain.
• Control stays on your side, with Business Central as home: DGP facilitates the decisions, but does not make them for you.
• Senior staffing means: someone who can assess change requests, licensing logic and process compromises before they surface at go-live.

The most telling one is the decision log, and not because it exists but because the rejected alternatives are recorded in it. If you cannot say with confidence who at your company decides the next conflict of goals with authority, let us clarify exactly that in a conversation.