How to Meal Plan When Someone Says "I'll Cook If It's Easy"

Nearly every household has a version of this conversation. One person does most of the planning and cooking. The other is willing to help — genuinely willing — with one quiet condition: "I'll cook, if it's easy."

It's easy to hear that as a lack of enthusiasm. It usually isn't. It's a completely reasonable statement about effort. This person will happily get dinner on the table on a Wednesday, as long as doing so doesn't require reading a recipe with fourteen steps, dirtying every pan in the house, and improvising a technique they've never done. Ask them to do that after a full workday and, understandably, the answer is takeout.

The mistake most meal plans make is treating everyone as the same cook on every night. They plan by recipe and hope the effort works itself out. But in a house with a reluctant cook, effort is the variable that decides whether the plan survives contact with a Tuesday. Plan around that, and the reluctant cook becomes a reliable one.

Effort is a real dial, not a personality

Start by dropping the framing that someone is "not a cook." Almost everyone will cook at a low enough effort level. The question isn't whether they'll cook — it's where their line is.

Think about meals as sitting on an effort dial:

• Simple: few ingredients, one pan, hard to get wrong, minimal cleanup. Assembly more than cooking. This is the reluctant cook's whole comfort zone — and it's most weeknights for everyone.
• Standard: a normal recipe, a few components, 30–40 minutes, some multitasking. Fine for the confident cook on an average night.
• Involved: multiple techniques, longer times, a sink full of dishes. A weekend project, not a Wednesday.

The reluctant cook isn't refusing to cook. They're refusing to cook at Involved on a weeknight — which is a preference the confident cook usually shares and just powers through. Once you see it as a dial, you can set it deliberately instead of hoping.

Match the effort to the cook and the night — both

Now assign meals with two questions, not one: who's cooking, and how much do they have in the tank tonight?

• Nights the reluctant cook has dinner: keep it firmly at Simple. This is non-negotiable, and it's the whole game. A Simple meal they'll actually make beats a Standard one they'll bail on. "Boring but cooked" wins every time over "interesting but ordered in."
• Nights the confident cook is home and has energy: Standard, or an Involved meal if they want the fun of it.
• The tired nights, whoever's cooking: Simple, always. Nobody does Involved on fumes.

Notice what this does to the dynamic. Dinner stops being a nightly negotiation — "can you handle Thursday?" met with a wary "...what is it?" — because Thursday was already planned as something they can obviously handle. You've removed the reason to say no.

Keep variety without adding effort

Here's the fear that keeps people from planning this way: if half the week is "Simple," won't we eat the same four boring things forever?

Only if you let "simple" mean "the same." Simple is a constraint on effort, not on variety. A one-pan lemon-garlic chicken, a black-bean quesadilla, a quick shrimp stir-fry, and a sheet-pan sausage-and-peppers are all Simple — and all completely different dinners. The trick is having a deep enough bench of low-effort meals that "easy" never has to mean "again."

That's the real work of planning for a reluctant cook: not lowering your standards, but building a wide rotation of genuinely easy meals so the effort stays low while the food stays interesting.

Let the reluctant cook own their nights

One more move that pays off: when the plan reliably hands the reluctant cook meals at their effort level, they can actually own those nights — shop for them, start them, finish them — without the planner hovering. That's how the load actually gets shared instead of just talked about. A plan that respects the effort ceiling is what makes a second cook possible at all.

The honest problem with doing this manually

Doing this by hand means holding a lot in your head every week: who's cooking which night, how tired everyone's likely to be, which of your meals are genuinely Simple versus secretly a 40-minute affair, and keeping enough easy variety that nobody notices it's easy. That's a real amount of juggling — and it's the planner doing even more invisible work to make someone else's cooking easier. Which is a little unfair, and it's usually the reason people stop.

That's the lever we built into Eat Roostly.

Roostly has a cooking-effort dial — Simple, Standard, Involved — so you can set how much work a plan should ask for. Tell it "keep this week simple" and you get a week of low-effort meals your reluctant cook will actually make, with enough variety that it never feels repetitive. Turn it up for a weekend you feel like cooking. Because Roostly also plans around your real schedule, it already keeps the busy nights easy on its own — and every plan is still filtered for everyone's allergies and tastes. The effort ceiling becomes something you set on purpose, not something you fight over at 6pm.

The insight in this article is the right one: plan around effort, not just recipes. Roostly just turns that into a dial you can actually set.