On this page
Giving business units more authority over investment can make decisions more responsive to local customers and operating needs. It also changes the role of the corporate center. Leaders need to decide which controls still serve the enterprise organization and which approvals can move closer to the work.
The distinction becomes important where business units remain dependent on shared systems, specialist teams or funding. A local budget can pay for an initiative without securing the people needed to deliver it. If two units commit the same team to different priorities, greater local authority has created a decision that neither unit can settle alone.
HBR recently highlighted large companies giving business units greater accountability while simplifying corporate management. For portfolio leaders, the task is to make that authority practical across the commitments that still connect the organization.
The center needs to retain the information and decision rights required to manage those connections. Business units can then control their own work within boundaries that reflect the consequences for the wider portfolio.
Authority should follow the consequences of a decision
The starting point is the business result. A local owner needs authority over the operational changes and adoption required to achieve the benefits an initiative promises. Giving that owner accountability while retaining routine delivery decisions at the center creates an avoidable dependency.
Within approved funding and confirmed capacity, the business unit should be able to organize delivery and adjust local priorities. The need for a wider decision arises when a proposed change affects another unit's commitment or exceeds the owner's delegated limits.
A financial threshold alone cannot define that boundary. Work may fit comfortably within a local budget while requiring a platform release or specialist service on which other units also depend.
The approval therefore needs to distinguish money available from capacity agreed. Where a shared commitment is involved, the owner needs confirmation from the team or service responsible before treating the schedule as approved.
That principle also clarifies escalation. A routine local change can stay local. A change with cross-unit consequences needs a route to a person or forum authorized to decide between the competing interests. The threshold concerns the effect of the decision as well as its financial size. For further reading on this subject see Rethinking approvals: How guardrails enhance agility in enterprise organizations.
Where a decision sits depends on what it affects
-
Business unit ownerDecides locallyOrganizing delivery and adjusting local priorities, within approved funding and confirmed capacity.
-
Shared team or serviceConfirms firstWork that depends on a platform release or specialist service other units also rely on. The owner needs this confirmation before treating the schedule as approved.
-
Authorized executive or forumDecides across unitsChanges that affect another unit's commitment or exceed the owner's delegated limits.
A budget threshold alone cannot draw these lines. Work can fit a local budget and still need a shared team's capacity.
Local control needs comparable portfolio information
The executive committee still needs to compare investments across business units. Local authority does not remove its responsibility for the total commitments the organization can afford and deliver.
That comparison requires a common meaning for the information being reported. Expenditure to date and forecast total cost answer different questions. Delivery status assessed against different baselines can make similar commitments appear to have different levels of risk.
Common requirements should therefore specify the financial measures, approved dates and status criteria used for enterprise portfolio decisions. Benefit reporting needs a named owner and a baseline, with shared benefits counted once. Capacity information needs to distinguish requests from confirmed commitments.
This does not require business units to use identical delivery methods or produce identical local reports. A product team and a regulatory program can manage their work differently while supplying comparable information about expected results, costs and resource needs.
The center should maintain those definitions with finance and the relevant delivery functions. Local owners remain responsible for the accuracy and currency of their submissions. Estimates and missing information should be visible, so an executive comparison does not imply more certainty than the underlying records support. For further reading on this subject see Quick wins to improve data quality across enterprise portfolios.
The common view also needs to include shared expenditure. Business-unit budget ownership can remain intact while finance and the portfolio office consolidate local forecasts and central costs into an enterprise investment assessment.
The center needs authority to resolve competing commitments
Making a conflict visible does not establish who should decide it. The operating model needs to name the authority that can approve a change affecting several business units.
The portfolio office should prepare the options and their consequences. That includes the expected business effect of changing sequence, the dependencies affected and the resources required. The authorized executive or governance forum then makes the trade-off with the relevant business owners involved.
Considering the options together matters. Separate discussions with individual sponsors can produce agreements that seem reasonable locally but cannot both be honored.
A change in enterprise priority need not involve moving individual employees between units. It may require a different sequence of work for a stable team, a change in scope or a revised funding allocation. The delivery assessment should establish which option is workable.
Once the decision is made, the people responsible for affected budgets and team plans need to implement it. A central decision record provides little protection if local owners continue working to incompatible dates. The portfolio office should check that the revised commitments agree across those plans.
Resolving a conflict between business units
- Portfolio officePrepare the optionsThe business effect of each change in sequence, the dependencies affected and the resources required.
- Authorized executive or forumDecide with the business owners togetherSeparate talks with each sponsor can produce agreements that cannot both be honored.
- Owners of affected budgets and teamsChange the plansA new sequence for a stable team, a change in scope or a revised funding allocation.
- Portfolio officeCheck the plans agreeConfirm the revised commitments match across local forecasts and delivery plans.
Test the model before changing the approval rights
An upcoming investment decision provides a practical test of the proposed arrangement. The local owner should be able to establish the funding available, identify shared dependencies and confirm the resources required.
Then examine a change that would delay another unit's approved work. If the decision route is unclear, or neither owner can obtain a binding agreement, the operating model needs to be resolved before authority transfers.
The first portfolio review under the new model should check whether agreed decisions have reached the local financial forecasts and delivery plans. Where they have not, the center has a specific coordination problem to fix. It can address that gap while preserving the local authority the reorganization was intended to create.







