ERP governance after go-live is a small set of standing decisions: who may change the system, how a change is approved and recorded, and when the whole configuration is reviewed. The most valuable thing a programme produces is not the configuration. It is the log of why each decision was taken. Most programmes hand over the system and lose the reasons.
Why does the decision log matter?
Two years after go-live nobody remembers why an approval step exists, why a field is mandatory or why a report is built the way it is. Without the reason, the safe answer is to leave it alone, so every workaround is preserved and every upgrade becomes harder. With the reason recorded, a team can see what still applies and remove what does not.
What goes in the log
- The requirement, in the business owner's words.
- The options considered: standard, configuration, integration or customisation.
- The decision, who took it and the date.
- The cost of ownership that was accepted, including the effect on the next upgrade.
Four standing mechanisms
- A change owner per process. Each end-to-end process has a named business owner who approves changes to it. IT implements; the owner decides.
- A change gate. Requests are logged, assessed against the standard-first rule, and approved or declined in a regular forum. Emergency changes are allowed, and reviewed afterwards.
- Access reviews. Roles and permissions are checked against real jobs on a schedule, and after any organisational change.
- An upgrade calendar. ERP vendors ship new versions on a rhythm and support only recent ones. Plan the next upgrade as a project, with the log telling you which customisations to keep, rebuild or retire.
How do you know governance is working?
Watch for signs that the operation is going around the system: spreadsheets that duplicate a report, approvals done by message, requests waiting for a developer instead of an owner. Track the number of open change requests and how long they wait, and ask each process owner every quarter what the system makes harder than it should be.
Start with one page
If there is no log today, start one. Record the next ten changes properly. Within a year it will be the most consulted document in the programme.