principle of operations management sustainability and supply chain management

If you manage anything—a factory, a restaurant, a hospital ward, a software team's backlog—this book gives you the vocabulary and the tools to see your operation clearly. It's the standard text for MBA students and operations professionals, but the stories make it readable for founders and general managers who just want to know why their supply chain keeps breaking. You'll never look at a queue, an inventory shelf, or a late project the same way.

1. 1Chapter 1

   Operations is just value creation made visible

   Picture a title insurance office: four workers pushing eight titles through per day. Then a new system lands, and the same four people process fourteen. The math is almost embarrassingly simple—8 divided by 4 is 2 titles per worker; 14 divided by 4 is 3.5. Productivity rose from 2 to 3.5 titles per worker per day, and nobody worked harder. That's the whole discipline in miniature: operations management is the set of activities that create value in goods and services by transforming inputs into outputs, and the ratio of what comes out to what goes in is the scoreboard.

   The idea

   Productivity isn't a vague aspiration—it's a fraction you can actually move. The book's formula, units produced divided by input used, forces you to name your inputs and count your outputs, which is where most organizations get uncomfortable. What surprises people is how small the levers can be: a better system, a clearer process, a smarter layout. The ten strategic decisions include design of goods and services, managing quality, process strategy, location strategies, layout strategies, human resources, supply chain management, inventory management, scheduling, and maintenance.

   Try this: Pick one process you own and compute its output-per-input ratio this week, then again after one small change.

2. 2Chapter 2

   Boeing outsourced 70% of a plane and paid for it

   The 787 Dreamliner was supposed to be Boeing's masterpiece of global strategy. The company outsourced roughly 70% of the aircraft's components to suppliers in Italy, Japan, and South Korea, spreading risk and tapping the best engineering on three continents. Then the parts started arriving—incomplete, or worse, not fitting together. The complex supply chain produced costly delays, and a plane meant to showcase global coordination became a case study in its hazards. Strategy, as Porter puts it, is choosing what not to do; Boeing outsourced about 70% of the aircraft's components to suppliers around the world.

   The idea

   Global operations strategy is a trade, not a free lunch. Outsourcing buys expertise and shares risk, but every handoff adds a point where the system can fail—and when your product is a single aircraft assembled from pieces made worldwide, those failure points compound. Porter's five forces—rivalry, new entrants, substitutes, customer power, supplier power—give you the map for deciding which activities truly belong inside your walls. The surprise is that 'more partners' often means less control, not more capability.

   Try this: List one activity you've outsourced and ask what would break first if the supplier delivered late.

3. 3Chapter 3

   Denver's airport lost $1 million a day on a baggage system

   Denver built a new international airport and bet its opening on an automated baggage-handling system designed by BAE Automated Systems. The system failed repeatedly, delaying the airport's opening by 16 months at a cost of about $1 million per day in interest and operating costs. A project that looked like a plumbing problem was actually a project-management problem: scope, scheduling, and integration of thousands of moving parts that no one had fully tested together.

   The idea

   Project management exists because big undertakings fail in predictable ways: optimistic schedules, untested integration, and no honest way to say 'we're behind' until the money's gone. Denver's 16-month delay is what happens when a system this complex is treated as a single delivery rather than a sequence of testable milestones. The discipline—networks, critical paths, earned value—isn't bureaucracy; it's the difference between a late airport and an open one.

   Try this: For your next project, identify the one integration step most likely to fail and schedule a test of it first.

4. 4Chapter 4

   Disney forecasts attendance 20 years out

   At Walt Disney World, a forecasting group sits at the center of everything: staffing, maintenance, even the shows. They blend historical data, survey data, and a toolbox of models—judgmental calls, econometrics, moving averages, regression—to predict how many people will walk through the gates. Forecasts range from daily up to 5-year and 20-year horizons. Get it wrong and lines balloon or cast members stand idle; get it right and the magic looks effortless.

   The idea

   Forecasting isn't one technique—it's matching the method to the horizon and the stakes. Disney's range, from daily staffing calls to two-decade capacity bets, shows why a single model can't serve every question. The mix of judgment and math matters too: historical patterns anchor you, surveys catch what history can't, and complex models squeeze out the last bit of accuracy. Most organizations underinvest in the boring discipline of being less wrong about next month.

   Try this: Write down your demand forecast for next month, then compare it to reality and note where your guess came from.

