Timeline for Timing cooking: methods / workflow
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2010 at 17:42 | comment | added | stack | Yeah, definitely no Gantt charts in my kitchen -- I just review recipes ahead of time and hope everything sticks (the floating-vaguely-in-your-head technique). Luckily I haven't been in charge of handling any epic feasts, or I'd have to add more structure. | |
| Aug 9, 2010 at 7:42 | comment | added | Tobias Op Den Brouw | Which you did, yes. :) But I assume you don't have Gantt charts in your kitchen yourself. Do you use a watered-down version, or is it all floating vaguely in your head (like it is for me)? | |
| Aug 6, 2010 at 22:01 | comment | added | stack | Maybe... though mine is perhaps more consistent/definitive in terms of method, and allows you to map dependencies more clearly. Basically I just wanted to offer up what's probably the most extreme management method you could feasibly use. :) | |
| Aug 6, 2010 at 13:15 | comment | added | Tobias Op Den Brouw | A good answer - but it's basically hobodave's answer as well, right? While I applaud the nice result this planning will put out, I guess it will be a casualty on the kitchen floor as soon as something goes out of whack - whiteboard (and a bit of yelling) will help. Still, when cooking for a huge meal, many courses, a few cooks, it might be a nice tool to get everyone on board. And it will pinpoint bottlenecks (too many pans, not enough fire) as well. | |
| Aug 5, 2010 at 19:43 | history | answered | stack | CC BY-SA 2.5 |