The Chicken Tikka Masala Problem: Invented Dish, Real Demand

The Glasgow Question Nobody Can Actually Settle

In 1988, a Glasgow restaurateur named Ali Ahmed Aslam told the story of how he invented chicken tikka masala in the 1970s at his restaurant Shish Mahal. A customer complained that his chicken tikka was too dry. Aslam, or someone in his kitchen, added a sauce made from tomato soup, cream, and spices. The customer was satisfied. A dish was born. Or so the story goes.

The story has problems. Tomato-cream sauces appear in Mughal-era Persian-influenced cooking. Butter chicken, which is structurally similar, was developed at Moti Mahal in Delhi sometime in the late 1940s or early 1950s by Kundan Lal Jaggi, who used leftover tandoori chicken and a tomato-butter sauce that had originally been a way to keep the meat from drying out. The line between butter chicken and chicken tikka masala is not a bright one. It is more like a gradient — two points on a continuum of tomato, cream, and charred chicken, separated by geography and a marketing decision.

In 2009, the European Parliament member for Glasgow, Mohammad Sarwar, pushed for chicken tikka masala to receive Protected Geographical Indication status as a Scottish dish. He did not succeed. In 2001, Foreign Secretary Robin Cook had already called it Britain's true national dish in a speech that was partly about multiculturalism and partly about votes. Neither the parliamentarian nor the foreign secretary was making a culinary argument. They were making a political one.

The question of chicken tikka masala's origin is genuinely unanswerable with certainty, and the people who argue about it most loudly are usually not cooks. They are people who want the dish to belong to a particular national story. The cooks have a different relationship to the question. They make the dish or they do not, and either way they move on.

What It Means to Invent a Dish Inside a Living Tradition

The trouble with the invention narrative is that it treats cuisine as if dishes arrive fully formed, the way patents do. A named individual, a specific date, a contained act of creation. Food does not work this way. Chicken tikka masala did not come from nowhere. It came from tandoor culture, from Mughal court cooking, from South Asian spice logic, from the British adaptation of Indian restaurant food that had been happening since at least the 1960s.

What likely happened in Glasgow or somewhere like it is not invention but crystallization. A set of techniques and flavors that existed in diffuse form — charred chicken, tomato, cream, aromatic spice — was pulled together and given a name that could survive a menu. The name is what made it spreadable. Without the name, it was just a cook improvising. With the name, it became something a restaurant could put on a card and a customer could reliably order again.

This is how most dishes that travel actually travel. Not as recipes but as names attached to a recognizable flavor profile. The name gives the dish a fixed point. The recipe continues to move. Every cook who makes chicken tikka masala makes a slightly different version, and the dish accommodates all of them because the name is doing the stabilizing work, not the formula.

The Dish explored this pattern with XLB — the way a dish's name freezes something that the underlying technique keeps refining — and the dynamic is identical here. The name chicken tikka masala has stayed constant for roughly fifty years. The dish it names has not stayed constant for a single decade.

The Bay Area as an Unintentional Laboratory for the Dish

The Bay Area's Indian restaurant population is large enough and internally diverse enough to serve as a useful test case for what actually happens to a dish after it spreads. There are restaurants here serving Punjabi-inflected tikka masala that runs deep orange and thick. There are restaurants serving versions that are lighter, more tomato-forward, closer to a British curry house than to anything in North India. There are restaurants that refuse to serve it at all, positioning themselves around regional cuisines where the dish has no native context.

Vik's Chaat. Udupi Palace. Dosa. These are restaurants that have built reputations around South Indian cooking — dosas, idli, sambar — where chicken tikka masala is not on the menu and its absence is not an oversight. The omission is a statement about regional specificity. South Indian cooking does not have a tikka masala tradition. Putting it on the menu would be like a Sichuan restaurant adding General Tso's chicken to avoid confusing customers. Some do it. Most that care about their food do not.

Then there are the restaurants that serve it because they have to. Any sit-down Indian restaurant with a broad menu in an American city knows that a meaningful percentage of its customers will order chicken tikka masala regardless of what else is available. Amber India. Shalimar. Curry Up Now. Each handles the dish differently. Some version of it appears on most menus, and the version tells you something about what the kitchen thinks of its customers and of itself.

The scoring data from our Bay Area Indian restaurant coverage picks up on this. Restaurants that treat chicken tikka masala as a serious dish — where the kitchen is grinding whole spices, charring chicken on a real tandoor, building the sauce over real time — score differently from restaurants where the dish is a concession. Flavor scores diverge sharply. Value scores are roughly comparable across both categories because the dish is priced similarly everywhere. The algorithm can see the difference that the menu cannot say out loud.

The Demand Side Argument: Why Invented Dishes Earn Their Place

There is a version of the chicken tikka masala conversation that treats the dish as a problem — a corruption of authentic Indian cuisine, a colonial imposition, a dumbed-down proxy that crowds out more complex cooking in the minds of Western diners. This version has merit as a critique of how mainstream restaurant culture works. It does not have much merit as an argument about the dish itself.

Chicken tikka masala is fifty-odd years old. The cooks who have made it well over those decades have not been making a fake dish. They have been making a real dish that happens to have a contested origin story. The tomato-cream-spice logic at the center of it is coherent. It works as food. The demand for it is not a mistake or a failure of taste education. It is a genuine preference that has persisted across generations, across continents, across wide variation in who is doing the cooking and who is doing the eating.

Real demand is the thing that separates an invented dish from a gimmick. A gimmick generates interest and then fades. A dish with real demand generates imitation, regional variation, argument about whose version is correct, and eventually the kind of deep amateur knowledge where a regular at a restaurant notices when the kitchen has changed its spice balance. Chicken tikka masala is past all the early stages. It is in the argument stage, which means it has already won.

