Why this decision matters
Every operations manager eventually has the same realization: the system is exactly as fast as its slowest step. You can hire more cashiers, but if the kitchen takes ten minutes per order, the queue still grows. You can buy a faster server, but if the database is the bottleneck, response time doesn't move. Bottleneck thinking is the single most reusable mental model in operations — this topic teaches you to do it on paper, in spreadsheets, and in real time.
By the end of this topic you'll be able to
Walk a process and identify the bottleneck in under five minutes. Compute cycle time, throughput, and flow time for a multi-step process. Apply Little's Law to relate inventory, throughput, and lead time. Use a process flow diagram and a capacity analysis to make a defensible recommendation about where to invest next.
Materials
Key concepts to know
- Cycle time — the time between completions at a step. Cycle Time = Available Time ÷ Units Required.
- Throughput — units per time. For the whole system: 1 ÷ (bottleneck cycle time).
- Bottleneck — the step with the longest cycle time. Determines system capacity. Everything upstream piles up; everything downstream is starved.
- Flow time — total elapsed time from raw input to finished output for one unit.
- Little's Law — Inventory = Throughput × Flow Time. The most useful identity in operations.
- Takt time — the customer's pace. The rhythm production must hit to keep up with demand.
- Utilization vs. efficiency — utilization is share of design capacity used; efficiency is share of effective capacity used.
- Capacity strategy — lead (build before demand), lag (build after), match (incremental).
Class notes & cheat sheets
- Operations Cheat HandbookZone 1 has all the bottleneck and capacity formulas.
- OSCM Student Study GuideWalks through the Ch 5 and Ch 11 concepts with worked examples.
Hands-on activity — the Bakery process
The bakery walkthrough is the canonical first bottleneck problem: a five-step morning bake process where the obvious "slow" step isn't actually the constraint. Work the worksheet, then check yourself against the key.
- Bakery Process Analysis (worksheet + key)Cycle time, throughput, bottleneck, flow time, and a small Little's Law check.
- BrewLine Operations DataMulti-sheet dataset — orders, staffing, deliveries. Find the constraint that's hurting CSAT.
Practice with games · Bottlenecks, capacity & flow
- Bottleneck HunterIdentify what's slowing down production.
- Bottleneck BusterIdentify, invest in, and improve constraints.
- Little's Law LiveBuild intuition for inventory, throughput, and flow time.
- Process Velocity RaceReduce waste and improve speed.
- Part 1 Review — JeopardyMixed review of everything in Part 1.
- Part 1 Review — Spin WheelRandom-prompt retrieval practice.
Using AI on this decision
Bottleneck analysis is a near-perfect AI workflow: paste process step times into an assistant and it will identify the constraint instantly. The harder, more interesting question is the one AI tends to dodge: which feasible action raises throughput the most? Force a numbered comparison ("rank these three interventions by expected throughput gain, with arithmetic").
The AI Student Guide uses BrewLine's CSAT crash as the worked example.