5. 5Chapter 5

   Regal Marine designs a boat in 5 months

   At Regal Marine, a Florida boat builder, design is a race. The company uses CAD and a disciplined product development process to move from concept to production in as little as 5 months, introducing new models every year. Speed matters because a boat that misses the season is a boat that doesn't sell. The chapter pairs this with quality function deployment—the house of quality matrix that translates what customers say ('easy to close' on a car door) into engineering characteristics like door seal resistance. Toyota used QFD to cut startup costs for a new van by 60% and development time by one-third.

   The idea

   Product design is where cost and quality get locked in, long before the factory sees anything. QFD's house of quality is deceptively simple: it forces engineers to trace every technical choice back to a customer phrase, which kills features nobody asked for. The surprise is how much money hides in the translation step—Toyota's 60% startup-cost reduction came not from building cheaper but from building the right thing the first time. Fast design cycles and customer translation are the same discipline seen from two angles.

   Try this: Take one feature you're building and write the customer sentence it serves; if you can't, cut it.

6. 6Chapter 6

   Ritz-Carlton lets any employee spend $2,000 to fix a guest's problem

   The Ritz-Carlton Hotel Company empowers employees to spend up to $2,000 to resolve a guest's problem or complaint without management approval. That's quality management as a living system, not a poster. It sits alongside the heavier machinery: Six Sigma, pioneered by Motorola in the 1980s, targeting no more than 3.4 defects per million opportunities, later made a central business strategy by Jack Welch at GE. At Arnold Palmer Hospital in Orlando, a quality team cut epidural wait times from an average of 45 minutes to under 15 and pushed Press Ganey patient satisfaction scores to the 99th percentile.

   The idea

   Quality is a system of decisions, not an inspection step. Deming's 14 Points include 'Create constancy of purpose toward improvement of product and service' and 'cease dependence on inspection'; Deming taught quality methods to Japanese manufacturers after World War II (in the 1950s), and the lesson holds: build quality in, don't check it in afterward. Crosby's line that quality is free, and what costs money are the unquality things, reframes the whole budget conversation. Empowering the person closest to the problem, as Ritz-Carlton does, is what 'built in' looks like in service.

   Try this: Give one frontline person on your team explicit authority to fix a customer problem up to a set dollar limit this week.

7. 7Chapter 7

   Harley-Davidson cut assembly from 21 hours to 6

   Harley-Davidson's York, Pennsylvania plant builds 1,400 variations of motorcycles. The plant produces 1,400 variations of motorcycles using a work-cell layout that reduced assembly time per motorcycle from 21 hours to 6 hours. The book describes four process strategies: process focus (low-volume, high-variety), repetitive focus (modules), product focus (high-volume, low-variety), and mass customization (high-volume, high-variety), with examples such as hospitals (process focus), Harley-Davidson (repetitive focus), and Frito-Lay (product focus). Dell's build-to-order model lets customers configure PCs online with assembly and shipping of the customized unit within about 48 hours while holding only a few days of inventory. Build-A-Bear Workshop, where customers customize their own teddy bears.

   The idea

   Your process strategy is a choice about volume and variety, and the four options are really a map of where you sit. Mass customization is the seductive corner—high volume, high variety—but it only works if you've modularized everything behind the scenes, as Dell's 48-hour build-to-order shows. The theory of constraints, from Goldratt's 'The Goal,' adds the discipline: find the one constraint, exploit it, subordinate everything else, elevate it, repeat. Most plants spread improvement thin instead of attacking the bottleneck.

   Try this: Identify the single slowest step in your main process and spend one week improving only that step.

