Cafe and Cloud Kitchen Operations Study
A neighbourhood café and a delivery-only cloud kitchen can sell the same sandwich at the same price and end the month with completely different bank balances. One pays rent for twenty-four seats and a barista who is idle from three to six in the afternoon; the other pays a commission on every order and lives or dies by how fast food leaves the counter after a rider arrives. Owners of both feel the pressure daily, yet almost none of them have ever timed an order, costed a recipe, or worked out which menu items quietly lose money on every sale.
The intern runs a comparative operations study of two fictional small food businesses, a twenty-four seat café called Kettle and Crumb and a delivery-only kitchen called Tandoor Tales, using observation rather than opinion. That means six timed site visits with a stopwatch log of forty orders from placement to service, activity sampling of what staff actually do minute by minute, a five-day wastage tally, a hundred public delivery-app reviews coded into complaint categories, a menu engineering matrix in excel that sorts twelve items by popularity and contribution margin, a peak-hour capacity model that names the bottleneck station, three swimlane process maps drawn in canva, and a pack of standard operating procedures written in google-docs.
The project teaches the core toolkit of operations management: process mapping, cycle-time analysis, bottleneck thinking, contribution margin, capacity planning, and turning messy observation into a costed recommendation an owner can act on this week. Operations, supply chain, retail, and quick-service roles all interview on exactly this ground, and a study that names a bottleneck and quantifies the fix reads far stronger than a summer spent shadowing a manager.
Related projects
You might also like