Running a Good Chef Bad Chef Competition at Home or at Small Events
I've organized maybe twelve of these over the years, mostly for restaurant team building and some charity events. They're not as simple as telling two people to cook and then voting. The format works, but if you screw up the structure, it falls apart fast. Here's how to actually do it right. Two chefs, one set of ingredients, one dish to create, and a panel of judges who taste blind. The "good chef bad chef" part comes from the voting dynamic — you're not judging technique or creativity on its own merits, you're picking a winner between two people cooking the same brief. That distinction matters more than people realize. The basic run: chefs get a mystery ingredient or a constrained menu prompt, they have 45 to 90 minutes depending on the scale, they plate simultaneously, judges taste without knowing which plate came from whom, then you reveal and score. Repeat for two or three rounds and you have a winner.
I ran one once where I let the chefs see each other's ingredients. Bad move. One chef spent twenty minutes adjusting his game plan based on what the other was doing, which defeated the whole point. After that I switched to a sealed ingredient reveal system. Chefs draw their constraints in private fifteen minutes before the timer starts. Much cleaner.
How to Set It Up Properly
You need four things: a clear theme or constraint for each round, identical equipment and station setups, a scoring system that isn't just "which one tasted better," and judges who can actually separate flavor from presentation bias. The constraint is the most important part. Vague prompts like "make something Italian" produce boring results because both chefs play it safe. Specific constraints force interesting decisions. Last year I used "comfort food elevated" and one chef did a deconstructed tuna melt with bottarga foam while the other made a brioche bread pudding with brown butter. Both were valid. Both were interesting. That's what you want. For scoring, use a simple 1-5 scale across three categories: flavor balance, technical execution, and originality. Average those three numbers. This prevents the judge who only cares about taste from swaying the whole result. I learned this the hard way when a judge kept voting based purely on plating aesthetics and a technically flawless dish kept losing.
Get the Full Details
Common Problems and What I Do About Them
Timing is the first thing that goes wrong. One chef finishes in thirty minutes and sits around while the other is still plating. The judges notice. It creates an unconscious bias toward the finished dish because it's warmer and freshly presented. Solution: all dishes come out on the same call. No exceptions. I use a kitchen timer with a audible bell and neither chef plates until the bell rings, even if they're done early. They hold their dishes in the pass, and you bring them all out together. Another issue is ingredient quality variance. If one chef gets slightly better produce or a higher grade of protein, the comparison isn't fair. Get all ingredients from the same supplier on the same day, weigh everything before it goes out, and log it. Takes an extra twenty minutes of prep but it matters more than you'd think. Judge fatigue is real. After round three, people are tasting through butter sauces and reduced stocks and their palates are shot. Keep rounds to two or three maximum, and provide palate cleansers between — plain water crackers, maybe a light citrus sorbet. Don't let it drag into a fourth round expecting the same quality of judgment.
Practical Run Sheet
Here's a template that's worked for me at events ranging from six judges to forty. Adjust the times based on your crowd and kitchen capacity. Round one: 45 minutes cooking, 15 minutes judging, 10 minute break. Round two: same structure. Tally scores after round two. If there's a tie, go to a sudden death round with a 20-minute constraint like "finish something using only what's left in the pantry." Those rounds are chaotic but entertaining for the audience, which matters if you're doing this as a public event. The audience piece is worth thinking about separately. If people are watching, they want drama. If they're just eating, they want efficiency. These are different events disguised as the same format. I usually run a simplified version for catered audiences where the competition is between staff teams and the crowd just votes by applause after each round. Less precision, more atmosphere. Different tool for a different job.
When This Format Doesn't Work
Don't use this for training new cooks. The pressure of competition doesn't reveal teaching moments, it reveals who performs well under stress, which is a different skill. Don't use it when ingredient budgets are tight and you can't afford duplicates of everything. And don't do it with more than four rounds unless you have professional judges who understand palate management. Past that point you're just generating noise. If you're looking for something more educational, a blind taste test format where multiple people prepare the same dish and everyone shares what they did works better. If you need a charity fundraiser, lean into the audience voting and make it theatrical. The Good Chef Bad Chef Competition format is flexible but it's not a catch-all. Know what you're actually trying to accomplish before you book the kitchen.
