Lily Hayes

My Story

My grandmother kept a green recipe box on top of her refrigerator. It held index cards in her handwriting — smudged, stained, annotated in the margins — and every single recipe in it worked. She made a pot roast every Sunday that I have been trying to recreate for fifteen years. I’m close. Not there yet. That chase is what made me a serious cook.

I studied culinary arts formally and spent several years working in professional kitchens before leaving to focus on recipe development full-time. What those years gave me wasn’t prestige — it was repetition. Making the same sauces hundreds of times teaches you things you can’t read in a book. You learn what temperature sounds like, what properly emulsified looks like, what almost-done smells like.

I founded Recipe Gap in 2019 because I kept seeing the same problem online: recipes that looked beautiful in photos but fell apart in real kitchens. Instructions that assumed equipment nobody owns. Timing that only worked if you were already an experienced cook. I built this site to close that gap — to write recipes that work for real people in real kitchens, the first time they try them.

My husband James is a landscape architect who cooks exactly one thing: scrambled eggs, and only on weekend mornings. He is, however, an excellent eater — he finishes everything, says almost nothing, and then asks casually if there’s more. When James reaches for seconds without commenting, I know the recipe is done. When he pushes something to the edge of his plate, I go back to the notes.

We have one daughter: Nora, age 8. Nora’s current food philosophy is that everything is better with cheese and that soup should not have visible vegetables. She has softened slightly on carrots. Testing recipes with Nora in the kitchen means something will spill, something will get knocked off the counter, and at least once I’ll hear “Mom, is this supposed to smell like that?” — which is usually a useful signal.

My biggest kitchen failure happened in year two of the blog. I published a slow cooker chicken recipe that I had tested successfully three times. A week after it went live, my inbox was full of readers telling me it had turned out watery, bland, and wrong. I made it twelve more times before I found the problem: my slow cooker ran hotter than average, and I had never accounted for that variable. I pulled the post, fixed it, and added a temperature note that has been in every slow cooker recipe I’ve written since. That failure changed how I test.

Two things always live on my counter: a well-seasoned wooden spoon I’ve had since culinary school — it belonged to a chef instructor who gave it to the student he thought would actually keep cooking — and a bottle of good apple cider vinegar. A teaspoon of cider vinegar at the end of almost any savory dish pulls the flavors into focus in a way that’s hard to explain until you’ve tried it. I use it more than any other finishing ingredient.

I taste every recipe at three points: during cooking to build the base seasoning, just before serving to make final adjustments, and cold the next morning straight from the refrigerator. The cold taste is the one I trust most. It tells you whether the flavors are genuinely layered or whether they were just masked by heat.

One opinion I will defend to anyone: the instruction “season to taste” is the laziest phrase in recipe writing. It tells you nothing about how much, when, or what you’re tasting for. Every recipe on this site has specific seasoning guidance because “season to taste” is where most home cooks get lost, and getting lost at that step means the whole dish underperforms.

How I Develop Recipes

Every recipe on Recipe Gap starts the same way: I cook it until it fails. I find every way it can go wrong — wrong temperature, wrong timing, wrong substitution — and then I write the recipe around those failure points. The troubleshooting notes in my posts aren’t theoretical. They come from actual failures during testing.

I test every recipe a minimum of four times before publishing. At least one test is done under unfavorable conditions: rushed timing, a substituted ingredient, an oven I’m not used to. If a recipe only works when everything goes right, it isn’t ready for this site.

Recipe Gap has published over 800 tested recipes since 2019. Every single one has been made in a home kitchen, using equipment and ingredients that any home cook can find at a standard grocery store.

What You’ll Find Here

Recipe Gap is organized around one idea: the gap between recipes that look good and recipes that actually work. Every post on this site is written to close that gap — with specific instructions, honest troubleshooting, tested substitutions, and the kind of detail that only comes from making something go wrong first.

You’ll find weeknight dinners that come together in under an hour, weekend projects worth the extra time, seasonal recipes built around what’s actually at peak flavor, and baking recipes with the kind of precise ratios that make the difference between something that works and something that doesn’t.