Introduction: The Governance Gap in Business Central Programmes
Governance is the most frequently mentioned and least precisely defined term in ERP project delivery. Ask ten Business Central professionals what governance means in the context of their programme, and you will receive ten different answers. Some describe project management processes. Some describe reporting structures. Some reference methodology compliance.
This ambiguity is not merely semantic. When governance is undefined, it is also unenforceable. And when governance is unenforceable, the programme does not operate without governance. It operates with informal governance: unspoken norms, undeclared decision hierarchies, and accountability gaps that accumulate invisibly until a crisis forces them into view.
What Is ERP Governance? A Working Definition
ERP governance, in the context of a Business Central or Dynamics 365 programme, is the set of structures that determine how decisions are made: who has authority, what triggers escalation, how conflicts between competing interests are resolved, and how accountability is maintained as the programme evolves.
Three things governance is not: it is not project management (which handles tasks and timelines), not methodology (which defines how work is done), and not tooling (which enables governance visibility but is not governance itself). Organisations frequently invest in governance tools while leaving governance structures undefined. The result is better-formatted reporting of the same underlying confusion.
Why Governance Determines Programme Outcomes
Governance is the lever that connects strategic intent to programme execution. 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 momentum. Accountability is clear enough that problems surface before they become crises.
Four outcomes are directly determined by governance quality: decision speed, accountability clarity, conflict resolution, and rollout consistency. Slow or absent governance produces decision debt: a growing backlog of unresolved choices that eventually forces a crisis.
The Four Dimensions of ERP Governance
DGP’s Four-Dimension Framework provides a practical structure for evaluating and building governance in ERP and Business Central programmes across four interdependent dimensions.
1. Strategy: Decisions Above the Project Level
Strategic governance concerns the decisions that sit above the programme: the business case, the scope boundaries, and the alignment between ERP objectives and organisational strategy. Most programmes have a formal project sponsor. Fewer have a functioning strategic governance layer with the authority to make and enforce decisions when programme-level conflicts exceed the programme manager’s authority.
2. Governance: Decision Authority and Accountability Structures
This dimension covers the operational governance of the programme: who has authority to make which categories of decision, how the steering committee is constituted and operates, and how accountability is documented as the team evolves. The most common failure here is governance by committee: decision-making structures where authority is distributed across a group with no individual accountability.
3. Delivery: Execution Discipline and Coordination
Delivery governance addresses the structures that maintain quality and consistency in execution: workstream coordination, milestone accountability, scope management, and the feedback loops that surface problems before they compound. In multi-country programmes, delivery governance must additionally address coordination between central delivery teams and country-level implementations.
4. Readiness: Organisational Capacity to Absorb Change
Readiness governance addresses whether the organisation is structurally prepared to receive the system: change management ownership, training and enablement accountability, data preparation discipline, and the organisational readiness of key user groups. Programmes that deliver technically on time frequently underperform on adoption because readiness governance was treated as an operational detail rather than a programme-level responsibility.
Common Governance Failure Patterns in BC Programmes
Governance by Committee (No Individual Accountability)
The steering committee meets monthly. Issues are discussed. Decisions are noted for further review. Project managers are leaving the meeting with no clearer authority than before. This pattern produces the appearance of governance while eliminating its function. Governance by committee diffuses accountability to the point where no one is responsible for anything specific.
Governance That Exists on Paper but Not in Practice
The governance framework is documented. RACI matrix is complete. But in practice, decisions are made in Slack channels and through informal relationships. The formal governance structure is bypassed because it is slower and less trusted than the informal one that has grown around it. This creates a false sense of security while the real decision-making operates without oversight.
Governance That Does Not Scale When the Project Goes International
A governance model that functions well for a single-country implementation will frequently fail when the programme expands. Country leads develop their own interpretations of programme authority. Coordination mechanisms that worked informally require formal structure. The escalation path that was obvious domestically becomes ambiguous across jurisdictions.
How Good Governance Is Built: Five Structural Principles
- Individual accountability at every tier. Every governance tier requires a named individual who is accountable for that tier’s decisions. Committees advise. Individuals decide.
- Explicit decision authority mapping. Each category of decision must be explicitly mapped to a decision owner. Informal authority is the enemy of governance.
- Escalation paths that are trusted and used. Governance that consistently converts escalations into decisions builds trust. Governance that converts escalations into committee discussions destroys it.
- Governance rhythms that match the programme’s pace. Steering committees that meet monthly cannot govern programmes that make daily decisions. Governance structures must be calibrated to the decision frequency required.
- A feedback mechanism that surfaces reality, not reporting. Effective governance includes a mechanism for surfacing the informal reality of the programme alongside the formal one.
Governance in International Programmes: Additional Complexity
When a Business Central programme extends across multiple countries, four additional structures become essential: programme-level authority above the country level; country-level governance charters; cross-country coordination mechanisms; and wave-level governance reviews: formal checkpoints between rollout waves that evaluate whether the governance model is holding.
How DGP Addresses Governance in Practice
In the Strategic Project Assessment, governance is analysed as one of four diagnostic dimensions. The SPA identifies structural governance gaps, misalignment between formal and informal authority structures, and early-warning signals that governance is beginning to fail under programme pressure.
With the International Project Consultancy, DGP provides programme-level governance support for BC partners running complex multi-country rollouts: the coordination mechanisms, escalation paths, and decision authority frameworks that allow individual country rollouts to operate coherently as part of a single programme. Fully independent. Senior-led. Practical and structural. Clarity. Confidence. Control.
