CaseKit

Operations & Cost Reduction

Diagnosing a cost problem is not the same as cutting costs. One is analysis. The other is guessing.

Cost & turnaround

Operations and cost reduction cases reward a specific kind of thinking: structured decomposition of where money is going, why it’s going there, and what can realistically be done about it. Candidates who jump to “headcount cuts” or “outsource everything” without diagnosing the root cause fail these cases even when their recommendations are directionally right.

If you’ve never done a case interview before, start here.

Imagine your family runs three ice cream shops around town. Business is fine (people are still buying cones), but profits have quietly gotten tighter over the past couple years, and nobody’s totally sure why. Your uncle’s instinct is: “let’s just cut everyone’s budget by 10% and see what happens.”

Stop and notice why that’s a bad idea, even though it sounds decisive. A 10% across-the-board cut treats the cost of waffle cones and the cost of the walk-in freezer repair as if they’re the same kind of problem. They’re not. One is a supply cost you might be able to negotiate down. The other is a fixed cost you can’t shrink without breaking the shop. Cutting both by the same 10% either barely touches the real problem or breaks something essential (often both at once).

What you actually need to do is boring but powerful: go find out where the money is actually going, and why that specific category is growing. Maybe it turns out each of the three shops orders its ice cream mix from a different supplier, at three different prices, because nobody ever combined the orders. Maybe one shop has a walk-in freezer old enough that it’s costing a fortune in electricity. Maybe each shop has its own person doing the books by hand, three times over, for identical paperwork. Each of those has a completely different fix, and none of them get found by a flat 10% cut.

DIAGNOSE PRESCRIBE
Never the other way around

That’s the entire discipline this framework exists to build: separate diagnosis from prescription. Find out specifically what’s driving the cost increase before you recommend anything. The fix only makes sense once you know the actual cause.

Operations cases come in several forms, but the underlying question is always: why is this company operationally inefficient, and how do you fix it?

Classic operations / cost prompts

  • “Our manufacturing costs are 22% above the industry benchmark. Where should we look?”
  • “The company needs to reduce operating expenses by $100M without affecting customer experience.”
  • “Margins have compressed even though revenue is growing. What’s wrong with the operations?”
  • “This distribution network is too expensive. How do you redesign it?”

These cases also appear as turnaround situations: a company is burning cash and needs to stabilize fast. Same framework, higher urgency.

This is one of the most common points of confusion for beginners, because both frameworks touch costs. Here’s the actual distinction, and it matters for picking the right one under time pressure:

Profitability
Wide but shallow

Asks “why did profit change: is it revenue, costs, or both?” Covers the entire P&L, but when it reaches costs it stops at a fairly high-level split (fixed vs. variable). Reach for it when you don’t yet know where the problem lives.

vs.
Operations & Cost Reduction
Narrow but deep

Asks “given that costs are the problem, which specific function is driving it, and what operationally can be done about it?” Covers only the cost side but goes much deeper, by business function (procurement, production, labor, overhead) instead of by financial category.

A simple rule for picking between them

  • Prompt is open-ended (“profit is down, why?”) → start with Profitability.
  • Prompt already frames it as a cost problem (“cut $100M,” “costs are 22% above benchmark,” “why are operations inefficient?”) → go straight to Operations.
  • You started with Profitability and it pointed you toward “the issue is fixed costs, specifically G&A” → switch into Operations and go one level deeper into why G&A specifically is bloated.

A useful mental image: Profitability is the wide first pass across the whole P&L that tells you which side of the ledger has the problem. Operations is the zoomed-in toolkit for once you’re already inside the cost side and need to get granular about which function is actually broken, and how to fix it. The CareNetwork worked example below is a case where Profitability would have told you “it’s a cost problem” in about thirty seconds. The real work, and the real interview, happens once you’re inside Operations.

Same discipline as every framework in this guide: the order isn’t arbitrary, and skipping a step is exactly how beginners end up recommending a fix that solves the wrong problem.

Step 1 Understand the cost base before touching anything

Before you can diagnose why costs are high, you need a map of where the money actually goes. This step alone often reveals more than people expect. A cost line that’s 40% of the total and growing fast is a very different priority than one that’s 3% of the total and flat.

  • What are the major cost categories, as a percentage of revenue?
  • What’s the fixed vs. variable split?
  • Are costs growing faster than revenue? (If revenue is flat and a cost category is up 30%, that category is your prime suspect.)
  • How does this compare to industry benchmarks: are we structurally out of line, or just tight this year?

