Divisions can bring decisions closer to a product, market or business model. They can also duplicate capabilities, compete for the same customers and create internal negotiations over shared resources.
A divisional structure creates value when the scope of accountability is coherent and the corporate center has a clear reason to intervene.
Define what makes a division a business
A division needs a meaningful customer or market scope and sufficient influence over the activities that determine its performance.
A profit target alone does not create business accountability. If product decisions, pricing, capacity and service are controlled elsewhere, the division may be held responsible for results it cannot manage.
Specify the division’s authority and the important dependencies it shares with other units. Make the boundaries understandable to customers as well as employees.
Match coordination to the relationship between businesses
- Related businesses may benefit from shared platforms, brands, procurement or technical knowledge. Cooperation then needs explicit ownership and incentives.
- Strategic business units can group related divisions where coordination is useful within the group but less valuable across the whole portfolio.
- More independent businesses may justify a corporate center focused on capital allocation, leadership and oversight. Even then, common obligations and significant risks still need coordination. Independence is not the absence of governance.
These are design options rather than fixed evolutionary stages. The appropriate arrangement depends on the value the businesses can create together.
Give the corporate center a specific mandate
Corporate activity should provide scale, capability, control or strategic advantage that the divisions cannot achieve as effectively alone.
Define which matters remain corporate: perhaps capital allocation, leadership appointments, enterprise architecture or specific risk policies. Delegate other decisions with clear limits.
Avoid a center that requests detailed operational approval while describing divisions as autonomous. The resulting ambiguity slows decisions and encourages managers to negotiate around the formal design.
Make shared services usable
Shared services can reduce duplication and improve consistency, but only if service scope, demand, capacity and performance are managed.
A hypothetical industrial group centralizes technical documentation. Costs fall initially, but product launches compete in an opaque queue. Divisions create local workarounds and duplicate the capability.
A service agreement should clarify priorities, expected response, required inputs and escalation. Charge mechanisms can help expose consumption, but internal billing does not replace good service management.
Design financial comparisons carefully
Compare divisional results using consistent definitions and explain the effect of shared-cost allocations, internal transactions and centrally controlled decisions.
A division can improve its apparent margin by shifting cost to a shared function without improving the group’s economics. Internal transfer arrangements should support useful behavior and receive the relevant financial and legal review.
Use both business results and contribution to shared capabilities. Incentives tied entirely to local profit can discourage cooperation that the strategy requires.
Review the design through real decisions
Trace a recent product investment, customer conflict and resource allocation across the boundary between corporate center and divisions. Identify where authority was unclear or value was lost.
Ask what would be different if the units were more independent, and what advantage would disappear if coordination were reduced.
A strong divisional model combines local ownership with a corporate center that adds demonstrable value. The design is successful when accountability becomes more meaningful and the business manages its shared dependencies explicitly.