Operations Director
Interview Questions 2026

Whether you have a real operating model or just buzzwords. The difference between someone who's run multi-site operations and someone who's read about it.

Framework: "Three layers: (1) Standard operating model — common KPIs, common rituals (daily/weekly/monthly cadence), common methodology (typically lean-based). (2) Local execution — site leaders own delivery against the model, with autonomy on the how. (3) Network learning — best practices identified, codified, deployed across sites via paired-site programmes. The wrong pattern is one-size-fits-all dictation from HQ; the right pattern is common framework + local execution + continuous network learning."

Concrete example: "Inherited 7 sites operating with 7 different KPI sets, no comparable benchmarks. Year 1 standardised on a single operational scorecard (OEE, OTIF, safety, customer NPS, employee engagement) and weekly site reviews. Year 2 introduced cross-site mentoring — best site on OEE paired with worst, knowledge transfer plus targeted CapEx. Network OEE moved from 64% to 79% in 18 months. Total cost-out: €11M annual run-rate."

S: "The order-to-cash process at my previous company had been unchanged for 9 years. 4.2 days end-to-end, 18% touchpoint error rate, customer NPS on fulfilment at 6.4."

T: "I was asked to reduce cycle time by 30% without significant tech investment. Budget €400k, 6 months."

A: "Rather than start with technology, I ran a 2-week value-stream mapping with the operations, sales, and finance teams. Identified that 67% of cycle time was waiting — between approvals, between ERP handoffs, between credit checks. We reorganised approval thresholds (60% of orders could bypass manager approval), pre-calculated credit limits for top 200 customers, and combined order-entry + credit-check into a single role. Tech investment was just a workflow tool, €80k."

R: "Cycle time dropped from 4.2 to 1.8 days. Touchpoint error rate fell to 6%. NPS on fulfilment rose to 8.1. Annual working capital benefit: €6.3M cash freed up. The lesson: process redesign almost always beats technology investment as the first move."

"Three categories of decisions, three different governance models. Standardise: anything where variation creates risk or cost without value — safety standards, financial controls, master data, core ERP processes, regulatory compliance. No local flexibility. Frame: common framework with local execution — KPI structure, operating cadence, performance management methodology. Sites pick the specifics. Decentralise: anything where local context truly matters — customer relationships, hiring decisions, tactical pricing, supplier relationships within network strategy."

Practical insight: "The mistake most operations leaders make is over-standardising customer-facing or relationship-driven activities. The other mistake is under-standardising controls and safety. Get those two categories right and the rest sorts itself out."

"Pragmatism over hype. Most operations automation projects fail because companies start with technology rather than process clarity. My approach: process redesign first, automation second, AI last."

Concrete example: "Led a 3-year operations digital transformation at a €450M industrial business. Phase 1: redesigned 12 core processes to eliminate waste before automating anything. Phase 2: deployed RPA on 23 high-volume transactional processes (invoice matching, master data updates, exception handling) — 45 FTE freed up for value-add work. Phase 3: introduced predictive maintenance on critical assets — unplanned downtime reduced 38%. Phase 4 (current): AI-driven demand sensing for inventory optimisation, currently 9 months in, working but not yet at scale."

Lessons learned: "Buy proven SaaS, build only where you have unique advantage. Predictive maintenance from SAP/IBM/PTC works; building your own predictive maintenance is expensive failure for most companies. AI-driven scheduling is interesting but most companies don't have data quality to support it yet."

"The risk during growth isn't running out of capacity — it's the operational debt that accumulates when you postpone fundamentals. Three priorities I never let slip during growth phases: financial controls discipline, safety standards, talent development pipeline."

Practical playbook: "Capacity planning 12 months ahead, refreshed quarterly. Don't wait for the bottleneck — anticipate it. Build the leadership bench before you need them; promoting unprepared people during growth is how you lose your best operators. Standardise the operating rhythm even as the company grows — daily/weekly/monthly cadence shouldn't drift just because the team is busier."

Example: "At a SaaS company growing 60% year-over-year, I built capacity 6-9 months ahead of demand on customer operations. Felt expensive at the time. Saved us when growth accelerated unexpectedly — never had a service outage during the scaling. The companies that visibly broke during growth had run capacity at 95% utilisation. Lesson: growth is when you need MORE operational discipline, not less."

"Most KPI systems fail for one of three reasons: too many metrics (people focus on nothing), wrong metrics (measuring activity not outcomes), or no consequences (publishing dashboards changes nothing without accountability)."

