Autonomy still needs management

One of the more useful things I learned from more than 12 months of regional market-management responsibility across different manufacturers is that local autonomy is not the opposite of regional control. The more room a market has to act, the more precise the regional organisation has to be about what remains common, what can be decided locally and what has to come back into the regional management cycle.

I held comparable regional responsibility for longer than the single assignment described here and across more than one manufacturer, which is why I see the underlying management problem as a recurring operating pattern rather than a one-company exception. One of those assignments is documented in enough detail to use as a concrete proof point, and it is worth setting out before drawing the wider management conclusions.

Customer behaviour, dealer economics, regulation, stock position and competitive intensity differ too much for every decision to sit at regional headquarters. Trying to centralise everything would make the portfolio slower and less responsive. The failure mode appears at the other extreme, when markets gain authority but performance definitions, ownership and escalation remain vague. Local teams then act, regional management receives the result later, and the explanation has to be reconstructed after the fact.

The case behind the insight

In the documented case, I was part of the senior team carrying regional market-management responsibility across the complete NSC portfolio of a multi-market automotive organisation. This was an employed operating role inside the business, not an external advisory assignment.

The work began with the organisation, structure, processes and performance of the portfolio, but it did not stop at assessment. The role stayed connected to operational planning and alignment, consultative support and coaching, reporting and management reviews, network management, facilities, processes and inventory. Protecting network profitability was part of the remit because regional decisions on stock, standards or network development eventually land in the dealer economics as well as the NSC P&L.

That combination is important because it explains what “embedded regional management” meant in practice. We were not producing a periodic view of the markets and stepping away. The same operating responsibility remained connected to the issue as it moved from performance visibility into planning, market support, review and execution, which made it possible to see when an apparently local problem was actually being created or reinforced somewhere else in the regional system.

The documented qualitative outcomes were operational rather than rhetorical: lead-time optimisation, inventory reduction and a more balanced stock position, reducing exposure to obsolescence while supporting the broader profitability objective. The three internal quantified outcomes attached to the case remain excluded from this public version.

From reporting to an operating rhythm

The first requirement was a common operational picture. Organisation, structure, processes and performance were assessed across the portfolio alongside detailed market research and operating context. The point was not to force every market into the same explanation. It was to create enough consistency that a regional discussion could distinguish a genuine market difference from a different definition, measurement practice or management response.

That picture only became useful once it was connected to planning and action. Strategic direction had to become operational priorities that a market could actually run, with consultative support and coaching where local teams needed help translating a regional requirement into a workable plan. Reporting and reviews therefore became management routines rather than the output itself: understand the issue, establish the commercial or operating consequence, agree who owns the response and keep the topic connected to implementation.

A dashboard cannot do that on its own. A market issue may be visible locally long before it becomes a regional topic, and once it does, the decision owner may still be unclear or the original operating context already lost. The useful part of regional management is the connection between information, responsibility and action. Without that connection, adding more reporting often improves documentation rather than management.

Why the scope crosses the value chain

Regional market management does not stay inside one function because the issues do not stay there either. Lead time and inventory are an obvious example. Reducing stock without understanding the lead-time consequence can exchange obsolescence risk for availability risk, while carrying too much stock protects short-term availability at the expense of working capital and ageing exposure. Treating inventory as a logistics topic alone misses the commercial consequence.

The same is true in the network. Facility requirements affect the retailer's investment burden. Network-development decisions affect coverage and the economics of the existing dealer base. Process changes can improve regional consistency while making local execution harder if the market conditions behind them are ignored. This is why the role also included network management, facilities, process improvement and the explicit objective of protecting network profitability so the brand remained economically worth representing.

Coaching belonged inside the same operating model. Some market issues need a regional decision; others need a market team to translate regional direction into something that works locally. Staying close to the reviews makes that distinction visible earlier and reduces the temptation to treat communication of a decision as proof that it has been implemented.

The regional layer therefore needs enough common structure for markets to remain visible and comparable without turning that structure into unnecessary central control. The practical work sits at the interfaces: regional standards and local economics, portfolio performance and market context, network expectations and retailer viability.

What the case actually establishes

The documented case above gives us one concrete result set, but it should not be stretched into proof for every management effect discussed here. Its recorded outcomes sit around lead time and inventory; the broader argument comes from repeated first-hand regional responsibility across more than one manufacturer.

The case does not measure whether regional leaders made decisions faster, whether market teams became more consistent or whether the management culture changed. Those are plausible effects of an embedded model, but they are not outcomes I would claim from this record. The defensible point is narrower: regional market management can be carried as an operating function across a portfolio, with the same senior team staying connected from assessment and planning through to market support, reviews and network decisions.

My interpretation from doing the work is that decentralisation becomes more useful when the regional layer is strong enough to preserve visibility without taking the decision back unnecessarily. That is a different objective from centralisation. The question is not how much authority the region can retain, but whether the management system is good enough to let local authority work without losing control of the portfolio.

When the embedded model is worth using

This approach is not necessary in every regional organisation. If markets already work to a comparable performance logic, decision ownership is clear, the regional team has enough capacity to stay close to implementation and recurring issues are being resolved without delay, adding another embedded layer would create cost without fixing a real constraint.

It becomes more relevant when the regional organisation is expected to steer several NSCs but the work between formal reviews is fragmented, when inventory, network or profitability issues repeatedly cross functional boundaries, or when market teams need more than a policy decision to translate regional direction into local execution. The practical test is whether the management system between regional and local authority is strong enough to make both levels work without recreating the same issue at the next review.

That is also why I would not treat regional autonomy as an organisation-chart question. It is an operating-system question. Decision rights matter, but they only work when the performance logic, management routines and escalation path around them are strong enough to make the decision useful.