Big resolutions are overrated. This year, we’re all about highly doable improvements we can pull off any day. In Small Change, Big Impact, we're making tiny tweaks and sharing the results. Follow along, join in, and let us know what other small changes you’re making this year.
At the start of every year, it’s easy to have all sorts of cooking and eating resolutions: try a new recipe every week; eat less meat; become a meal-prep master. One resolution I always have: bring my lunch to work. I’ve written about it before and devised plenty of strategies to make it happen.
By the time August rolls around (okay, May), I’m back to buying lunch most days, with a brought-from-home sandwich or leftovers occasionally thrown in. And it’s fine, I don’t beat myself up over it. But when the Food52 team discussed this idea of skipping big resolutions in favor of little changes this year, lunch definitely felt like a good place to start.
I asked myself: What would make this time different from all the homemade lunch promises I had made myself in the past? And how would I keep it as minimally demanding as the task at hand requires? Enter Catherine Seaver.
Last year, Catherine reached out to our resident Genius, Kristen, about something truly genius she does: Since 2015, Catherine’s family has been trading dinners with four other families. As in, each family makes one dish in a portion enough to feed 20 people, then divides up the food into five batches so that every family can have a week’s worth of meals. (The whole thing's truly amazing, and you can read more about it here.) Each family only has to cook once (though, admittedly, they cook an enormous quantity!), but has dinner—more specifically, a different dinner—every night of the week.
Particularly valuable for families with small children, or too little time to prepare a brand-new dinner every night, this system of cooking and sharing is really inspiring, if a little daunting. A small change it was not, but I wondered: Could it be adapted somehow to make bringing lunch to work a little easier?
When I chatted with Catherine over the phone, she not only had ideas about how I might adopt a similar strategy, she immediately gave me helpful tips that made the whole thing feel doable.
When I suggested a giant lunch swap the whole editorial team could try together, Catherine cautioned against making it too big (it’s supposed to be a small change, right?). When she first started her dinner village, it was just her family and one other; only gradually did they expand to five families. So we landed on experimenting with just two people—me and Brinda, our managing editor. The initial plan was that we’d each make a big batch of just one dish and alternate eating the two for lunch all week.
Few things are more personal than cooking for another person, so getting on the same page in terms of likes, aversions, allergies, and other dietary restrictions is really important. Does anyone have food issues to be aware of? Make sure these are discussed from the outset. For our lunch swap, I was already aware that Brinda is a vegetarian, but at the time, she was also eliminating certain foods (like dairy, gluten, soy, and eggs) from her diet to test for allergies. What I cooked needed to meet these requirements. Sounded easy enough, but discussing it ahead of time was critical to the success of our experiment.
Another important thing to agree on: how long you’ll swap meals for. Is this a one-week thing, or something that could be ongoing? Also be sure to communicate your meal plan. What are you each thinking of making? If you weren’t a meal planner before, now’s your chance to start.
Brinda and I brainstormed a bit the week before we started this experiment, then confirmed the menu on Sunday. My idea was to make mujadara with some kind of green vegetable (after checking with Brinda, I eventually decided on zucchini), and a Thai-style curried sweet potato and lentil stew I’d been wanting to try. Independently, Brinda was thinking about either a coconutty dal (leftovers from the big batch she made that weekend) or a quickie chana masala (since she had the time, she decided on both).
Upon comparing recipe plans, we realized we were both proposing pulse-based dishes. But since the flavors and cooking styles were different enough, we agreed this would be fine for the week. If we continued our swapping into the future, we decided it would be good to avoid using the same ingredients next time around, so we wouldn’t be eating the same thing (lentils, in our case) for a week straight.
This doesn’t have to be the most elaborate cooking project you’ve undertaken in your life. Pick tried-and-true dishes you love eating, or a simple new recipe you’ve been meaning to make. Little flourishes or garnishes are a nice touch, but certainly not required. Sharing something delicious is really where it starts and ends.
In Brinda and my case, we both went with recipes that we were familiar with: For me, I chose a favorite from Lucky Peach Presents Power Vegetables!, and that new lentil recipe I knew would work well in big batches. Brinda opted for standbys that she already cooks once or twice a month (she went off book for this experiment, but the recipes were pretty similar to this coconut dal and this chana masala).
Overall, I think Brinda and I were both pretty pleased with how our lunch experiment went. It required a little extra planning, but proved worth it—impactful, even—during a particularly busy week at work. Plus, Brinda is an excellent cook, so it was doubly rewarding. Could I really make it a regular thing for the rest of the year? With a willing companion, I think so.