8. 8Chapter 8

   FedEx built an empire on a hub in Memphis

   FedEx's overnight delivery promise rests on a single decision: where to put the hub. Memphis won—for its central US location and time zone, its large labor force, and historically good weather. The hub processes about 1.5 million packages daily, enabling overnight delivery across the United States. Location strategy at this scale isn't a spreadsheet footnote; it's the physical architecture of the entire business.

   The idea

   Location decisions have long half-lives: pick wrong and you pay rent on the mistake for decades. The book's toolkit—factor rating for weighted criteria, locational break-even analysis, the center-of-gravity method, the transportation model—turns a gut call into a structured comparison. What FedEx shows is that the right factors aren't always obvious: weather and time zone matter as much as real estate cost when your whole model depends on a nightly sort. Weigh the factors your business model actually depends on.

   Try this: For one siting decision you face, list five weighted factors and score two options before you debate gut feel.

9. 9Chapter 9

   McDonald's rebuilt its kitchen to make a sandwich in 45 seconds

   The old system held pre-made sandwiches in warming bins. The new layout uses high-tech equipment and a sandwich assembly line that can produce a customized sandwich in 45 seconds. Layout is strategy made physical. The same chapter covers assembly-line balancing—computing cycle time as production time available divided by units required, then the theoretical minimum number of workstations and efficiency. At Toyota's Georgetown, Kentucky, plant, workers are cross-trained to operate multiple machines in a U-shaped cell, reducing throughput time and work-in-process inventory.

   The idea

   Layout determines what's possible before a single process improvement is attempted. McDonald's move from batch-and-hold to build-to-order wasn't a software upgrade—it was walls, equipment, and the path a sandwich takes. Line balancing math (cycle time, workstation count, efficiency) turns 'the line feels slow' into a number you can fix. Toyota's U-shaped cells show the same principle in manufacturing: shorten the loop, and inventory and time shrink together.

   Try this: Sketch the physical path a unit of work takes through your operation and count every place it stops or waits.

10. 10Chapter 10

    The Hawthorne studies: attention itself moves the needle

    At Western Electric's Hawthorne plant, researchers changed the lighting to see how it affected output. Productivity went up. Then they changed it back—and productivity went up again. The finding, now called the Hawthorne effect, was that the attention given to workers, not the lighting, drove the gain. The chapter pairs this human insight with the mechanical side of work measurement: time studies, predetermined standards like MTM, and work sampling. In a time study example, 20 observations averaging 0.40 minutes with a 110% performance rating give a normal time of 0.40 × 1.10 = 0.44 minutes.

    The idea

    People are not machines, and pretending otherwise produces bad data. The Hawthorne studies are the classic warning: any change you measure is confounded by the fact that someone is paying attention. Work measurement—time studies, MTM, work sampling—gives you the labor standards that make scheduling and costing honest, but only if you remember that the observer is part of the system. The best operations treat worker attention as a resource to be earned, not assumed.

    Try this: Time one repetitive task you do five times, average it, and see where the variation hides.

11. 11Chapter 11

    Darden moves 700 million pounds of food a year

    Darden Restaurants (operator of Red Lobster, Olive Garden, and LongHorn Steakhouse) sources food from around the world—over 700 million pounds annually for its 1,500+ restaurants—through a centralized distribution system. The stakes are visible in the bullwhip effect: P&G's Pampers diapers showed retail sales relatively stable while wholesale orders and orders to suppliers fluctuated dramatically, because small demand changes amplify as they move up the chain. Vendor-managed inventory (VMI), in which the supplier manages inventory at the retailer, was pioneered by Walmart and Procter & Gamble; Walmart's satellite-based system transmits point-of-sale data from stores to suppliers, enabling replenishment within 48 hours. Disruptions such as the 2011 earthquake (and tsunami) in Japan affected global supply chains, particularly automotive parts, forcing Toyota to shut down production for several weeks.

    The idea

    Supply chains fail in two ways: too much information friction and too little resilience. The bullwhip effect is pure information economics—each tier orders on distorted signals, so the farther you are from the customer, the wilder your world looks. Sharing data, as Walmart's satellite-linked VMI shows, is the antidote. Risk is the other half: a single earthquake can idle a global automaker. Darden's scale shows why centralized distribution and diversified sourcing aren't luxuries—they're insurance.

    Try this: Trace one product you buy back two suppliers and ask what single event could cut it off.

