The Execution Vacuum
Automotive organisations can have a clear strategy and still stall because the senior capacity needed to arbitrate across functions, markets and parallel operating models is already fully loaded.
Automotive organisations can have a clear strategy and still struggle to move it through the business because the people who must arbitrate across functions, markets and old and new operating models are already fully loaded.
Cost discipline and flatter structures have reduced spare senior bandwidth across many programmes at the same time that EV industrialisation, cybersecurity, software-update governance, data requirements, new distribution models and legacy portfolios have to be managed in parallel.
The failure mode then looks deceptively strategic. Decisions reopen, programmes pause, local markets improvise and management asks for another refinement of the plan. Often the unresolved issue is more practical: there is not enough integrative capacity at the points where several functions have to make one decision.
Cybersecurity management, software updates, sustainability and data obligations no longer sit outside the operating model as occasional compliance projects. They have recurring owners, evidence requirements, release gates and market consequences.
That work intersects with product, legal, IT, sales, aftersales and local-market execution. The load does not disappear after launch because the vehicle and customer relationship continue to change after delivery.
Governance density therefore behaves like an operating cost and a decision-capacity requirement, not a temporary programme burden.
Legacy ICE and new EV portfolios run together. Dealer networks coexist with agency or direct-sales pilots. Existing software stacks have to support vehicles while new architectures are developed. Markets move at different speeds and cannot all switch on the same date.
The old and new systems therefore overlap for years. Coordination demand often increases after the first launch because exceptions, customer issues and market differences become visible only in operation.
Calling this a transition understates the management requirement. Parallel-run has become part of the operating model.
Cross-functional decisions wait because the relevant senior owners are already carrying full spans of control.
Markets solve immediate customer or regulatory problems locally when the central decision is too slow, creating another integration problem later.
A decision appears settled, then reopens when another function or market surfaces a constraint that was not integrated the first time.
Teams repeat analysis and reporting because the management bottleneck sits above the level at which the work is being produced.
These symptoms can coexist with a sensible strategy. Treating them as proof of strategic confusion can send the organisation back into another planning cycle without changing the capacity constraint.
Additional people can increase throughput. AI can accelerate analysis, documentation, consistency checks and preparation of decisions. Both are useful.
The constrained activity is often different: deciding between competing functional objectives, recognising a pattern across several markets, negotiating an exception, assigning risk and forcing a decision through an organisation that has several valid reasons to hesitate.
That is senior integrative work. It requires context, authority and enough proximity to implementation to see whether the decision actually survived contact with the operation.
Adding permanent management layers can solve part of the problem, but it also adds fixed cost and takes time to integrate. The capacity model therefore needs more than a binary choice between hiring and overloading the existing team.
A more flexible execution layer can work when it is treated as part of governance rather than as extra hands outside it.
- Define which decisions can be delegated to a temporary or variable senior operator and which remain with line management.
- Give the operator access to the same data, meetings and implementation constraints as the internal team.
- Use a small number of operating measures that show whether the constraint is being removed, rather than activity reporting.
- Build repeatable playbooks for the recurring parts of market rollout and parallel-run operations so that senior capacity is spent on the exceptions.
- Keep the work close enough to implementation that ownership does not fall into another handoff.
The objective is not to create a shadow hierarchy. It is to restore enough surge capacity that the permanent organisation can make and implement the decisions it already knows it needs.
External support adds little if it produces another recommendation that line management then has to translate. It becomes useful when a bounded piece of senior work can be inserted into the existing decision system, carry an issue through to implementation and then leave the capability and routine with the organisation.
That is a different role from strategy refresh or programme-office reporting. It is closer to temporary operating capacity around a defined constraint.
The execution vacuum is therefore not an argument for more consulting. It is a reminder that transformation design has to account for the amount and type of senior integration work the operating model can actually absorb.
Written from operating experience, not market commentary.