Step 2 Diagnose by function, not by vibe

This is the step that separates real analysis from a guess. “Costs are too high” is not a diagnosis. It’s a symptom. You need to trace the symptom to a specific function, because each function fails for different, specific reasons:

  • Procurement / Supply Chain: are input costs too high versus peers? How concentrated are suppliers, and are contracts spot-priced or fixed? Is there waste, spoilage, or excess inventory sitting around?
  • Production / Operations: is capacity actually being used, or are expensive assets sitting idle? How do throughput and cycle time compare to industry norms? Are defect rates or rework quietly eating margin?
  • Labor: how does revenue per employee compare to peers? Is overtime or temp labor being overused? Are there too many layers of management for the size of the org? Are expensive, skilled people doing low-value work that a cheaper role could handle?
  • Overhead / G&A: how large are corporate HQ costs relative to revenue? Are functions like finance, HR, or IT duplicated across business units that could share one team instead of running several?

Notice the ice cream shop example already hit three of these four without even trying: procurement (separate suppliers, no combined buying power), production (an inefficient old freezer), and overhead (three duplicate bookkeeping setups).

Step 3 Recommend solutions by time horizon, not all at once

Only once you know which function is actually driving the cost problem do you get to propose fixes. And even then, not everything happens at the same speed. A recommendation that ignores timeline is a wish list, not a plan.

  • Short-term (0–6 months): freeze discretionary hiring, renegotiate existing contracts, cut clearly discretionary spend.
  • Medium-term (6–18 months): process redesign, outsourcing, automation.
  • Long-term (18 months+): facility consolidation, vertical integration, structural restructuring.

Putting it together

Toggle each stage to expand it. The order matters more than the labels.

1. UNDERSTAND THE COST BASE ├── What are the major cost categories (as % of revenue)? ├── Fixed vs. variable split ├── Cost trend: are costs growing faster than revenue? └── Benchmark: how do we compare to industry peers? Goal: find the buckets that are big, growing fast, or out of line with peers. Those are your suspects.
2. DIAGNOSE BY FUNCTION Procurement / Supply Chain ├── Input costs too high vs. peers? ├── Supplier concentration, contract terms, spot vs. fixed └── Inventory carrying costs, waste, spoilage Production / Operations ├── Capacity utilization: are assets fully used? ├── Throughput & cycle time vs. industry ├── Defect rates, rework, quality costs └── Automation opportunity Labor ├── Revenue per employee vs. peers ├── Overtime rates, temp-labor usage ├── Span of control (too many managers?) └── Skills mismatch (expensive people, low-value tasks) Overhead / G&A ├── Corporate HQ costs vs. revenue ├── Middle-management layers └── Duplicated functions across business units
3. RECOMMEND BY TIME HORIZON Short-term (0–6 months) └── Freeze hiring, renegotiate contracts, cut discretionary spend Medium-term (6–18 months) └── Process redesign, outsourcing, automation Long-term (18 months +) └── Facility consolidation, vertical integration, structural restructuring

Separate diagnosis from prescription. Don’t recommend solutions until you understand which cost bucket is the actual problem. The root cause determines the intervention, and two problems that look identical on the surface (“costs are up”) can have completely different fixes underneath.

Core disciplines: tap a card to flip

01
Diagnose before you prescribe
Flip

Name the cost bucket, the dollar gap, and the root cause before you suggest anything. A fix without a diagnosis is just a guess that happened to sound decisive.

02
Benchmark, don't eyeball
Flip

Compare each category to peers as a % of revenue. The biggest gaps versus benchmark, not the biggest absolute numbers, are where the recoverable savings hide.

03
Chase growth, not just size
Flip

A line growing 40% while volume grows 7% is the smoking gun. Cost growth that outpaces the business points straight at structural inefficiency.

04
Sequence by speed & risk
Flip

Capture quick, low-risk wins now; start the big, slow levers in parallel. Time horizon is part of the recommendation, not an afterthought.

Reading the framework is one thing. Hearing it applied out loud is what makes it click.