My framework: "Maximum 5-7 KPIs per leader, balanced across four dimensions — customer (service, quality), commercial (cost, productivity), people (engagement, safety), and continuous improvement (one specific initiative). Each KPI has: a clear definition (no ambiguity in calculation), an owner (one accountable person), a target (with stretch), and a review cadence (weekly for operational, monthly for strategic). Misses get diagnosed; hits get celebrated; nothing gets ignored."

Real example: "On joining one role, the operations function had 87 tracked KPIs. Nobody could tell me which mattered most. I cut to 6 site-level KPIs and 4 network-level KPIs, all linked to bonus. First quarter, three sites failed targets and bonuses were reduced — first time in years there was real consequence. Performance picked up the next quarter because the KPIs finally meant something."

"Neither extreme works — the answer is always hybrid, and the question is which functions sit where. My decision lens: centralise for scale and risk, decentralise for speed and customer proximity."

Typical pattern that works: "Centralised: procurement of common materials, IT infrastructure, financial controls, master data, HR policy framework, safety standards. Decentralised: customer relationships, hiring decisions, local supplier relationships, tactical execution, plant-level continuous improvement. Shared services centre for transactional finance/HR/IT support — economic for scale of 5+ sites."

Common failure modes: "Over-centralising kills customer responsiveness; you lose deals because every decision has to go through HQ. Over-decentralising kills cost and risk control; sites buy 47 different chemical suppliers when 3 would suffice. The judgement is which problems you'd rather have. For most mature businesses, slight bias toward centralisation creates better economics; for early growth or customer-intimate businesses, slight bias toward decentralisation creates better outcomes."

Framework: "Pre-defined crisis playbook: contain first, communicate second, fix third, learn fourth. Customer communication within hours, not days. Executive briefing within the first 24 hours. Root cause investigation by independent team (not the people who caused it). Public post-mortem when warranted."

Real example (STAR): "Major distribution centre suffered a fire on a Sunday night, 35% of European inventory destroyed. By Monday 06:00 I had: activated business continuity to route demand through 3 alternative DCs, called the 50 top customers personally with realistic recovery commitments, briefed insurance and legal, set up daily customer comms for the next 14 days. Built recovery plan with 3 milestones (back to 50% capacity in 2 weeks, 80% in 4 weeks, full in 8 weeks). Hit each milestone, only lost 3 of 50 top customers temporarily, all returned within 6 months. Cost €18M including insurance gap; strategic damage minimised because customer trust was protected by daily honesty."

S: "Inherited a network of 14 sites in Europe. Analysis showed 3 sites contributed less than 4% of revenue and required €12M of capex in 18 months to remain compliant. Restructuring was the right call."

T: "Lead the consolidation: close 2 sites, downscale 1, redirect volume to 4 existing larger sites with capacity. Budget €25M (restructuring costs), 12-month timeline, no service disruption to customers."

A: "Worked closely with HR on consultation processes (German Betriebsrat, Belgian works council). Personally led communication to affected sites — 320 employees. Built capacity at receiving sites 6 months before closure. Outsourced consultancy to placement service for transitioning employees (helped 78% find new roles within 90 days). Customer communication was specific and proactive."

R: "All 3 sites closed on schedule, zero customer service interruption (one missed delivery in 12 months across €450M of moved volume). Annual cost saving €18M against €25M one-time cost — 18-month payback. The piece I'm most proud of is the 78% redeployment rate; companies that handle these moments well preserve culture, those that don't carry the damage for years."

Cover four dimensions: (1) the case for change (financial, competitive, strategic), (2) target operating model design, (3) execution sequencing and governance, (4) people and change management. End with quantified outcomes.

Quick example: "Led an end-to-end supply chain transformation at a €600M consumer goods business. 3-year programme. Restructured from 5 regional supply chains to 1 European supply chain with regional execution. Rebuilt S&OP process. Consolidated 11 distribution centres to 5 strategic hubs. Implemented integrated planning system. Outcomes: working capital reduced €38M, OTIF improved from 87% to 96%, supply chain cost as % of revenue dropped from 8.4% to 6.1%. Total programme cost €22M, payback in 14 months."

"Three buckets, three different approaches. Easy cuts (low risk, fast): SKU rationalisation, supplier consolidation, discretionary spend tightening. Pursue immediately. Structural cuts (medium risk, medium time): organisational restructuring, automation of repetitive work, footprint optimisation. Pursue with care and communication. Strategic cuts (high risk, requires patience): exiting non-strategic businesses, fundamental process re-engineering. Pursue only with executive committee alignment."

