Operations and Capacity Case Interview Framework

Market entry and M&A cases test strategic judgment. Operations cases test systems thinking — the ability to understand how components of a process interact and fail together. When an operations problem also has a profitability dimension, bridging the two with the profitability case framework helps you connect operational inefficiency to its P&L impact.

Think of a supply chain like water flowing through pipes of different widths. The total flow through the system is limited by the narrowest pipe, regardless of how wide all the other pipes are. You can triple the capacity at the source and triple the capacity at the destination, but if there is one narrow pipe in the middle, the system throughput does not improve. Operational improvement is the discipline of finding the narrow pipe, widening it, and then finding the next narrow pipe, which is always somewhere else. This iterative bottleneck identification is what separates genuine operational excellence from well-intentioned but ineffective process projects.

Interviewers use operations cases to test whether you have this systems thinking instinct.

Structure any operations case around three questions: where is the process breaking down, where is capacity constrained, and what drives the efficiency gap?

Process breakdown. Map the end-to-end process from input to output. At each step, ask: what is the input required, what is the output produced, what is the time and resource consumed, and where does quality failure occur? The step where delays concentrate or quality failures cluster is the process failure point.

Capacity constraint. Capacity is the maximum throughput a system can sustain. Find the step with the lowest capacity, and you have found the binding constraint. Everything upstream is operating below its potential. Everything downstream is starved for inputs. Improving anything except the binding constraint does not improve system throughput. Understanding fixed versus variable costs at each step also matters — steps with high fixed costs and low variable costs behave very differently under load than variable-cost-heavy steps, and the investment case for adding capacity differs accordingly.

Efficiency gap. Even without a capacity problem, systems can be inefficient. Changeover time, idle time between steps, rework from quality failures, and unplanned downtime all reduce realized output below theoretical capacity. The efficiency gap is the difference between what the system could produce at full utilization and what it actually produces. A related concept worth understanding is operating leverage — as volume increases, a business with high fixed costs and low variable costs can see disproportionate gains in profitability, which is exactly the dynamic that makes capacity utilization so valuable.

Operations cases often come with a lot of descriptive context. The interviewer will tell you about a factory, a hospital, a call center, a distribution network. Resist the urge to react immediately to the details.

Open with: "I'd like to map the end-to-end process first to understand where the constraint is. Can you walk me through the key steps from input to final output, and tell me where you are currently seeing the longest delays or the most failures?" This question invites the interviewer to give you the information you need while signaling that you understand the diagnostic sequence.

Then structure: "I'll map the process, identify where capacity is constrained, quantify the efficiency gap, and prioritize the two or three interventions that would have the highest impact on throughput."

Practice this framework on a real case: the Zoom COVID-2020 case on BoardroomIQ puts you inside one of the most dramatic capacity scaling challenges in modern technology, where demand exploded 30x in weeks and the operational constraint was not the product but the infrastructure supporting it.

The Theory of Constraints, developed by Eli Goldratt, gives you a precise method for operational improvement: identify the constraint, exploit it fully, subordinate everything else to it, elevate the constraint, and repeat.

In a case context, you don't need to cite Goldratt. But you need to execute this logic. Once you identify the binding constraint in the process, your recommendation should be: first, run the constraint at 100% utilization (eliminate waste at that specific step). Second, add capacity to the constraint if full utilization is not enough. Third, only after the constraint is resolved, look for the next one.

Candidates who recommend broad process improvements across every step without identifying the binding constraint demonstrate that they understand operations conceptually but not operationally. The interviewer will notice.

"You don't improve a system by improving everything. You improve a system by improving the one thing that's slowing everything else down."

Exercise 1: Process mapping from observation. Visit any physical business, a coffee shop, a grocery checkout, a bank branch, and map the process from customer arrival to departure. Identify the step with the longest queue or the most failure. That is the bottleneck. Practice doing this observation quickly and structured.

Exercise 2: Capacity math drills. Take any process with multiple steps and throughput rates. Calculate the overall system throughput given each step's capacity. Then model what happens to throughput if you add 20% capacity at the bottleneck versus at the input step. This builds intuition for where investment actually improves output.

Exercise 3: Implementation feasibility check. For any operational improvement you recommend in a practice case, ask: "What is the realistic timeline to implement this, and what are the top two implementation risks?" Operational improvements that are analytically correct but operationally infeasible destroy value rather than creating it.

The best way to practice operations cases is under realistic pressure, with a case that fights back.