Interviewer
“Our client, a regional hospital system, has seen operating costs grow 21% over three years while patient volume grew only 7%. The board wants $120M in annual savings without cutting clinical staff. Where would you start?”
Candidate
“Before I recommend anything, I’d want to break down the cost base by category, since a 21% increase against 7% volume growth tells me there’s a real problem, but not yet where it lives. I’d want to see which categories grew fastest relative to revenue and volume, and compare those to industry benchmarks. That’s usually where the real diagnosis starts.”
Interviewer
“Good instinct. Medical supplies grew 31% and administrative costs grew 42%, both well ahead of the 7% volume growth. What would you want to know next?”
Candidate
“I’d want to understand the root cause behind each, since they’re probably different problems. For supplies, I’d ask whether purchasing is centralized across the hospital system or handled separately by each location. Decentralized procurement is a classic driver of inflated supply costs. For administrative costs growing that much faster than volume, I’d suspect duplicated back-office functions across locations, and I’d want to check whether each hospital runs its own finance, HR, and IT team instead of sharing one.”
Notice the candidate never says the word “recommend” until they’ve traced each cost spike to a specific structural cause. That’s the entire skill this framework is built to train.

Your client is CareNetwork, a regional hospital system operating 6 hospitals across the Mid-Atlantic United States. Total operating costs are $1.4B. Over the past three years, operating costs have grown 17% while patient volume grew only 7%. The CFO has been tasked by the board to find $120M in annual cost savings without reducing clinical staff levels or patient care quality. You’ve been brought in to help. How do you approach it?

Step 1 Understand the cost base

CategoryAnnual cost% of total3-yr growth
Clinical labor (protected)$812M58%+9%
Medical supplies & equipment$308M22%+31%
Facilities & utilities$168M12%+18%
G&A / administrative$112M8%+42%
Total$1.4B100%+21%

Clinical labor is protected, leaving $588M as the addressable cost base. A $120M reduction is 20.4% of that base: ambitious, but achievable if the right drivers are identified. G&A grew 42% and medical supplies grew 31%, both far outpacing the 7% volume growth. These are the two smoking guns.

Step 2 Diagnose by function

Medical Supplies & Equipment ($308M, grew 31%)

Each of the 6 hospitals manages its own procurement independently: separate teams, separate contracts, sometimes separate preferred vendors. This is the root cause: decentralized procurement eliminates any economies of scale. Peer systems using a Group Purchasing Organization (GPO) or centralized procurement pay 18–24% less for equivalent supplies. Estimated savings: $55–75M annually, the single largest opportunity.

Facilities & Utilities ($168M, grew 18%)

Utilization data shows two of the six hospitals running at 48% and 52% occupancy, well below the 65–70% industry standard, both within 30 miles of the two highest-utilization facilities. Converting one under-utilized facility to a satellite urgent care model reduces maintenance, staffing overhead, and utility costs. Estimated savings: $22–28M annually.

G&A / Administrative ($112M, grew 42%)

Each hospital runs its own finance, HR, IT support, and billing team, roughly 6 instances of each back-office function. Peer systems of similar size run G&A at 5–6% of revenue; CareNetwork is at 8%. Centralizing into a shared services center is the structural fix. Estimated savings: $25–30M annually, entirely from redundant non-clinical roles.

Now size each lever. Drag the sliders and watch whether you hit the $120M target while staying inside the addressable base.

Addressable base: $588M (clinical labor’s $812M is protected). Board target: $120M. Build a plan that gets there.

Centralized procurement / GPO · biggest lever$65M
Shared services (consolidate G&A)$27M
Facility consolidation$25M
Quick wins (hiring freeze + discretionary)$5M
Total annual savings
~$122M
Procurement / GPO$65M
Shared services$27M
Facility consolidation$25M
Quick wins$5M
% of addressable base20.7%
Hits target, no clinical cuts
  • Total of $122M, meets the $120M board target
  • Procurement / GPO is your biggest lever, correct prioritization
  • 20.7% of the $588M addressable base, ambitious but achievable

Step 3 Recommendations by time horizon

Short-term (0–6 months)

  • Freeze non-clinical hiring (~$4M).
  • Join a GPO and renegotiate the top 20 supply contracts, which represent ~60% of supply spend. Savings begin within 4 months.

