A German conglomerate operates plants in Poland and Serbia under one COO. Poland is shipping to plan. Serbia is ramping new capacity. The Group Board receives monthly KPIs: aggregate output is tracking, capital spend is within budget, and the portfolio appears sound.
What the board does not see is that Tier 2 ramp-up board visibility manufacturing metrics at the Serbian operation are deteriorating in ways aggregate reporting masks. Labour scarcity is compressing timelines. Customer delivery milestones are sliding. By the time the formal escalation reaches the board, the cost of delay has crystallised.
The Core Problem
This is not incompetence. It is a story about how Tier 2 operational oversight fails when portfolio governance depends on aggregate metrics and board attention concentrates on sites that deliver to plan.
- When Poland performs, the board assumes the rest of the portfolio is tracking.
- When Serbia stalls silently, the plant manager escalates internally but the escalation does not trigger board-level intervention until customer escalation forces the issue.
- By then, cash is already at risk.
Market Context
Serbia’s automotive industry generated €4 billion in exports in 2025, representing 12.3 per cent of total exports. According to the UNDP labour market study, labour demand in Serbia will increase from 125,000 in 2024 to 144,000 in 2026, with manufacturing leading.
The impact manifested acutely in 2025:
1. 12,640 workers in Serbia’s automotive sector were placed on paid leave at 60 per cent compensation longer than legally allowed.
2. This resulted in dismissal of more than 6,000 employees.
3. The effect cascaded into ramp-up delays DACH headquarters never detected until customer delivery penalties arrived.
Decision 1: How Many Sites Can A COO Oversee Without Losing Visibility?
The Structural Accountability Gap
A COO overseeing multiple sites typically manages through quarterly reviews and exception reporting. This works when sites are mature and performing to plan.
It fractures when a COO manages both a delivering site (Poland) and a ramp-up site (Serbia) simultaneously. The delivering site demands optimisation attention. The ramp-up site demands escalation and problem-solving. One person cannot give both sufficient scrutiny.
What Actually Happened
Month 8 of the ramp-up: Serbian operation missed labour recruitment targets.
The Plant Manager flagged it to the COO. The COO understood the risk but did not escalate to the board because aggregate portfolio numbers still looked acceptable, driven by Poland’s solid delivery.
The decision not to escalate was rational under the assumption that a Tier 2 variance could be resolved locally. That assumption was wrong.
Why Board Attention Disappears
The Serbian automotive sector saw revenues rise from €7.2 billion in 2023 to €8.3 billion in 2024, but forecasters warned in January 2026 that 2025 could be significantly weaker due to falling EU demand according to CorD Magazine. That external pressure was already known. What was unknown was that labour scarcity would compress the window for recovery.
Decision 2: At What Variance Threshold Triggers Board Review?
The Aggregate Metrics Trap
Most boards receive portfolio-level KPIs, not site-by-site detail.
- Poland delivers to plan.
- Serbia misses plan.
- Aggregate result: within tolerance.
- Board sees aggregate and assumes both sites are tracking.
The Missing Decision Rule
Few boards have explicitly defined the variance threshold at which a secondary market ramp-up requires board-level intervention. In practice, what constitutes an anomaly is subjective.
- Questions that go unanswered:
- A 5 per cent month-to-month variance in labour hiring?
- A delay in the ramp timeline of one month? Two months?
- Without explicit decision rules, the escalation does not happen until the anomaly becomes a crisis.
Decision 3: Who Escalates Before The Customer Does?
The Skill Displacement Problem
Stránka Stellantis EV conversion at Kragujevac illustrates the problem. The conversion compressed demand for traditional machinists by 12 per cent year-over-year while increasing demand for battery technicians by 34 per cent.
A Plant Manager facing this transition cannot solve it locally. Specialised skills do not exist in sufficient supply. This requires board-level capital reallocation.
Options available to the board:
1. Upskill (expensive and slow).
2. Outsource non-core assembly (margin hit).
3. Extend the ramp timeline (delays cash return).
4. The Plant Manager cannot make this decision. The COO may not escalate it without board authority.
When Customer Escalation Becomes Liability
OEM customers operate on fixed delivery schedules. A slip of two to four weeks is normal variance. A slip of eight to twelve weeks triggers formal escalation and penalty review.
The escalation sequence in the Serbian case:
1. Month 8: Plant Manager should have escalated to the COO when labour targets were missed.
2. Month 10: COO should have escalated to the board, framed as customer delivery risk.
3. Month 12: Customer saw the miss through delayed shipments.
4. Month 13: Customer placed formal claim.
That is how Tier 2 operational oversight failures become customer escalation risk and cash liability.
Why Aggregate KPIs Miss Operational Reality
A board typically tracks portfolio output, capital spend, margin, and cash flow.
- Poland produces 100,000 units to plan.
- Serbia ramps to 35,000 instead of 50,000.
- Aggregate: 135,000 instead of 150,000. Variance: minus 10 per cent.
This variance may fall within tolerance if market headwinds were already factored. What the aggregate does not show is the composition: Poland over-delivering to compensate for Serbia’s structural problem. Poland cannot sustain that for 18 months. When Poland returns to normal run-rate in Month 16, the portfolio collapses.
The Intervention Question
When Board Escalation Finally Comes
In Month 13, the customer formalises a delivery penalty claim. The board faces three options.
1. Invest capital and temporary executive resources to rescue the operation. This requires €15 to €20 million and assumes the labour market and customer patience both hold.
2. Extend the ramp by six months. This delays cash return but reduces monthly wage pressure.
3. Sell or close the operation and consolidate Serbian supply into Poland or Romania.
The board faces a restructuring decision it should have made at Month 10, when variance was internal. The board’s options have narrowed. At Month 13, when the customer has already escalated, any injected leader has less leverage and must work within tighter constraints.
Structural Prevention
Governance Architecture Without Single-Point Failure
The structural problem is not that one COO oversees multiple sites. It is that accountability for ramp-up variance is distributed across multiple roles without clear escalation ownership.
A more robust structure assigns explicit accountability in this sequence:
1. Plant Manager owns site-level performance and is required to escalate to the COO if any leading indicator breaches a defined threshold.
2. COO owns multi-site portfolio performance and must escalate to the Board if a threshold is breached.
3. Board owns portfolio-level variance review and must decide on capital reallocation or scope adjustment within a defined timeframe.
Separating Ramp-Up Oversight From Aggregate Reporting
Most boards receive portfolio-level KPIs quarterly. This is appropriate for mature operations. For ramp-up sites, quarterly is too infrequent.
A more effective governance model mirrors the approach documented in CE Interim, part of Valtus Alliance’s case study on Tier 2 governance gaps in DACH-owned portfolios: portfolio KPIs remain quarterly, but ramp-up sites receive monthly variance review by a designated committee. This committee reviews leading indicators, escalations, and changes to the investment case.
The Serbian case illustrates why this matters. Had a designated committee been tracking ramp-up variance monthly, the labour shortage would have been visible in Month 8. Formal escalation in Month 10 would have given the board time to decide on capital injection, timeline extension, or divestment. The decision would have been made proactively, not reactively.
The Board’s Decision
The immediate question facing this board is whether to commit additional capital to rescue the Serbian ramp-up or to restructure and accept a delayed return. Behind that is a second question: why was this decision deferred until the operation was already in crisis.
The answer is structural. Without explicit decision thresholds, without separate oversight for Tier 2 ramp-up governance, and without clear accountability for escalation, a secondary market problem becomes invisible until customer escalation or cash miss forces board attention.
What is required is deliberate portfolio governance architecture that makes Tier 2 operational oversight visible to the board before a customer needs to escalate it. CE Interim’s experience with multi-country simultaneous portfolio turnarounds shows that early detection and board-level decision-making prevent cascading crisis.
For situations this far advanced, interim executive leadership with specific ramp-up and labour cost management experience often accelerates diagnosis and buys the board time to make a clearer strategic decision. But interim authority cannot substitute for governance. The structural repair must happen before the next investment case is approved and the next secondary market problem emerges.

