The tension
Every region could defend its own priorities, and no one could see where those priorities overlapped, competed, or depended on one another.
Growth through mergers and acquisitions had left a global consumer goods enterprise with six regions, each running its own planning calendar, project list, funding logic, and way of reporting progress. From inside any one region the work made sense. From the top, overlapping projects, hidden dependencies, and inconsistent approvals made it hard to put money where it would do the most good.
The answer was not to centralize every decision. It was to build one shared backbone that kept the regional freedom worth keeping while making enterprise tradeoffs visible to everyone.
What was happening underneath
Where the system was getting in the way.
Every region made sense on its own
Regional teams could defend their own initiatives with good reasons. What leaders lacked was one place to compare demand, effort, value, and strategic fit across all six.
Funding took different roads
Initiatives moved through regional approval processes with uneven decision rights. Similar work could start in two places without anyone comparing them at the enterprise level.
Dependencies surfaced too late
Infrastructure, analytics, customer, and operational work crossed regional lines. Those connections only became visible after commitments were made, which was too late to sequence the work well.
Reports showed activity, not choices
Each region sent its own updates, and none of them could show what a new investment would push aside. Leaders could not see where resources were stretched or which efforts belonged together.
What Agileon designed
A connected set of operating moves.
The value came from how the parts worked together, not from any one meeting, tool, or template.
Get the decision-makers on the same problem
Focused interviews and leadership workshops brought the tension between global consistency and local flexibility into the open. Leaders agreed on one shared portfolio, joint funding decisions, and clear roles.
Put every initiative on one list
Every significant current and proposed initiative went into one transparent backlog, with its objectives, dependencies, estimated effort, and strategic context. Teams ranked the work together instead of reconciling separate lists after the fact.
Build a forum that actually decides
One cross-functional forum brought together global leaders, regional representatives, and functional experts. Monthly reviews set portfolio direction and budgets, and check-ins every two weeks handled new conflicts and delivery constraints as they came up.
Tie the portfolio to the work itself
Shared tooling connected each portfolio item to the actual work being done. Financial, delivery, dependency, and risk information came together in one review instead of several.
Hand the system to the regions
Regional champions, regular retrospectives, a few simple measures, and standards that could evolve kept the model adapting after launch. Ownership moved out to the regions instead of staying at the center.
Observed outcomes
Movement the organization could see.
These results describe the direction the enterprise moved and the faster approval times it saw. They are not a controlled before-and-after financial study.
Less duplicated work
Projects running in parallel showed up in one portfolio, so teams could combine them and reuse solutions across regions.
Faster decisions
Clear authority and a regular forum cut approval times from months to weeks, and to days for some initiatives.
Money that can move
Financial and operational information could be reviewed side by side, so funds could shift when priorities or expected returns changed.
Freedom with accountability
Regions kept room to experiment for local conditions, and approaches that worked had a visible path to wider use.
What this work teaches
The principles that traveled beyond the engagement.
One list changes the conversation
A shared portfolio made overlap, tradeoffs, and dependencies visible without erasing what made each region different.
A forum needs authority and rhythm
It became useful because the right people could make real tradeoffs on a predictable schedule.
Local freedom works better with shared facts
Regions gained a clearer way to make the case for their priorities and to borrow what worked elsewhere.
Keeping it going is part of the design
Champions, measures, retrospectives, and evolving standards kept the system from hardening into another static process.



