A logistics site manager near Lyon needs to replace a broken forklift. The quote is ready, and the supplier is available within 48 hours. The order must go up to the purchasing department at the Paris headquarters, pass through the budget validation of the CFO, and then come back down with a purchase order.
The result: ten days of downtime on a loading dock, two temporary workers mobilized to compensate, and an indirect cost that far exceeds that of the forklift. Centralization in companies produces this type of situation much more often than we admit.
Related reading : 5 kilos less in 2 months: my method
Response time on the ground: the real cost of a centralized decision
The problem is not centralization itself. It is the gap between the speed at which an operational problem arises and the speed at which the organization can respond. On a production site or in a sales agency, delays are measured in hours. In a centralized circuit, validations are measured in days.
This gap is observed in various subjects such as replacing a failing service provider, adjusting a schedule in response to a peak in activity, or choosing a tool suitable for a local need. As detailed in the analyses of Jeune et Actif, this slowness is not a one-time dysfunction; it is a mechanical consequence of the model.
Related reading : Why choose Empire Business coworking spaces to boost your productivity?
The bottleneck is not always at the top of the hierarchy. It can form at the level of a support service (purchasing, HR, IT) that processes requests from all sites in the order they arrive, without distinguishing urgency. The waiting line becomes the default management mode, and field teams learn to circumvent the system rather than use it.
Centralization of digital tools: when headquarters decides for everyone
A common case illustrates the rigidity of the model: the IT department selects a single project management software for the entire group. The tool suits the headquarters teams, who participated in the specifications. The field teams, however, discover software that does not match their processes or their business vocabulary.
Feedback varies on this point, but it is regularly observed that teams end up managing their actual work in parallel, using spreadsheets or messaging apps. The centralized tool remains filled out by obligation, with incomplete or delayed data entry. Management thinks it is steering the activity through a unified dashboard. In practice, this dashboard reflects an administrative version of reality, not the operational reality.
What standardization costs
Standardizing tools and processes has an invisible cost: the loss of local adaptation skills. When a team no longer has the right to choose how it organizes its work, it gradually loses its ability to solve problems independently. Frontline managers become administrative relays rather than decision-makers.
This erosion produces three concrete effects:
- Experienced employees, accustomed to autonomy, leave the organization or disengage. Turnover increases in field positions.
- Newcomers immediately adopt a dependency reflex on headquarters. Any local initiative goes through a formal request.
- Operational innovation disappears. Process improvements come exclusively from headquarters, often disconnected from field constraints.
Centralization and AI adoption: a structural brake
Recent studies by Gartner and Deloitte on organization in the face of generative AI highlight a paradox. Companies that strictly centralize AI governance at headquarters notice an underutilization of business use cases. Operational teams, who know the daily irritants, do not have the latitude to test solutions suited to their context.
In contrast, organizations that decentralize the ability to experiment achieve faster diffusion of productivity gains. Headquarters sets a framework (data security, compliance, budget) but allows business units to identify and validate their own uses.
This observation goes beyond AI. It applies to all technological transformations. A centralized deployment produces a uniform tool. A deployment that allows space for teams produces a tool that is used.
Subsidiarity in companies: delegating decision-making to the right level
The principle of subsidiarity proposes a simple rule: each decision is made at the level closest to its execution. Headquarters retains what pertains to strategy, regulatory compliance, and overall budget allocation. Everything else goes down.
In practical terms, this means defining clear thresholds:
- Below a certain amount, the site manager alone validates a purchase or replacement of equipment.
- Choices of operational tools (business software, scheduling organization) remain in the hands of the teams, within a technical framework defined by IT.
- Common HR decisions (overtime, temporary reorganization of a team) fall under the local manager.
This division does not eliminate control. It shifts it to a post-facto monitoring, through shared indicators, rather than to a prior validation that blocks the flow.
What changes for headquarters
The role of headquarters evolves: it shifts from validator to architect of the rules of the game. It sets the limits, provides reporting tools, and intervenes only when a threshold is crossed or a systemic risk arises. Headquarters gains strategic capacity what it loses in operational control.
Companies that have initiated this transition after the health crisis, according to observations by McKinsey and BCG, notice a reduction in decision-making times and an increase in engagement from field teams. The model is not without risk (disparity of practices between sites, increased need for coordination), but it responds to a reality that strict centralization refuses to acknowledge: growing organizations cannot funnel everything through a single point.