It happens at least once a week in our kitchen. I pull a sheet pan from the oven, or tilt a skillet toward a waiting bowl, and my partner looks over and asks, reasonably enough, what I’ve made. And I stall. ‘It’s, uh, that thing with the chickpeas and the greens that were about to turn, and I threw in some of the cilantro before it got slimy, and there’s lemon, and I toasted those seeds from the back of the cupboard.’ What I mean is dinner. What I say is a nervous list of evidence. What we end up calling it, after a beat of mutual confusion, is ‘the chickpea thing.’
That name does nobody any favors. It undersells the meal before a fork touches it. It erases the thinking—the quick decision to bloom cumin in oil, the last-minute handful of walnuts for texture, the grate of garlic that happened while the water was coming to a boil. It makes the cook feel like they produced an incident rather than an answer to the question what are we going to eat? And honestly, it makes the eater a little less excited. Words matter, even when nobody’s writing a menu.
We wouldn’t introduce a friend as ‘the person from the thing.’ We wouldn’t describe a book we loved as ‘that story with the detective and the fog.’ A name—even a simple one—frames how we experience what’s in front of us. So why do we let our cooking go nameless or, worse, apologize for it with a shrug and a mumble?
How a Dish Gets Named in a Real Kitchen
Restaurants have a whole machinery for naming food. There are consultants who specialize in menu language, people paid to decide whether a dish sounds rustic or refined, approachable or aspirational. Home cooks have none of that, which is mostly a relief. But it also means we default to the ingredients list or the recipe title we found online, even when we’ve changed half of it. ‘I made Melissa Clark’s lemony chickpea stew’ feels weird when you used no lemon and added coconut milk because that’s what you had. So we say nothing, or we say ‘chickpea thing.’
The alternative isn’t to start naming our Tuesday stir-fry like a tasting menu. We don’t need ‘Hand-Torn Greens with Cultured Butter and Allium Confit’ when we mean ‘wilted spinach with butter and garlic.’ But there’s a middle ground—a way to name food that’s honest, inviting, and rooted in what actually happened in the pan. It starts with noticing what the dish is about, not just what’s in it.
Take that chickpea situation. When I pause and think about what made it work, I realize the whole thing hinged on the fact that I toasted coriander and cumin seeds in oil before adding anything else. The kitchen smelled warm and earthy, and that base note carried through the wilted chard, the softened onion, the chickpeas that had been hanging out in the fridge since Tuesday. The lemon went in at the end, because acid always wakes things up. So maybe it’s ‘Cumin-Toasted Chickpeas with Whatever Greens You Have.’ That tells you what to expect. It tells me what I did. It sounds like something I’d order, but also something I’d make on a Thursday when I’m tired.
The Parallel Nobody Talks About: Naming Food and Naming Stories
Here’s where things get unexpectedly resonant. A while ago, I was watching a writer friend struggle to name her novel-in-progress. She had a stack of index cards with words like salt, inheritance, river, fracture. She moved them around on her kitchen table while her soup cooled. She said, ‘I know what the book is about. I just can’t find the two or three words that hold it.’ I nodded, because I’d just spent ten minutes trying to name a lentil soup that had smoked paprika and a parmesan rind I’d been saving in the freezer. Same problem, different scale.
The creative muscle that names a dish is not so different from the one that names a poem, a painting, or a book. It’s about finding the core—the one thing the work is actually saying or doing or tasting like—and letting that lead. A novel called The River Between Us promises something different from River alone. A soup called ‘Smoky Lentil Soup with Parmesan Broth’ tells you why it’s good. ‘Lentil soup’ just tells you what it is. Both are fine, but one invites you in.
Writers, especially those working on long projects, often turn to structured brainstorming when they’re stuck on a title. They’ll use tools that generate book title ideas—not because they expect a machine to name their life’s work, but because seeing a hundred possibilities shakes something loose. A phrase like ‘The Last Season’ or ‘What the Fire Left’ might not be the final title, but it points toward the emotional register the writer was circling. In the same way, a home cook staring at a colander of greens and a half-block of feta can borrow that approach. What’s the mood here? Is this dinner bright and sharp, or slow and quiet? Is it a Tuesday rescue mission or a Saturday project? The answer often contains the name.
The Reedsy Book Title Generator works exactly like this: it’s a free, infinite bank of titles that writers can sift through, not to copy, but to trigger their own thinking. The tool doesn’t know your book, but it knows the shapes titles can take—lyric, declarative, enigmatic—and seeing those shapes helps you recognize the one that fits. Naming a dish can work the same way. If I tell you ‘Crispy Rice with Ginger and a Runny Egg’ is a possibility, suddenly you see that the runny egg is the point, not an afterthought. The name guides you.
And just as writers sometimes use a Character Name Generator to spark a personality—a name like ‘Maren’ or ‘Cyrus’ carries a certain weight, a certain era—cooks can use the same associative logic. ‘Tarragon Chicken’ feels French and slightly fancy, even if it’s just chicken thighs with a handful of tarragon from the garden. ‘Chicken with Herbs’ feels like a default. The difference is one word, but it changes how you cook it and how you serve it.
Why We Should Name Our Meals (Even When Nobody’s Listening)
There’s a practical reason to name what we cook, and it has nothing to do with impressing anyone. A name is a memory anchor. If I call something ‘that lentil thing,’ I will never make it again, because I won’t remember what I did. If I call it ‘Smoky Lentils with Charred Onion and Yogurt,’ I’ve created a tiny mental recipe card. I’ll remember to char the onion next time. I’ll remember the yogurt. I’ll remember that it took twenty-five minutes and made the whole kitchen smell like a wood-fired oven.
There’s also an emotional reason. Naming a dish is an act of claiming it. It says: I made this. I figured this out. This came from my hands and my brain and the half-bag of spinach that was not going to last another day. That’s worth acknowledging, even if you’re the only one who knows. Especially if you’re the only one who knows. So much of home cooking is invisible labor. Naming it makes it visible, at least to ourselves.
And then there’s the way a name shapes the eating. If I tell you we’re having ‘Pasta with Sardines and Breadcrumbs,’ you might brace yourself. If I say ‘Spaghetti with Crispy Lemon-Herb Breadcrumbs and Sardines,’ you hear the crunch first. You hear the lemon. The sardines are still there—I’m not hiding them—but they’re part of a whole, not the headline nobody asked for. That’s not manipulation; it’s just accurate description with better PR.
A Small, Unpretentious Guide to Naming Your Dinner
You don’t need a system for this. But if you’re stuck, here’s what I’ve learned to ask myself:
What did you do first? Often the first step in the pan becomes the name. ‘Garlic-Rubbed Toast with Tomatoes.’ ‘Cumin-Fried Potatoes.’ ‘Seared Broccoli with Soy and Sesame.’ The technique announces the flavor.
What’s the thing that makes it work? Maybe it’s the finishing oil, the handful of herbs, the splash of vinegar at the end. ‘Radicchio Salad with Walnuts and Sharp Cider Vinegar.’ The vinegar is doing the heavy lifting; name it.
What season is it? Seasonal naming is honest and useful. ‘Early Summer Squash with Basil and Burrata’ tells you when to make it. ‘January Citrus and Fennel Salad’ makes sense of a winter counter. The calendar is part of the recipe.
What’s the texture? Crispy, creamy, brothy, charred, smashed, torn. These words are free and they do a lot of work. ‘Charred Green Beans with Garlicky Yogurt’ sounds like a plan. ‘Green Beans with Yogurt’ sounds like a compromise.
What’s the mood? Some meals are Tuesday meals. Some are Sunday meals. ‘Quick Black Bean Soup with Lime’ is a Tuesday name. ‘Slow-Braised Pork with Orange and Chile’ is a Sunday name. Both are good; one takes longer.
When the Name Changes the Cooking
Here’s a concrete example from last week. I had a head of cauliflower, a jar of capers, some flat-leaf parsley that was starting to yellow, and a lemon. I could have made ‘roasted cauliflower’ and called it a day. But I decided to call it—at least in my own head—‘Crispy Cauliflower with Brown Butter, Capers, and Lemon.’ The name forced me to actually brown the butter, not just melt it. It made me wait until the cauliflower was truly crisp-edged, not just steamed-soft. It reminded me to chop the parsley at the last minute so it would stay bright. The name was an aspiration, but a reasonable one. It took maybe five extra minutes of attention and made a vegetable feel like a centerpiece.
That’s the quiet power here. Naming isn’t about pretending your kitchen is a restaurant. It’s about paying enough attention to what you’re doing that you can describe it honestly, and then letting that description guide you back to it later. It’s the difference between cooking as a series of tasks and cooking as a practice you can build on.
The Thing to Remember
You already know how to name things. You name your pets, your playlists, your houseplants, the group chat that’s been going since 2019. You name the leftovers you put in the freezer (‘soup for a bad day’). You name the cocktail you invented that one summer (‘the thing with the mezcal and the watermelon’—okay, maybe you need a little help with that one). The point is, you have the instinct. It just gets buried under the assumption that naming food is pretentious or unnecessary.
It’s not. It’s an act of care. It’s a way of saying this meal mattered enough to remember. And the next time you pull a sheet pan from the oven and someone asks what you made, you can say, ‘Cumin-Roasted Carrots with Yogurt and Pistachios,’ or ‘Spicy Greens with Crispy Chickpeas,’ or even just ‘Tuesday pasta, the one with the lemon.’ You’ll watch their face change. And you’ll feel, for a second, like the person who made exactly the thing they meant to make.
Try this tonight: Before you serve whatever you’ve made, give it a name—out loud, even just to yourself—that includes one texture word and one flavor that actually happened in the pan. See if it changes how you eat it.