My parents had one move for a kid who wouldn’t eat. Wait him out. When he gets hungry enough, he’ll eat. It worked on me. Or at least it worked enough that I internalized it as the way you handle a kid at the table.

So when my son started refusing food, I tried it. I made dinner. He wouldn’t eat. I left it on the table. He still wouldn’t eat. I figured hunger would do what I couldn’t. Hours passed. He went to bed without eating. And I sat there looking at a full plate of cold food and realized the playbook I’d inherited was built for a kid who doesn’t exist in my house.

He didn’t eat because he couldn’t. He refused to the point where it stunted his growth. ARFID doesn’t bend under pressure. Hunger makes it worse. The more distressed he gets, the narrower the window of what he can tolerate. I was playing chicken with a constraint I didn’t understand yet, using a strategy designed for a neurotypical relationship with food.

That was the night the old approach broke. I stopped trying to make him eat and started trying to figure out what eating actually looks like for him.

Here is a good day without the system in place. This is what functional looks like when you’re running it all in your head.

The dread starts around 3:30. I’m still working, still in code or meetings, but the dinner clock is already ticking in the back of my head. I don’t have a plan. I don’t know what’s in the fridge. I haven’t ordered groceries and it’s too late for delivery. So now I’m trying to finish my work while half my brain is running a parallel thread on what two kids with incompatible diets are going to eat in two hours. Neither thing gets my full attention. The work suffers because I’m stressing about dinner. The dinner planning suffers because I’m trying to squeeze one more thing into the daily build.

By 5 PM I launch out of my chair in a panic. The executive function budget is spent. Whatever I had for sequencing and planning got allocated hours ago, and the last hour and a half of it went to the dread, not the work.

I check on the kids. Make sure nobody needs anything urgent. Then I walk to the kitchen and start by resetting it, because the kitchen is never clean at 5 PM. Dishes from lunch, from snacks, from whatever got left on the counter. I clear surfaces and wash what’s in the sink so I have somewhere to work.

Then I figure out what each kid is eating tonight. My son’s list. My daughter’s list. What’s in the fridge. What’s missing. Most days, something is missing. So I drive to the store. This is 5:30 now, maybe 5:45. I get what I need, drive back, unload, and start cooking. Two separate meals, usually, because the constraint profiles don’t overlap enough for one. I get both on the table. The kids sit down, both with iPads in front of them.

Then I eat, if I managed to make something for myself. Standing, usually. Or I grab whatever is left.

While they’re finishing I drive back to the store to pick up a salad for my wife. She eats lighter than the rest of us, doctor’s orders, and the kind of salad ingredients she needs don’t survive in our fridge. They rot before we use them because the kids’ food has always been the priority. Getting her meal figured out has been the last thing on the list for a long time. We haven’t solved it. The greens go bad, the prepped salads are expensive, and the logistics of keeping fresh salad components stocked when you’re already running two separate dinner operations just hasn’t risen above the waterline.

I get home. Clean up dinner. Get the kids moving toward showers and bed. That’s the sequence. On a day when nothing goes wrong.

Things go wrong.

The meal is slightly outside what my son expected. The texture is different. The brand changed. Something about it is off in a way I can’t see but he can feel. He won’t eat it. My daughter picks up on the tension and they start going at each other. On bad nights this has escalated to screaming. On the worst nights, to physical aggression.

Or I wake up without enough capacity to set any of this up. I don’t have the spoons to plan, to shop, to sequence the cook. Those days, there is no system. There’s just me standing in a kitchen at 5 PM with nothing defrosted and no plan and two kids who need to eat in the next hour.

The difference between a functional evening and a disaster is whether the structure was in place before I got to the kitchen. Once I’m standing there dysregulated and empty, I can’t build it in real time. The decisions are too many and the stakes cascade too fast. No plan means a store run, which means dinner is late. The kids get hungrier, their sensory tolerance drops, and by the time food hits the table my son can’t eat it. The evening collapses from there.

My son hates eating. I want to be clear about that because people hear “won’t eat” and think “picky.” He doesn’t enjoy food. He doesn’t look forward to meals. Eating is a task he endures.

He eats with an iPad in front of him. The screen is an accommodation. The distraction is what lets him get food in. Without it, the sensory experience of eating is front and center and the whole thing stalls. With it, his attention is somewhere else and the food goes in almost mechanically.

I spent a while feeling guilty about that. A kid eating dinner in front of a screen looks like lazy parenting from the outside. But from the inside, the iPad is the thing that gets 400 calories into a child who would otherwise eat nothing. I stopped caring what it looks like.

When the system is in place, 5 PM is different.

The building blocks are already in the fridge. The batch cook happened on Sunday. Rice for my daughter. Proteins prepped to my son’s specs. Sous vide bags ready to reheat. Gluten-free options already separated. I walk into the kitchen and assemble instead of inventing.

The stress is gone. No store run, no standing in front of the fridge trying to figure out what everyone can eat. The decisions were made three days ago when I had the capacity to make them. Tuesday me doesn’t have to be strategic. Tuesday me just has to be functional enough to open the fridge and heat things up.

That’s the difference the system makes. It moves the hard cognitive work to a time when I can actually do it and leaves the execution for the part of the day when I can’t.

But I want to be honest about this. The system doesn’t fix me.

There are days where I wake up and I don’t have the capacity to set the system up. The batch cook didn’t happen. The fridge is empty. I’m starting from zero at 5 PM with nothing in reserve. On those days, the system is just an idea I had last week that didn’t survive contact with this week.

I think people imagine that once you build the system, you’re done. Like it’s a machine you turn on. It’s not. It’s a practice, and the person practicing it has the same constraints the system was built to accommodate. I’m the cook and I’m the one whose executive function runs out before dinner starts. The system was designed around those limits, and some days they’re lower than what I planned for.

What the system changes is the floor. On a day when everything works, dinner is calm and nobody goes to the store and everyone eats. On a day when nothing works, the infrastructure from last week’s batch cook might still have something in the fridge I can fall back on. The worst case is less bad. But it still happens.

The salad is the part I haven’t solved.

My wife needs different food than the rest of us. She eats for her health. The kids and I eat calorie-dense, fat-packed meals because that’s what their profiles need and what I can build a system around. She needs lean, fresh, vegetable-forward food. And the logistics of keeping salad ingredients fresh in a house where the entire kitchen system is oriented around batch-cooked proteins and shelf-stable components, I haven’t cracked that.

The greens rot. The cherry tomatoes go soft. The prepped ingredients from the store last two days and then they’re compost. I end up driving to a salad shop at 7 PM because the at-home version keeps failing.

I’m being honest about this because the system isn’t done. The kids’ food came first because the stakes were highest. My own nutrition came second, and it’s still inconsistent. My wife’s meals came third, and they’re still mostly manual. There’s a triage order to how this got built, and it reflects where the crises were loudest, not where the need is greatest.

I’ll figure it out. I think the answer is something about smaller, more frequent produce runs, or a different storage approach, or maybe a separate mini-system just for salad components. But right now it’s the gap in the system that I work around every night, and I’d rather say that than pretend the whole thing is seamless.

The system is a work in progress. Some parts are solid. Some parts are held together with duct tape and a second trip to the store. But my wife eats better than she did six months ago, and both kids eat dinner most nights without a meltdown, and that’s enough to keep me working on the parts that aren’t there yet.