Regions and the global function were funding similar work, and no shared list showed the overlap until the money was already spent.
Every Region Could Defend Its Own List
A global consumer goods enterprise had grown through a decade of acquisitions across six business regions. Each business it bought kept its own technology, and each region kept its own budget and made its own investment decisions. The global technology group had tried more than once, over several years, to consolidate. Each attempt hit the same wall: a local fix was faster than waiting for a global one, so the regions built, and every local fix made the next consolidation harder.
Inside any one region, the work made sense. What nobody had was a view of what was happening outside their own domain, so overlapping work stayed invisible. The first step was not a new process. It was getting everyone's work onto one surface at the same time.
Thirty Minutes on One Board
We brought application owners, regional leaders, and global representatives together on one call from around the world, with tension that had been building for a long time. The ask was simple: put all quarterly work on a shared digital board. Global initiatives, regional fixes, application roadmaps. If a team was planning it or had committed to it, it went up.
Within thirty minutes the board was covered. Then an application leader who had been scrolling quietly stopped. A regional item was solving the same problem his application team had been working on for two quarters. The regional lead who owned it explained that his team had been building it with a local vendor over the past quarter. Neither side had known about the other.
Nothing had let them know. Each budget ran its own planning process and priority list, and those lists had never been in the same place.
The Argument Was About Structure, Not People
The discovery did not calm the room. The leader responsible for the core applications argued, as he had before, that application work had to come first, because regional work built on an unstable application would not hold. A regional leader answered that his region could not keep waiting on application timelines that had been slipping for eighteen months. His team had found a solution that worked and put it in place. Global, the application side answered, now had to support two solutions instead of one. Voices rose.
Then a leader who had been off camera turned his video on and reframed the exchange. None of this, he said, was any one person's fault. The structure had handed each of them a budget and told them to solve their own problems, and they had. Their solutions did not fit together, and nobody's budget carried the cost of that. Another leader added the other half: regions built around the global strategy because it did not move at the speed their operations required. Both sides were describing a real problem.
The regional lead asked the question that mattered: in his experience, global alignment meant waiting a year and a half for something that did not quite fit, so why would this be different? We were not there, we said, to decide whose priorities were right. From where each of them sat, they were all right. The problem was that each was optimizing the slice of budget they controlled, and decisions made in isolation were creating costs for everyone else on the call. The only way out was to prioritize the full portfolio together, through the same lens.

Ranked From the Whole Company's Seat
Everyone estimated the value and effort of every item on the board, not from a regional view, an application view, or a global strategy view, but from the view of the organization as a whole. As the order emerged, the application leader saw that his work was not at the top. It sat in the top third, and two items ranked above it were regional items that depended on it. If they went ahead first, they would stall. His work had to come first not because it scored highest, but because nothing else could move without it. Priority was not only value and effort. It was also what unlocks what.
By the end, more than five hundred initiatives sat on one board, scored and sorted, a little over half of them global work. The order was not the global list or any regional list. It had not existed when the session began. One of the leaders said that if they had seen this picture at the start of the year, they would not have funded the duplicate work. They would have pooled the money and done it once.
The argument did not end that day, but it moved: from whose priorities mattered most to which made the most sense for all of them together. That was an argument the room could finish.
- 54.5%Global work
- 45.5%Six regions
-
All work on one board Global, regional, and application.
-
Enterprise lens Value and effort Scored from the enterprise's view.
-
What unlocks what Sequence by dependency What unlocks other work goes first.
-
Done once Merge the duplicates Overlapping work combined or reshaped.
-
One ranked list Nobody's list, and everyone's.
One List That Stayed Current
What the session produced in a day, the enterprise made permanent. Leaders committed to a single backlog for every major initiative. Each region gathered its in-progress and proposed projects, with objectives, estimated timelines, and known dependencies. Some of that work had been running for months without anyone outside its home division knowing. Longer-term proposals without formal support went in too, so near-term commitments could be weighed against what was coming.
Regional and global leaders ranked it together on strategic importance, complexity, and expected return. Where several regions were working on similar challenges, such as systems modernization or market expansion, projects were merged or modified. Mapping dependencies changed the sequence too; some analytics work, for example, relied on infrastructure upgrades in another region. A cross-functional forum kept the list current.
Duplicate projects declined sharply. Teams that had not known about each other began sharing initiatives, consolidating vendors, and reusing solutions proven elsewhere, and the money and people freed up went to higher-impact work. This was not a controlled financial study, and no count of merged projects was published. What the enterprise had, for the first time, was one list of its work that every region could see, challenge, and plan against.
- Each budget set its own order
- Overlap found after the spend
- Global supported two solutions
- Dependencies surfaced late
- All major work ranked together
- Duplicates merged or modified
- Work sequenced by dependency
- Overlap visible before the spend
A shared backlog does not erase local judgment. It lets each region see what everyone else is deciding at the same time.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


