I’m tightening our seasonal menu and station flow and want CE that improves throughput, not just checks a box. After a 90-minute mise en place module last spring, our grill station cut average ticket time from 14 to 11 minutes by reordering the build and updating the par sheet in KitchenSync. If you’ve taken a course or micro-credential that directly boosted menu engineering or batch prep scheduling (Rouxbe, ACF, Lean in Kitchens, HACCP with costing), which delivered the biggest ROI?
Swapping to a ‘one-touch, left-to-right’ build after a short station-choreography CE shaved about 2 minutes off burgers by keeping cold toppings on the non-dominant side and pre-slicing buns to par; it only sticks if you park low-velocity mods in a flex bin or 86 them during peak.
Building on @nmoore10, a quick ops CE from eCornell pushed us to tag SKUs in the POS by cook-time bands (2/4/8 min) so chits print in fire order; that alone cut our median ticket from 12:30 to about 9:45 on mixed orders. Small caveat: expo has to enforce the ‘longs first’ rule for a week or it backslides — want the banding chart we used?
Did a 60-minute TOC + 5S micro that had us map the bottleneck and tag SKUs by “cook-time x margin”; we cut a 9‑minute grill item from lunch, pre‑griddled bacon, and tied daypart pars in KitchenSync — median tickets fell about 2 minutes. It only sticks if you re-time items weekly or the bands drift. Pairs nicely with @nmoore10’s fire-order setup.
Quick example: a Rouxbe micro on capacity planning had us score items by “touches per plate” and rebalance by station; we moved two garnishes to pantry, put sauces in 2‑oz squeeze bottles, and capped grill at five live plates with a simple kanban — our long‑tail tickets shrank fast. Caveat: it only sticks if you re‑score touches each menu change, or the creep sneaks back like a mise goblin. https://rouxbe.com.
We got the most lift from a short Typsy module on station layout that had us make a one-page ‘plate map’ for each dish and tape it to the pass; aligning the rail and tools to that map cut assembly by about 30 seconds per item and reduced expo chatter. Small caveat: it sticks only if you run a 10‑minute pre-shift drill for a couple weeks so people use it; @nmoore10, it also made cross-training faster when we swapped seasonal items.
I had a good result with eCornell’s Menu Engineering: Pricing & Design (Home - eCornell) by adding a simple “complexity index” (steps per plate + station hops) to our sheet; we cut two high-labor, mid-margin dishes and pre-portioned a couple of finishing components, and sauté’s median to pass dropped 1.7 minutes with far less variance. Felt like swapping a grocery cart for one that doesn’t wobble. Caveat: you’ll need a solid week of timing samples per item to make the index honest.
Not chef-y CE, but Wharton’s Operations Management on Coursera (https://www.coursera.org/learn/wharton-operations) gave us Little’s Law; we set a WIP cap at grill and moved two 8‑min cooks to prep‑finish — tickets dropped from 13 to 10, echoing your 90‑minute mise bump. Caveat: it only sticks if expo enforces the cap in KitchenSync with a simple “max in queue” field.