The wrong cuts I refuse: "Safety investment, leadership development, customer-facing capacity, system maintenance. Cutting these is borrowing from the future to flatter the present P&L. I've watched two operations leaders take that bargain and pay for it later — quality crises, leadership exodus, customer churn. I won't do it; I'll tell the CFO why and find the same money elsewhere."

"Capacity allocation discipline. I run operations with explicit categories of investment: 60-70% of resources on running the business well today, 20-30% on building tomorrow's capabilities, 5-10% on experimentation. When short-term pressure hits, the temptation is to take 100% from the future categories. I refuse to take more than half. The CFO and CEO sometimes push back; my counter is showing what happens to companies that defer leadership development, automation, or systems renewal for too long."

"Segment suppliers by strategic importance, not just spend. Tier 1 (single-source strategic): annual structured review with named executive sponsors, joint roadmap, mutual KPIs, multi-year deals with structured terms. Tier 2 (significant but multi-source): annual benchmarking, structured RFP every 2-3 years. Tier 3 (transactional): aggregated through procurement, light governance."

Negotiation principles: "Multi-year commitments with escalator caps. Performance-linked terms (SLAs with credits). Right-to-audit and right-to-benchmark clauses. Avoid sole-source arrangements without documented alternatives. Renew 4-6 months early when you still have leverage."

Real result: "Restructured top 30 supplier contracts on joining one role. Total spend €180M. Achieved €14M annual saving (7.7%) without any volume reduction, primarily through multi-year commitments, payment term standardisation, and consolidation of duplicate suppliers."

"Resilience is built before the crisis, not during it. Three pillars: (1) Mapped supply chain (down to tier 3 for critical components — most companies don't have this and discover it during the crisis), (2) Strategic safety stock for genuinely critical items (data-driven, not blanket), (3) Pre-qualified alternative suppliers for top 20 risk categories."

During disruption: "Daily war room for first 2 weeks, weekly cadence after. Customer communication is sacred — never let them be surprised. Internal communication is honest — sales needs to know what they can promise. Document decisions and rationale; this is how organisations learn."

Example: "During the 2024 Red Sea shipping disruption, we lost 18 days on Asia-EU lead times. Because we'd mapped tier 3 supply 6 months earlier, we identified 4 critical components that would deplete within 30 days. Pre-built relationships with European alternatives let us swap supply on those 4 components within 10 days. Zero customer service interruption while competitors were on allocation."

"Inventory is the most expensive insurance most companies buy without thinking. My approach: segment SKUs by demand pattern (runners, repeaters, strangers), service-level commitment by segment (95% for runners, 92% for repeaters, 80% for strangers), and rigorous quarterly review of slow-movers."

Practical results: "On joining one role, inventory was 76 days of cost-of-goods-sold. Bottom 20% of SKUs (by volume) accounted for 41% of total inventory but only 6% of revenue. Phase 1 — aggressive SKU rationalisation, exited 600 unprofitable SKUs over 6 months. Phase 2 — segmented service levels by SKU class. Phase 3 — implemented daily demand sensing. End result: inventory dropped from 76 days to 51 days, €34M working capital released, service levels actually improved because we focused stock on what mattered."

"ESG in operations is increasingly non-negotiable — customers ask, regulators demand, employees expect, capital markets price it. My approach: integrate ESG metrics into operational KPIs rather than treating it as a separate workstream. Energy intensity, waste per unit, water usage, supplier ESG ratings — all on the operational scorecard."

Concrete progress: "At my current company: led the Scope 1 + 2 emissions reduction programme, achieved 28% reduction in 3 years through energy efficiency, on-site solar, and supplier engagement. Now extending to Scope 3 (60% of footprint) with structured supplier engagement programme. Committed to Science-Based Targets initiative validation by 2027."

"Compliance as outcome of culture, not paperwork. Three structural elements: clear standards (one global HSE management system, not 14 site variants), competent local leadership (HSE managers reporting to site leaders for visibility, dotted-line to me for independence), and regular leadership presence on the floor (I personally walk every site quarterly minimum)."

Personal philosophy: "Zero LTI is achievable and I expect it. Near-miss reporting is the leading indicator I watch most carefully — if it's declining, people aren't reporting, which means we're losing the early warning system. Annual independent audit, not just internal. Treat audit findings as gifts, not threats."

"Operational leaders aren't trained in classrooms — they're developed through deliberate exposure. Three mechanisms: (1) Stretch assignments — every high-potential gets one role bigger than they're comfortable with each 18-24 months. (2) Cross-site rotation — moving high-potentials between sites builds breadth and breaks down silos. (3) Real-world problem ownership — give them the difficult project, not the safe one."

