Nothing in this program was a mistake, and that was exactly the trouble. Each business unit was choosing sensibly for itself, and together those choices were making an enterprise-wide transformation harder than it needed to be. ERP integration governance helped a diversified industrial enterprise align local choices with enterprise needs without removing the autonomy that made its units effective.
Sensible Choices, Costly Sum
The client was a diversified industrial enterprise with several business units, each with its own priorities, customers, and ways of working. An enterprise-wide ERP transformation was underway, and it needed the units to move in ways that fit together.
As enterprise program and governance lead, I found executives who were not up against resistance. They were up against something subtler. Units were making choices about processes, data, and system configuration that were locally sensible and collectively costly. Every decision was defensible, and the sum of them was producing integration friction that nobody had chosen.
A Boundary Nobody Had Drawn
The friction appeared wherever unit-level work had to connect to the enterprise. Integration was harder than it should have been, and the effort to reconcile differences kept growing.
Behind it sat an unanswered question: which decisions belonged to the units and which belonged to the enterprise? Without a line, every unit reasonably assumed its own needs came first. Choices between local fit and enterprise coherence were being made implicitly, one configuration decision at a time, without anyone recognizing them as choices. No forum looked across the units and asked what the pattern of local decisions added up to.
Taking away local judgment was never the answer. The organization needed a way to decide, on purpose, where local judgment should stop and enterprise standards should begin.
ERP Integration Governance Around Decisions and Boundaries
I kept the work centered on decisions and boundaries. Several steps asked something of unit leaders and enterprise leaders alike, and I brought those costs into the conversation instead of smoothing them over.
Sorting decisions, then assigning rights
We opened by sorting decisions into those that could safely remain with a unit and those that affected the enterprise as a whole. It was the single most important move. I facilitated working sessions in which unit leaders and enterprise leaders discussed real examples together, and a shared sense of where the line fell began to form. Units had to accept that some decisions would move upward, and enterprise leaders had to accept that many decisions should stay exactly where they were.
For decisions belonging at the enterprise level, we named who decides, who must be consulted, and how disagreement would be resolved. For decisions that stayed local, we defined the constraints within which units were free to choose. Clear decision rights reduced the number of conversations that had to happen at all, because people knew which ones they were entitled to settle.
Showing what variation costs
I helped leaders view local decisions in aggregate. When a unit proposed a variation, we asked what it would cost the enterprise to support it and what the unit would gain. The tone of the conversation shifted. Instead of unit against enterprise, the question became what the organization was willing to pay for a particular difference.
Unit-level changes were also colliding in time and in dependencies. We set up a lightweight way to coordinate them across units, so leaders could see where changes affected one another. Conflicts surfaced early, and leaders gained a basis for sequencing and for deciding which differences were worth keeping.
A steady forum for deciding together
Finally, I helped establish a regular forum where unit and enterprise leaders could raise issues and decide together. I kept it focused on decisions rather than status, and I stayed close to the stakeholders who found the new boundaries uncomfortable. Their concerns were legitimate, and listening to them improved the boundaries we drew.
Disagreements Reframed as Questions of Cost
Units understood which decisions were theirs and which were not, and enterprise leaders understood the real cost of the variations they were asked to accept. Integration conversations grew more constructive because they were framed as trade-offs instead of disputes. Fewer avoidable differences were introduced, and the ones that remained were chosen deliberately.
Executives noticed how disagreements were handled, too. Before, a dispute between a unit and the enterprise often escalated as a contest of authority. With decision rights agreed in advance, the same disagreements arrived as questions about cost and benefit, and they were resolved faster and with less residue. That shift in tone is easy to overlook, yet it is often what keeps a governance model going.
The units kept their identities and their judgment. Their decisions were simply made with awareness of the enterprise they belonged to.
Four Ideas for Leaders Facing the Same Pattern
- Draw the line between local and enterprise decisions. Without it, every unit will rationally optimize for itself.
- Make decision rights explicit. People settle faster when they know what they are entitled to decide.
- Show the aggregate effect. A choice that looks harmless alone can be costly in combination.
- Treat differences as purchases. Every variation has a price, and leaders should decide on purpose which ones are worth it.
Enterprise change that crosses organizational boundaries tends to follow this pattern, including AI initiatives coordinated across units, which I take up in my enterprise AI consulting and leadership work. For a wider picture of how I help executives govern complex programs, see my approach to enterprise program governance.
Deciding Who Decides What
When sensible decisions in individual units add up to friction at the enterprise level, the first step is settling who decides what. Start a conversation about your own transformation