Medium-term (6–18 months)

  • Fully centralize procurement across all 6 hospitals with one central VP of Supply Chain.
  • Begin shared services buildout for finance and HR.

Long-term (12–24 months)

  • Convert the lowest-utilization hospital to a focused urgent care + outpatient surgery model.
  • Consolidate 3 separate EHR/IT systems onto one platform.
InitiativeAnnual savings
Centralized procurement / GPO$65M
Shared services (G&A)$27M
Facility consolidation$25M
Misc. quick wins$5M
Total$122M

Target of $120M is achievable. No clinical staff reduced.

Root-cause fix beats blanket cut

Southwest Airlines: one aircraft type, dozens of cost lines

Worth knowing because it’s one of the clearest illustrations of “structural fix beats blanket cut” in business history: Southwest Airlines built one of the most durable cost advantages in the airline industry around a single structural decision, flying only one aircraft type (the Boeing 737) across its entire fleet. That one choice touched almost every cost category at once: pilots only need training and certification for one aircraft, mechanics only need to stock and learn one set of spare parts, maintenance crews don’t need specialized skills for multiple plane types, and scheduling gets dramatically simpler because any pilot or plane can cover any route.

Legacy competitors flying five or six different aircraft types paid for that complexity in every one of those categories simultaneously: separate training pipelines, separate parts inventories, separate maintenance certifications. No layoffs required to capture that advantage. It came from a structural decision that eliminated duplicated cost drivers at the root, the same logic CareNetwork used with centralized procurement above.

That’s the difference this framework is built to teach: a fix aimed at the actual cause tends to pay off across multiple cost lines at once, while a fix aimed at the symptom (just cut spending everywhere) rarely does.

Mistake 1: Recommending across-the-board cuts

“Cut all costs by 10%” sounds decisive, but it’s operationally naive. It’s the exact move your uncle wanted to make with the ice cream shops. It treats a $50M marketing budget and a $50M clinical supply budget as equivalent targets, which they aren’t; one is discretionary, one is regulated and quality-critical. The point of this framework is to identify where the excess is, why it exists, and what can specifically be done about it. Across-the-board cuts skip all three steps.

Mistake 2: Ignoring implementation risk

Cost reduction plans that are clean on paper often run into friction in practice: union contracts that limit headcount changes, vendor lock-in from existing contracts, technology dependencies that make consolidation take 2 years instead of 6 months, and cultural resistance to centralization in decentralized organizations. A strong operations recommendation includes not just what to do but what could slow it down, and how to sequence around those obstacles. Candidates who skip this look like they’ve never actually been inside an organization.

01

The logistics company 24% above the cost-per-delivery benchmark

A last-mile carrier's cost per delivery sits 24% above the industry average. Resist the urge to cut drivers. Decompose the cost structure (fuel/fleet, labor productivity, route efficiency, overhead allocation), benchmark each against peers, and find the line driving the gap before you prescribe a thing.

How to crack it
1
The 24% gap says what, not where

It signals a problem, not its location. Resist cutting drivers. That’s the conclusion of an analysis, never the starting point.

2
Decompose cost-per-delivery

Four buckets: labor (wages, overtime, benefits %), fuel & fleet (cost per mile, vehicle age, idle time), routing & tech (stops per route, failed-delivery rate), overhead (management layers per driver, depot, maintenance).

3
Benchmark each line vs. peers

12 stops per shift against an industry 16 is a productivity problem, not a headcount one. Fix route density and scheduling, not people.

4
Check the fleet

An average vehicle age of 8 years vs. a peer’s 4 drives higher fuel and maintenance cost. The fix is a capital plan, not operational cuts.

5
Don’t miss failed deliveries

A 12% failure rate means re-delivering ~1 in 8 packages, quietly inflating per-delivery cost. Delivery confirmation and proactive rescheduling fix it faster and cheaper than any headcount change.

Where you land

Find the line actually driving the gap, quantify it, then prescribe the specific intervention for that specific driver, not across-the-board cuts.

02

The manufacturer that must cut $80M

Three initiatives are on the table: automation ($50M, 18 months), supplier renegotiation ($25M, 3 months), and a discretionary freeze ($8M, immediate). Sequence them. Capture the quick, low-risk wins now, start the slow-but-large lever in parallel, and explain why doing everything at once would strain the organization.

