Getting Through the Kristen's Cookies Case Study Without Losing Your Mind
The Kristen's Cookies case study is one of those operations management problems that gets assigned every semester at business schools. It sounds simple on paper — you're running a small cookie bakery and need to optimize your process — but students tend to overcomplicate it. I've watched people spend hours going in circles on this one. The core of the problem revolves around a process flow where two students, Kristen and her roommate, make custom cookies to order. The process involves washing, mixing, portioning, baking, cooling, and packaging. Each step has different time requirements, and there are capacity constraints. The questions typically ask you to determine throughput time, cycle time, bottleneck resources, and how to improve the operation.
Where to Find the Kristens Cookies Case Study Solution
If you're looking for the full Kristens Cookies Case Study Solution to check your work or understand the answer key, you can find it on several academic solution repositories and course hero type sites. Make sure you're pulling from a version that matches your professor's specific question set, because editions vary. Some versions ask about pricing strategies, others focus purely on capacity analysis. The numbers change slightly between editions too. Here's the standard process breakdown most students miss on the first pass: Step one is loading the order, which takes about 3 minutes. Step two is washing and mixing, roughly 6 minutes. Step three is spooning the dough onto the tray, about 2 minutes. Step four is setting the oven and baking, 9 minutes for a dozen cookies. Step five is cooling, 5 minutes. Step six is packaging and taking payment, 4 minutes. The total throughput time for a fresh batch is around 29 minutes from start to finish.
But throughput time is not the same as cycle time. That distinction trips up probably half the class. Throughput time is how long a single order spends in the system. Cycle time is the time between completing successive units. For Kristen's operation, the cycle time is determined by the oven, which can only handle one batch at a time. The oven constraint gives you a cycle time of about 9 minutes per dozen, assuming the oven is the bottleneck.
Get the Full Details
Identifying the Bottleneck
The bottleneck in the basic case is the oven. Here's the thing most people don't immediately see: the oven is the bottleneck not because it's the slowest step in absolute terms, but because it's the only step that cannot be parallelized. Kristen can mix another batch while the previous one bakes. She can load trays while something cools. But she cannot bake two batches simultaneously in a single oven. I had a student once who insisted the bottleneck was the washing and mixing step because it took 6 minutes and the cooling step took 5 minutes. They were looking at individual step times without accounting for the fact that washing and mixing happens sequentially with other steps, while the oven blocks the entire line. The oven constraint means the theoretical maximum output is about 4 dozen per hour, not 6 or 7 like some students initially calculated.
Common Pitfalls and What I've Seen Go Wrong
Students frequently make three mistakes on this case. First, they forget to factor in the initial setup time. If you're starting from zero with an empty kitchen, the first batch takes the full 29 minutes because there's nothing in the oven yet. Subsequent batches come out faster because you can overlap activities. This is the concept of flow time versus response time, and getting it wrong throws off all your capacity calculations. Second, they calculate capacity by just adding up the step times and dividing. That gives you a number that sounds plausible but is fundamentally wrong because it ignores the sequential and parallel nature of the work. You have to map the actual resource usage over time. Third, and this is the big one, they don't consider the order size variable. The standard case assumes one dozen per batch, but if you're fulfilling a two-dozen order, you run the oven twice and the timing changes significantly. I worked through a version where a customer wanted three dozen in a rush, and the proper scheduling meant running one dozen, immediately starting the second, and overlapping the cooling and packaging of the first with the baking of the second. That changed the total time from what looked like 87 minutes on paper down to about 52 minutes in practice.
Pricing and Strategy Questions
Some editions of the case ask about pricing. The standard analysis shows that at the current price point, you're making very little margin after accounting for ingredient costs and the value of your time. The case typically gives you ingredient costs per dozen and asks whether you should raise prices, offer volume discounts, or both. The counter-intuitive insight here is that a volume discount might actually be the right move despite shrinking per-unit margin. If you can fill the oven more efficiently by combining orders, your effective capacity per hour increases, and that can outweigh the lower per-cookie price. One analysis I worked through showed that offering a small discount for orders of two dozen or more could increase hourly throughput by roughly 30 percent because you eliminate the changeover time between separate orders. But there's a limit. If you discount too aggressively, you saturate your capacity with low-margin work and end up worse off than if you'd stuck to single-order pricing at full price. The break-even analysis depends on your fixed costs and your available hours, which is why the case usually provides specific numbers you need to plug in rather than giving you a universal answer.
How to Improve the Operation
The textbook answer for improving the process usually involves one of three levers. You can reduce the oven time by increasing temperature or using multiple trays at once. You can add a second oven to break the bottleneck. Or you can redesign the workflow so that non-oven steps are done in parallel more aggressively. Adding a second oven is the most impactful change on paper. With two ovens, the bottleneck shifts away from baking, and your theoretical capacity roughly doubles. The catch is that a second oven costs money, and in the real world of a student-operated bakery, that capital might not be available. The case sometimes asks you to calculate payback periods, and the answer depends heavily on how many hours per week you actually plan to operate. A less obvious improvement is to prep dough in advance. If you mix and portion the dough the night before and store it in the refrigerator, you eliminate the 8-minute washing and mixing step from the daytime process. This doesn't increase theoretical capacity because the oven is still the bottleneck, but it dramatically improves responsiveness. Customers get their cookies faster because the delay between ordering and putting the tray in the oven shrinks from 11 minutes to basically zero.
Limitations of the Standard Model
The Kristen's Cookies case is useful for teaching basic process analysis, but it abstracts away a lot of real complexity. It assumes constant demand, no equipment failures, no quality issues, and perfectly reliable timing. In practice, a student bakery would deal with flour spills, oven malfunctions, customers changing their orders, and the inevitable variance in mixing times depending on humidity and ingredient temperatures. Another limitation is that the case treats labor as a cost to minimize rather than a capacity constraint with real human limits. Working a bakery shift back-to-back is physically taxing, and fatigue affects speed and quality over time. The math in the case doesn't capture that. If your professor's version includes a labor scheduling component, pay attention to it. Some editions ask you to figure out optimal shift lengths, and the answer isn't always what you'd expect. There's also a demand side that the case usually underspecifies. You can optimize the process all day, but if there aren't enough orders, your capacity is irrelevant. A few versions of the case include a demand forecasting element where you need to decide how much to produce in advance versus waiting for orders. That introduces inventory risk, which the basic version avoids entirely. If your edition has that component, treat it as a separate problem rather than trying to solve it with the process analysis tools.
What to Submit
When you turn this in, lead with your process map and clearly label the bottleneck. Show your cycle time calculation with the gantt chart or timeline diagram. Professors can tell when you guessed at the bottleneck versus actually mapping the resource utilization. Include your sensitivity analysis if the case asks for it — testing what happens if oven time drops by 20 percent or if demand doubles. That shows you understand the model rather than just filling in numbers. Keep your write-up tight. Most students bloat their submissions with restating the problem or explaining basic concepts the professor already covered in lecture. Just present the analysis, show your work, and answer the specific questions asked. Extra pages don't earn extra credit on this one. The Kristen's Cookies Case Study Solution is straightforward once you stop overthinking it. The trick is resisting the urge to add complexity that isn't in the problem. Map the process, find the bottleneck, calculate capacity, and move on.