12. 12Chapter 12

    Amazon's algorithms and the 80/20 of inventory

    Amazon uses sophisticated algorithms and a network of fulfillment centers to hold inventory close to customers. The logic underneath is ABC analysis: ABC analysis classifies inventory items by dollar usage: roughly 15% of items (Class A) account for 70–80% of dollar usage, 30% (Class B) for 15–25%, and 55% (Class C) for about 5%. The math that makes it work is the economic order quantity: Q* = sqrt((2DS)/H), where D is annual demand, S is ordering cost, and H is holding cost. Worked examples compute EOQ, reorder points, and safety stock so you know not just how much to order but when.

    The idea

    Inventory is where cash goes to hide, and the book's tools are all about making it visible. ABC analysis tells you where to spend your management attention—the 15% of items eating most of your dollars—instead of treating every SKU equally. EOQ balances two opposing costs: ordering too often versus holding too long.

    Try this: Pull your top 20 inventory items by dollar value and check whether they get proportionally more attention than the rest.

13. 13Chapter 13

    Frito-Lay matches millions of pounds of snacks to fickle demand

    Frito-Lay uses sales forecasts and capacity planning to match production capacity (in millions of pounds of snacks) with fluctuating demand for snack foods. Frito-Lay employs strategies like overtime, inventory, and subcontracting. The umbrella discipline is sales and operations planning, a process that keeps demand and supply in balance by integrating sales forecasts, production plans, and inventory plans into one coherent picture rather than letting each function plan alone.

    The idea

    Aggregate planning is the art of deciding which pain to accept: overtime costs, inventory carrying costs, or subcontracting premiums. S&OP matters because without it, sales promises one thing, production builds another, and finance forecasts a third. The surprise is how much of the problem is communication, not optimization—getting one number that everyone plans against. Frito-Lay's pounds-based view shows you can plan at the aggregate level even when the SKU list runs into the hundreds.

    Try this: Hold a monthly meeting where sales, operations, and finance agree on one demand number before anyone plans.