Specific: "9-box assessment for direct reports updated annually. Each direct report has identified successor with active development plan. I expect my own role to have 2-3 credible internal candidates within 3 years of my arrival; that's how I measure my own leadership development effectiveness."

"Move with both speed and dignity. Direct conversation about specific performance gaps within first week of identifying the issue. Clear documented expectations and timeline (typically 60-90 days for a senior role). Active support during the period — coaching, mentoring, resource. Honest decision at the end of the period — either back on track or transition out. Dragging it out is unfair to the person, the team, the business."

Example: "Inherited a Plant Manager whose site was the worst performer in the network. Spent 60 days observing before forming a view — he was a strong technical operator who'd been promoted past his leadership capacity. Honest conversation: the role wasn't where he could succeed, but the company valued his technical expertise. Restructured him into a Master Engineering role where he genuinely thrived. Brought in a new Plant Manager. Site moved from worst to top quartile in 18 months. He stayed at the company for years afterwards, in a role that fit. Both outcomes mattered."

"Culture is what gets celebrated and what gets tolerated, repeated daily. As a multi-site Operations Director, you can't be everywhere — so the question is how to make culture visible and consistent without you in the room. Three mechanisms: (1) Common operating rituals (daily/weekly/monthly cadence the same at every site), (2) Recognition systems that celebrate the behaviours you want (safety reports, continuous improvement contributions, customer wins), (3) Leadership presence rhythm — quarterly site visits at minimum, with structured time on the floor not just in meetings."

What I avoid: "Posters, slogans, culture decks. They're noise. Culture is what site managers actually do when nobody's looking. I spend more time observing how site leaders treat front-line operators than reading culture documents."

"Disagree privately, support publicly. If I disagree on an operational decision, I make the case fully in private — with data, with options, with my recommendation. If the CEO decides otherwise on a non-fiduciary matter, I align and execute as if it was my own decision. The rare exception is operational matters with material safety or compliance implications — those I escalate further, but they're genuinely rare."

Specific example: "CEO wanted to push a major capacity expansion 6 months earlier than my plan supported. I built a one-page memo with the specific risks: supplier qualification timeline, regulatory permitting, talent ramp. Showed alternative scenarios. CEO took 2 days, then aligned with my recommended timing. Sometimes you win the disagreement; what matters is you make the case professionally regardless of outcome."

"Treat my peers as customers I genuinely want to win. Operations exists to serve customers — internal and external — and most operational dysfunction traces to weak interfaces with sales (over-promising), finance (gaming budgets), and HR (slow hiring). Structural fixes: shared OKRs with peer functions, joint operating reviews monthly, embedded business partnering."

Practical: "S&OP discipline with sales — same monthly forecast, same accountability for accuracy. Finance partnering at site level — operational finance business partners physically present at major sites. HR partnering on workforce planning 12 months ahead. Most operational problems are interface problems; fix the interfaces and many issues solve themselves."

The question that separates researched candidates from rehearsed ones. Generic answers fail. Specific answers based on actual research succeed.

Structure: "Three specific things drew me — [specific operational situation], [specific strategic moment], [specific element you've researched]. Days 1-30: deep listening — 1:1 with every direct report, top 10 internal stakeholders, site visits to top 5 sites, structured review of operational KPIs, recent incident reports, current project portfolio. Days 31-60: diagnose — operational health assessment across five dimensions: safety, service, cost, people, transformation. Identify quick wins. Days 61-90: point of view — first strategic recommendation to ExCo: where operations should focus the next 18 months, with specific business outcomes. I commit to no major directional change in the first 90 days — that's earning the right to recommend."

Pick a real failure with clear lessons. Avoid: anything you'd hide in a reference check.

Strong answer pattern: "Led a €15M warehouse automation project that ran 18 months late and 60% over budget. Root cause: I trusted the system integrator's timeline without independent technical due diligence. By month 9 it was clear the design was flawed but I kept hoping recovery was possible. Lesson: in major capex projects, kill bad projects fast — sunk cost is sunk. Built independent technical review into all subsequent major investments. The two automation projects I've led since have come in on time and budget."

Don't anchor first if avoidable. Standard reply: "I'd like to understand the role scope, reporting structure, and operational footprint before discussing specific numbers — what range has been approved for this role?"

If you must give a number: Always a range, anchor 15-20% above target. Example: "Based on market data for Operations Director roles at companies of this size and complexity, I'd expect base in the €175k-€205k range, target bonus 25-30%, plus appropriate LTI. The right specific number depends on scope, team size, and any equity components."