The Only Way to Roll Out a Menu
Why This Matters Most menus don’t fail because the food sucks. They fail because the process sucked. When we try to write a menu in one sitting, it turns into: - Too many voices at once - No paper trail - Great ideas that disappear - Hours burned with nothing finalized - Energy spent arguing instead of building I stopped doing that. I learned it’s easier—and better—to collaborate across time instead of trying to force magic in one meeting. Menus need space to marinate. How We Build Menus Now Instead of sitting in a room fighting through ideas, I: - Post concepts early - Let the team read through them - Allow comments, edits, and suggestions over time - Give people space to think, not react - Create conversation without chaos This does two things: 1. It creates clarity before emotion 2. It builds ownership before execution By the time we meet? We’re refining, not starting. Leadership isn’t collected in a meeting. It’s built in systems. Order of Operations: The Only Way to Roll Out a Menu. If you skip steps, you pay later. Here’s the exact order I follow every time: 1. Build the Menu on Paper First No cooking yet. No ordering yet. Just clarity. Write every dish: - Name - Components - Garnishes - Sauces - Accompaniments Nothing lives in your head. If it’s not written, it’s not real. 2. Create the Order Guide Build your purchasing backbone: - Vendor - Cost per pound - Cost per ounce - Case size - Yield notes You don’t cost a menu blindly. You cost it from the source. 3. Create Station Lists Every station gets: - A responsibility list - Items owned by that station - Prep expectations - Par levels Unassigned food = unowned food. 4. Diagram the Stations If your team can’t see the system, They can’t run it. Map: - Walk paths - Hot zones - Cold zones - Pickup flow - Garnish zones Work smarter, not sideways. 5. Write the Recipes Every dish gets: - Exact measurements - Yields - Steps - Storage - Shelf life - Reheating instructions