The governance gap in Business Central programmes
Governance is the most frequently used and least precisely defined term in ERP projects. Ask ten Business Central professionals what governance means in their programme and you get ten different answers: project management processes, reporting structures, methodology compliance.
This vagueness is not just a matter of words. If governance is undefined, it is also unenforceable. And if it is unenforceable, the programme does not run without governance but with informal governance: unspoken norms, undeclared decision hierarchies and accountability gaps that build up invisibly until a crisis forces them into the light.
What is ERP governance? A working definition
In the context of a Business Central or Dynamics 365 programme, ERP governance is the sum of the structures that determine how decisions are made: who has the authority, what triggers an escalation, how conflicts between competing interests are resolved and how accountability is maintained as the programme evolves.
Three things governance is not: not project management (which tracks tasks and deadlines), not methodology (which sets how work is done), and not tooling (which makes governance visible but is not governance itself). Often investment goes into governance tools while the structures stay undefined. The result is better-formatted reporting of the same lack of clarity.
Why governance decides the outcome
Governance is the lever that connects strategic intent with delivery. When it works, decisions are made at the right level and at the right time. Conflicts between local and central interests are resolved without destroying the pace. Accountability is clear enough that problems surface before they become a crisis.
Four outcomes depend directly on the quality of governance: decision speed, clarity of accountability, conflict resolution and rollout consistency. Slow or missing governance creates decision debt: a growing backlog of unresolved questions that eventually forces a crisis.
The four dimensions of ERP governance
1. Strategy: decisions above the project level
Strategic governance concerns the decisions above the programme: the business case, the scope boundaries and the alignment of the ERP goals with the corporate strategy. Most programmes have a formal sponsor. Few have a working strategic governance level with the authority to decide when conflicts exceed the project lead's remit.
2. Governance: decision authority and accountability
This dimension covers operational governance: who may make which kind of decision, how the steering committee is staffed and works, and how accountability is documented as the team changes. The most common mistake is governance by committee: decision structures in which authority is spread across a group without any single person being accountable.
3. Delivery: execution discipline and coordination
Delivery governance concerns the structures that keep quality and consistency in execution: workstream coordination, milestone accountability, scope management and the feedback loops that make problems visible before they escalate. In multi-country programmes it must additionally govern the coordination between central teams and the country implementations.
4. Readiness: the organisation's ability to absorb change
Readiness governance clarifies whether the organisation is structurally ready to absorb the system: accountability for change management, training and enablement, data preparation and the readiness of the key-user groups. Programmes that deliver on time technically often fail on adoption, because readiness was treated as an operational detail rather than a programme responsibility.
If governance is undefined, it is also unenforceable. And if it is unenforceable, the programme does not run without governance but with informal governance: unspoken norms, undeclared decision hierarchies and accountability gaps that build up invisibly until a crisis forces them into the light.
Common governance failure patterns in BC programmes
Governance by committee (without individual accountability)
The steering committee meets monthly. Issues are discussed. Decisions are noted for further review. The project lead leaves the meeting with no more authority than before. This pattern creates the appearance of governance while removing its function: accountability is spread so widely that no one is responsible for anything concrete.
Governance that exists on paper but not in practice
The governance model is documented, the RACI matrix complete. In practice, though, decisions are made in chat channels and through informal relationships. The formal structure is bypassed because it is slower and less familiar than the informal one that has grown alongside it. This creates a false sense of security while the real decision-making runs without oversight.
Governance that does not scale internationally
A model that works well for one country often fails as the programme grows. Country leads develop their own interpretations of the programme's authority. Coordination that ran informally needs formal structure. The escalation path that was clear nationally becomes ambiguous across jurisdictions.
How good governance is built: five structural principles
- Individual accountability at every tier. Every governance tier needs a named person accountable for its decisions. Committees advise. Individuals decide.
- Explicit mapping of decision authority. Each category of decision is explicitly mapped to an owner. Informal authority is the enemy of governance.
- Escalation paths that are trusted and used. Governance that reliably converts escalations into decisions builds trust. Governance that turns them into committee discussions destroys it.
- Governance rhythms that match the pace. A committee meeting monthly cannot run a programme that makes daily decisions. The structure must be calibrated to the required decision frequency.
- A mechanism that surfaces reality, not just reporting. Effective governance has a way to surface the informal reality of the programme alongside the formal one.
Governance in international programmes: additional complexity
When a Business Central programme spans several countries, four additional structures become essential: a programme authority above the country level, governance charters per country, mechanisms for cross-country coordination, and governance reviews per rollout wave, that is, formal checkpoints between the waves that check whether the model still holds.
How DGP addresses governance in practice
In the assessment, governance is analysed as one of four diagnostic dimensions. It reveals structural gaps, the misalignment between formal and informal authority, and the early warning signs that governance is starting to tip under pressure.
For complex multi-country rollouts, DGP delivers the programme governance directly: the coordination, the escalation paths and the decision structures that hold individual country rollouts together as part of one programme. Senior-led, practical and structural, with control on your side and Business Central as home.
Structure, before the pressure comes
DGP evaluates governance across four dimensions and gives you a clear, decision-ready picture of what has to change before the programme makes it unavoidable. Let us talk about it.