How to crack it
1
Spend freeze: now

$8M at near-zero execution cost and risk. It takes one decision and one communication; capture it immediately.

2
Supplier renegotiation: in parallel

$25M over 3 months, high-ROI, no capital. Prioritize the top 5–10 suppliers by spend, they’re 60–70% of the savings. With the freeze, that’s $33M in the first quarter.

3
Start planning automation now, not later

The mistake is treating the 18-month timeline as a reason to defer. Vendor selection and capital approval alone take 3–6 months; waiting pushes the $50M out 6+ extra months.

4
Why not everything at once

Freeze and renegotiation are low-bandwidth. Automation needs deep engineering, ops and finance engagement. Launching it alongside a major renegotiation strains the teams who must be present in both.

Where you land

Capture quick wins immediately, plan the heavy lift in parallel, and start automation execution around Month 2 once the quick wins stabilize.

Try it yourself first. Talk through your full structure out loud before you click to reveal the answers below. That’s where the real reps happen.
Q1A logistics company's cost per delivery is 24% above the industry average. You've been asked to diagnose the problem. What's your first move?
A Recommend cutting driver headcount
B Benchmark major cost categories against industry peers to identify the largest gaps
C Suggest outsourcing the delivery function entirely
D Analyze the company's pricing strategy
Answer: B. Diagnose before you prescribe. A 24% gap versus peers tells you there's a problem but not where it lives. The first move is decomposing the cost structure by category and comparing each to industry benchmarks. The gap might be in fuel/fleet costs, labor productivity, route efficiency, or overhead, and each has a different intervention. Recommending headcount cuts (A) or outsourcing (C) before diagnosing is guessing.
Q2You identify that a company's G&A costs are 11% of revenue versus an industry benchmark of 6%. The company operates 8 regional offices, each with its own finance, HR, and IT team. What's the most likely root cause and recommendation?
A The company is overpaying its administrative staff
B Decentralized structure is creating duplicated functions; consolidating into a shared services center would close most of the gap
C The company needs to reduce its office footprint
D G&A is not the right focus, variable costs should be addressed first
Answer: B. 8 instances of the same back-office function is a classic duplication problem, the ice cream shop's tripled bookkeeping, at enterprise scale. A shared services model runs one centralized finance/HR/IT function for all 8 units instead of 8 separate ones, typically eliminating 40–60% of redundant headcount while improving quality through specialization. Reducing office footprint (C) might be a secondary benefit but isn't the root cause. D ignores the data that told you G&A is the problem.
Q3A manufacturer needs to cut costs by $80M. You've identified three initiatives: Process automation ($50M savings, 18 months to implement), Supplier renegotiation ($25M savings, 3 months), and Discretionary spend freeze ($8M, immediate). How do you sequence them?
A Start with automation, it's the biggest lever
B Start with the spend freeze and supplier renegotiation for immediate impact, begin automation planning in parallel
C Start with supplier renegotiation only and evaluate results before proceeding
D Implement all three simultaneously to hit the target faster
Answer: B. This is a sequencing question. The spend freeze and supplier renegotiation deliver $33M quickly with low execution risk, so they should start immediately. Automation is the largest lever but takes 18 months, so planning and procurement begin now even though savings land later. Doing everything simultaneously (D) strains management bandwidth and increases execution risk. Waiting on results before the next step (C) is too slow. Starting with the longest initiative first (A) ignores the quick wins.
Q4A candidate proposes $90M in savings from “consolidating IT systems across the company” as their single biggest recommendation, to be fully realized within 6 months. What's the most important thing missing from this recommendation?
A The dollar figure is too small to matter
B IT consolidation should never be a cost-saving initiative
C No consideration of implementation risk or realistic timeline. Large-scale system consolidations typically take well over a year and face real technical and organizational friction
D The recommendation should focus on labor costs instead
Answer: C. A number without a realistic timeline is a wish, not a plan. Large IT consolidations involve data migration, integration testing, staff retraining, and often vendor contract constraints. Six months is rarely realistic for a change of this scale. A strong recommendation would phase this initiative into the medium- or long-term horizon and flag the specific risks that could slow it down, exactly as the framework's third step requires.

Ready to put this into practice?

Reading the framework gets you halfway. The other half is reps: practice cases that build the muscle memory interviews demand.

Start practicing