The World In 80 Dishes

Working With The World In 80 Dishes as a Culinary Reference Project

The World In 80 Dishes is a curated framework used by food writers, recipe developers, and culinary educators to map out a coherent journey through global cuisine. Rather than treating it as a fixed list you simply follow, it works best as a structural scaffold — a way to organize ingredients, techniques, and cultural contexts into a sequence that actually makes sense to cook through. People tend to misunderstand it as a checklist, which defeats the purpose. You end up with 80 disconnected recipes instead of a usable reference system. The first step most people get wrong is starting with recipes instead of regions. Pick a geographic or cultural grouping first — Southeast Asia, the Levant, the Andean highlands, West Africa — then fill in dishes until you hit roughly eighty. Distribute them across meal types and cooking methods so you aren't left with seventy grilled proteins and three raw preparations. Spread them out across raw, boiled, steamed, fried, fermented, roasted, and stewed techniques. I ran into a specific problem last year when I was compiling a version of The World In 80 Dishes for a kitchen training program. I had about forty dishes mapped out, and every single one from the South Asian section required a spice blend that wasn't available pre-made anywhere in the supply chain I was working with. Garam masala was fine, but the regional variations I wanted — Assam-style, Kashmiri, Malabar — needed whole spices that cost more in small quantities than was practical for a classroom setting. My workaround was to create a master spice stock system. I bought five kilograms of cumin, coriander, fennel, mustard seed, and cardamom in bulk, then pre-mixed small batches scaled to each recipe's needs. That cut ingredient prep time from roughly forty minutes per session down to about eight minutes. The tradeoff is that your blends lose freshness after about three weeks, so I rotate the stock monthly.

Once your regions are mapped and your spice situation is sorted, start assigning difficulty levels. Not all dishes need equal weight in the collection. A beginner-friendly The World In 80 Dishes should have roughly a third of its entries at what I'd call foundation level — dishes that teach a single technique or introduce one new ingredient without requiring equipment most home kitchens don't already have. The remaining two-thirds can ramp up into intermediate and advanced territory, where you're combining techniques or working with harder-to-source items.

What Most People Miss About This Framework

One counter-intuitive thing about building a collection like The World In 80 Dishes is that the most useful dishes aren't always the most famous ones. A properly executed oxtail stew from Lagos teaches you more about West African flavor architecture than a chicken jollof recipe from a top-rated travel blog, because the stew forces you to deal with palm oil ratios, scotch bonnet heat distribution, and the layering of aromatics in a way that the rice dish doesn't. Famous dishes tend to get simplified in Western sources. Authentic versions often require techniques that are glossed over — smoking salt at home, toasting whole spices in a dry pan until they release their oils, fermenting chili paste for two weeks instead of using bottled sauce. Another thing beginners overlook is that you need a sourcing map alongside the recipe list. If your The World In 80 Dishes includes dill pickle from Sweden, harissa from Tunisia, and kimchi from Korea, you need to know whether your local shops carry those ingredients or whether you'll be ordering online. I keep a simple spreadsheet that tracks each ingredient against three columns: local grocery store availability, specialty import shop availability, and online ordering lead time. That alone saves hours when you're planning a cooking schedule. Without it, you end up three dishes into your collection and realize you can't get fresh pandan leaves delivered to your area in under five days. There's also a sequencing problem that trips people up. You can't cook The World In 80 Dishes in random order and expect it to build properly. If you start with a dish that relies on a technique you haven't practiced yet — say, making your own pasta from scratch for an Italian entry before you've attempted a simpler dough-based recipe — you'll either fail at the technique or skip learning it entirely. I sequence my collections by technique inheritance. Each new dish should reinforce at least one skill from a previous entry while introducing one new element. That way the whole project functions as a curriculum rather than a scrapbook.

Pitfalls and Where This Approach Breaks Down

The biggest limitation of using The World In 80 Dishes as a primary reference is that no single collection can cover the diversity it claims to represent. Eighty dishes across the entire world is roughly one dish per modern nation-state, which means hundreds of significant culinary traditions get compressed into a single entry or omitted entirely. A Mexican entry might stand in for twenty distinct regional cuisines. A single Korean dish replaces hundreds of family recipes and seasonal preparations. This isn't a flaw in the framework itself — it's a structural constraint you need to accept going in. Another practical bottleneck is ingredient shelf life. If you're building a physical copy of The World In 80 Dishes with sourced ingredients, you're managing perishables that expire at different rates. I've seen people buy everything upfront for a month-long cooking schedule and end up throwing out thirty percent of their ingredients. A better approach is to plan two weeks ahead at a time, sourcing only what you need for that window. For anyone looking to start with an existing The World In 80 Dishes framework rather than build from scratch, the most accessible route is searching for published collections from culinary institutions or well-known food writers who have already done the regional mapping. University extension programs, particularly those tied to food science departments, sometimes publish version of this kind of collection as part of their educational materials. Check academic food journals, culinary school syllabi, and publications from organizations like the International Association of Culinary Professionals. Those sources tend to be more rigorously sourced than what you'll find on general recipe blogs.

If you want something more structured than a personal compilation, consider pairing your The World In 80 Dishes project with a foundational cookbook that covers technique rather than just recipes. Books like The Food Lab by J. Kenji López-Alt or On Food and Cooking by Harold McGee give you the underlying principles that make any curated collection work. Without that foundation, you're just following instructions without understanding why they work, which limits how far you can go with the material.