Approvals That Took Months Started Closing in Weeks

A global consumer goods enterprise with six regions cut approvals from months to weeks, and to days for some initiatives. The speed did not come from pushing approvers. It came from putting authority, evidence, and a steady rhythm into one forum.

03 RANK
The condition

Funding and scope decisions moved through separate regional and global approval paths, and the back-and-forth between them could run for months.

Six regions, six ways to say yes

A global consumer goods enterprise had grown through a decade of acquisitions. Each business it bought kept what it already had: its own technology, its own budget, its own planning calendar, and its own way of approving work. Over time the company settled into six regions plus a global function, and each one ran its own approval cadence.

From inside any one region, that made sense. Regional leaders knew their markets and could move on their own money. The trouble showed up whenever a decision crossed a line. A global executive might approve a budget without understanding what a regional team's project actually needed. A local manager might approve a solution without anyone elsewhere in the company weighing in. Neither was careless. Each was deciding with the part of the picture in front of them.

The company knew it had a consolidation problem. It had tried more than once, over several years, to pull its technology together on its own. Each attempt stalled.

Faster to build than to wait

The earlier attempts had treated the problem as technology that needed to be consolidated. They missed a second cause sitting underneath it. Every region had its own budget and made its own investment decisions. When a region hit a problem, building a local solution was faster than waiting for a global answer, so regions built. Global then had to support several solutions where it had planned for one, and each local decision made the next consolidation attempt harder.

Approvals turned into negotiations. A request that touched more than one region, or depended on global work, had no single place where it could be weighed against everything else competing for the same money. It went back and forth between planning cycles that did not line up. Some of those decisions took months.

Underneath all of it was a structure nobody had chosen on purpose. The budget had become the prioritization system. Whoever controlled a budget controlled its priorities, and nothing required those priorities to be reconciled before the work started. No budget carried the cost of two regions solving the same problem in incompatible ways.

Figure 1
Two ways a decision went wrong
Approved from the center
  • Budget approved globally
  • Regional needs not in view
  • Regions build around it
Approved in the region
  • Solution approved locally
  • No input from other regions
  • Global supports a second fix
Both failures came from the same structure. Each approver decided with the slice of the picture their own budget and calendar showed them.

The decision made in the workshops

We started by interviewing people across the global function and the regional divisions. Three root causes came up again and again. Decision-making was fragmented, because each region had its own planning and approval cadence that often conflicted with enterprise priorities. Prioritization was unclear, because teams had no shared way to separate must-have initiatives from nice-to-have ones. And managers rarely saw anything outside their own domain, so overlapping work stayed invisible.

Then we brought executives, operational leads, and functional managers together in a series of workshops. The central tension came out in the open: global wanted standardization, and the regions needed flexibility. The turning point was when leaders saw these were not two competing models. A single governance structure could hold both.

By the end of those sessions the leaders had committed to three things. Every major initiative would sit in a single backlog. Funding decisions would be made together, so capital followed enterprise-wide impact and regions could pool money for shared problems. And each level of leadership would have a defined role in how decisions got made.

A group of leaders reviewing documents together in a meeting room.

One forum with the authority to decide

The mechanism was a cross-functional governance forum. Its members were global technology leads with oversight of enterprise initiatives, regional representatives empowered to speak for their own markets, and functional experts from design, quality, finance, and other disciplines. It became the one place where new requests were approved, escalations were settled, and priorities were set.

The forum ran on short, frequent meetings instead of large, occasional summits. A monthly review handled high-level prioritization, budget adjustments, and progress against strategy. A checkpoint every two weeks handled what came up in between, such as resource conflicts and shifting requirements. Between meetings, updates went into the shared backlog so every member walked in with current information. When something couldn't wait, like a budget shortfall or a regulatory deadline, teams could call an ad hoc session or escalate straight to the forum leads.

The rule that changed approvals was simple. Every major funding or scope decision came to this group. A regional proposal was checked against enterprise objectives so it would not duplicate existing work. Overlaps and dependencies were sorted out in a neutral room. Technical, finance, and operations people raised feasibility concerns before a project got too far along, not after. Local teams could also bring impediments directly to the people who could remove them.

Figure 2
The forum's working rhythm
HandlesTypical items
Monthly reviewDirection and budgetPriorities, budget shifts, progress
Two-week checkpointWhat changedResource conflicts, new requirements
Ad hoc sessionWhat cannot waitBudget shortfall, regulatory deadline
Short, regular meetings replaced occasional summits, so a request never had to wait long for the people who could decide it.

Weeks, sometimes days, and money that could move

Approvals that had once taken months because of back-and-forth negotiation were now made in weeks, and for some initiatives in days. The difference was immediate feedback and clear authority. A proposal no longer had to travel between calendars looking for someone with the full picture. The people with the full picture were already in the room.

Other things changed too. Duplicate projects dropped sharply once teams could see what else was underway and join forces. Regions began borrowing solutions that had already worked somewhere else. Finance and technology leads reviewed each initiative's forecast return and current spend on a regular schedule, so an underperforming project could be paused, rescoped, or merged instead of running on. Regions kept the freedom to pilot ideas for their own markets, as long as the pilot was recorded in the shared backlog. When a pilot worked, the forum could take it to the rest of the company.

The forum kept adjusting itself. Members tried shorter prioritization cycles, added a few simple measures, and rotated some roles to build leadership depth. None of this was a controlled study, and the gain came as a range rather than an average. The direction was clear, though. The speed came from changing where decisions were made, not from asking anyone to decide faster.

Figure 3
What the approval path produced
MonthsTypical approval time beforeBack-and-forth across separate calendars
WeeksTypical approval time afterOne forum with clear authority
DaysFor some initiativesReported, not averaged
Ranges, not a measured average. Speed came from authority and evidence arriving in the same place.

Approvals slow down where authority is split. Put the people who can say yes, and the facts they need, in the same forum on a schedule, and the waiting goes away.

Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Not sure where to start?

Answer five questions about where work stalls. We send back a starting plan: where to begin and what to look at first.