14. 14Chapter 14

    Wheeled Coach builds ambulances from 20,000 parts

    Wheeled Coach, a Florida-based manufacturer of ambulances (the world's largest), uses MRP to manage the thousands of parts—over 20,000 components—needed for each customized vehicle. MRP is what keeps that from collapsing into chaos: the master production schedule, the bill of material, and inventory records feed a system that computes planned order releases so the right parts arrive at the right time. Collins, a manufacturer of ambulances, uses MRP to manage an inventory of 18,000 part numbers. The MRP system reduced inventory by 30% while improving on-time delivery to 97%.

    The idea

    MRP is dependent demand made computable: once you know how many ambulances and when, every component's schedule follows from the bill of material. The three inputs to MRP are the master production schedule (MPS), the bill of material (BOM), and inventory records—simple, but keeping them accurate is where most implementations die. The surprise is the payoff size: Collins cut inventory by nearly a third while improving delivery, because accurate part-level timing means you stop ordering 'just in case.' ERP extends the same logic across the whole enterprise.

    Try this: Check whether your bill of materials for one product is actually accurate—walk the floor and verify.

15. 15Chapter 15

    Which job goes first? Scheduling rules decide

    A queue of jobs sits in front of a machine, and someone has to pick the order. The rules on offer: first-come, first-served, earliest due date, shortest processing time, critical ratio. Each performs differently on average flow time and average lateness, and the book compares them head-to-head with worked examples. For two work centers in sequence, Johnson's rule finds the sequence that minimizes total processing time—a small piece of math that can shave hours off a shop's makespan without buying anything new.

    The idea

    Sequencing is one of the cheapest performance upgrades available: no capital, no new hires, just a different rule for picking the next job. SPT tends to minimize average flow time but can starve long jobs; EDD protects due dates; FCFS feels fair but optimizes nothing. Johnson's rule is the rare case where an optimal answer exists for a common problem—two machines in series—and it takes minutes to apply. Most shops default to FCFS out of habit, not choice.

    Try this: Take tomorrow's job queue and re-sequence it by shortest processing time; compare total completion time to your usual order.

16. 16Chapter 16

    Toyota hunts seven wastes and calls it kaizen

    Toyota's production system became the template for lean operations worldwide, built on continuous improvement—kaizen—and the relentless elimination of waste. The seven wastes (muda) in lean operations are overproduction, waiting, transportation, (inappropriate) processing, (unnecessary) inventory, (unnecessary) motion, and defects. Taiichi Ohno, the system's father, framed it plainly: look at the timeline from the moment the customer gives an order to the point cash is collected, and reduce it by removing the non-value-added wastes. Every lean tool—cells, kanban, quick changeovers—is an attack on one of those seven.

    The idea

    Lean's power is its definition of waste: anything the customer wouldn't pay for. Ohno's timeline framing turns abstract efficiency into a single measurable span—order to cash—and every one of the seven muda stretches it. What surprises people is how much of a typical operation is waste: waiting and motion alone often dwarf actual processing time. Kaizen matters because waste regrows; the system isn't a project with an end date but a habit of looking.

    Try this: Walk your process with the seven wastes list and mark every instance of waiting and unnecessary motion you see in one hour.

17. 17Chapter 17

    Three 0.90s in a row give you 0.729

    Orlando Utilities Commission uses predictive maintenance with vibration analysis, infrared thermography, and oil analysis on 1,800 pieces of equipment, achieving a 98% availability rate on its coal-fired generating units. The math underneath is unforgiving: in a series system, reliability is the product of component reliabilities, so three components each at 0.90 yield 0.90 × 0.90 × 0.90 = 0.729. Chain enough 'pretty reliable' parts together and the system as a whole is worse than any one of them.

    The idea

    Reliability math is brutal in series: multiply, and watch the number sink. That's why redundancy exists—parallel paths raise the system's odds even when each component is mediocre. The maintenance side is a strategy choice: run to failure, prevent on a schedule, or predict with sensors. OUC's 98% availability shows why prediction wins for expensive assets—you fix things just before they fail, not after, and not wastefully early.

    Try this: List the components in series in one critical process and multiply their estimated reliabilities to see your true system odds.

18. 18Module D

    Queuing theory: why you always pick the slowest line

    A single-server system with service rate 10 per hour and arrival rate 8 per hour has average number in system 8/(10−8) = 4 customers and average time in system 1/(10−8) = 0.5 hours (30 minutes). That's the whole queuing model in one line: utilization, queue length, and wait time all fall out of the arrival and service rates. The book extends this to multi-channel systems, computing average customers in line, average waiting time, and utilization for each configuration.

    The idea

    Waiting lines behave non-intuitively because they're driven by ratios, not raw numbers. As utilization approaches 100%, waits explode nonlinearly—a server at 80% utilization has manageable lines; at 95%, chaos. The formula 8/(10−8) = 4 shows why: the gap between arrival and service rates is what matters, and it shrinks fast. This is why adding one more teller or agent can transform a system, and why 'we're only at 90% capacity' is already a warning.

    Try this: Estimate the arrival rate and service rate at one queue you manage and compute the average wait.

MBA students, operations managers, and supply chain professionals who need the canonical framework and vocabulary. Founders and general managers who want to understand why their operations feel chaotic—and what the levers are—will get a lot from the stories even if they skip the formulas.

FAQ