This is the same pattern visible in The Great American Biryani Belt — a dish that traveled, adapted to local supply chains and local palates, and ended up with regional American variants that are not inferior to the source but different from it in ways that matter to the people eating them. The travel is not contamination. The travel is how a dish proves it is worth keeping.

The Cooks Who Take It Seriously and What They Do Differently

The restaurants in the Bay Area where chicken tikka masala scores highest in our data share a set of observable practices. None of them are secret. Most of them are slow.

The chicken is marinated overnight, minimum, in yogurt and a spice paste that includes real cumin, real coriander, real turmeric, real garam masala ground in-house. It goes on a real tandoor, not an oven, not a grill. The char is real. The smokiness that comes off a properly tandoored piece of chicken is not a seasoning you can add later — it is a byproduct of high heat and live fire, and it is the structural anchor of the dish. Without it, you have creamy tomato chicken. With it, you have chicken tikka masala.

The sauce is built separately. Onions cooked down over a long time, not sweated but actually browned, which takes twenty to thirty minutes and cannot be rushed without changing the flavor. Tomatoes added and reduced until the oil separates, which is the visual signal that the base is done. Cream folded in at the end, not simmered, just warmed through. The dish comes together at the last moment. The chicken goes into the sauce only to be coated, not to continue cooking.

Zareen's. August 1 Five. Rooh. These are restaurants where the dish appears on the menu and where the kitchen is doing the slow version of the work. They are not identical restaurants — Zareen's is a counter-service spot in Mountain View with a $14 plate that the regulars will argue is the best in the region, Rooh is a tasting-menu-adjacent room in SoMa where the dish appears in a more formal context — but the underlying commitment to the tandoor and the long-cooked sauce is consistent across both.

The labor economics behind this are worth noting. A dish that requires overnight marination, a live-fire oven, and a forty-five-minute sauce construction is not a cheap dish to produce correctly. The price gap between the $14 version at Zareen's and the $26 version elsewhere is partly rent, partly service model, and partly the same labor compressed into a higher-volume operation where the margins only work if the kitchen turns tables fast. The economics of Indian food in the Bay Area are not straightforward — the labor is expensive, the expectations around price are calibrated to decades of underpriced Indian restaurants, and the tension between the two shapes what ends up on the plate. The piece on the all-day labor behind a $12 lentil crepe maps the same structural pressure across a different dish and reaches a similar conclusion: the price you pay is rarely the price of the work.

The Authenticity Trap and Why Serious Cooks Stopped Setting It

The word authentic has done a lot of damage to the conversation around Indian food in America. Applied to chicken tikka masala, it produces an impossible standard: a dish that developed in Britain cannot be authentic to India, but a dish that develops from Indian techniques and Indian ingredients cannot be dismissed as foreign imposition. The word collapses under the weight of the actual history.

The more useful question is not whether a dish is authentic but whether a cook is honest. An honest cook working with chicken tikka masala knows where the dish sits in the broader tradition, knows what the shortcuts look like and why they degrade the result, and makes choices based on what the food actually needs rather than what the customer will accept. An honest cook at a high-volume restaurant serving three hundred covers a night might make compromises that an honest cook at a thirty-seat room would not. The compromises are not dishonesty. They are the economics speaking.

What is dishonest is the restaurant that uses the name chicken tikka masala for a dish assembled from a commercial sauce base and pre-marinated chicken and presents it as equivalent to something made from scratch. The customer rarely knows the difference on a first visit. The regular always knows. The regulars are the real quality control in Indian restaurants, as in most ethnic restaurants in American cities — they are the ones who notice when the sourcing changes, when the kitchen takes a shortcut, when the dish that was the reason they came twice a week is no longer the same dish.

The Bay Area has enough Indian population with deep home-cooking knowledge to make this a real pressure on restaurants. A kitchen in Fremont or Sunnyvale or Santa Clara that cuts corners on its tikka masala is not cutting corners on a dish that only tourists order. It is cutting corners on a dish that the aunties at the next table have made at home a hundred times and know exactly how it should taste. That pressure does not guarantee quality. But it raises the floor in ways that are visible in the data.

What the Dish Actually Proves About How Food Crosses Borders

Chicken tikka masala is useful precisely because it makes the argument visible. Every dish that crosses a border gets renegotiated. The renegotiation is not a corruption of the original — it is how cuisines stay alive. A dish that cannot be adapted is a dish that cannot travel, and a dish that cannot travel stays in one place and eventually becomes a museum piece, something academics study rather than something people eat on a Tuesday.

The specific renegotiation that produced chicken tikka masala happened to be commercially successful in ways that amplified its spread and generated the origin argument. If the dish had stayed local — if it had remained a specialty of South Asian restaurants in the English Midlands without going global — nobody would be arguing about who invented it. The argument is a byproduct of the success, and the success is a byproduct of the dish actually working as food.

Bay Area Indian restaurants are currently in the middle of a second renegotiation. The generation of Indian-American chefs opening restaurants now — at Besharam, at Copra, at Rasa — is working with a different mandate than the generation that opened the first wave of sit-down Indian restaurants in the 1980s and 1990s. The first wave was translating Indian food for a Western audience. The second wave is doing something more interesting: it is making food for an audience that already knows what Indian food tastes like and is asking what comes next.

Chicken tikka masala does not disappear in this context. It sits at the table alongside the regional dishes and the experimental menus as evidence that the tradition is capacious enough to absorb an invented dish and make it real. The dish that started as a concession to a customer who wanted sauce on his chicken tikka is now the reference point against which every Indian restaurant in the country is measured, whether they serve it or not. That is not a small thing. That is how cultures actually work.