What Does “Eating Whole Foods” Actually Mean?

Somewhere along the way, “eating whole foods” started to sound like a second job.

Apparently, if you really care about what your family eats, you should be baking bread, fermenting yogurt, simmering chicken bones into stock, soaking dried beans overnight and making mayonnaise from scratch.

And listen—I’m a chef. I actually enjoy doing some of that stuff. But not all the time!

For most families, the choice isn’t between a perfectly homemade dinner and a slightly less perfect homemade dinner. It's more like cooking something palatable in 30 minutes and realizing at 6:15 that nobody has a plan and ordering takeout.

That’s why I think we need a more useful definition of what it means to eat a whole-food diet.

First, “processed” doesn’t automatically mean bad

Here’s where a lot of conversations about food go off the rails.

Almost everything we eat has been processed in some way.

Freezing vegetables is processing. Grinding wheat into flour is processing. Pasteurizing milk is processing. Turning cabbage into sauerkraut is processing. Canning tomatoes is processing.

Even chopping something changes it from its original state.

So telling people to “avoid processed food” isn't particularly useful advice.

What matters much more is what happened to the food, what was added to it, what nutritional value remains, and what role that food plays in your overall diet.

One commonly used system for thinking about this is called NOVA, which divides foods into four broad groups based on the nature and purpose of their processing.

At one end are unprocessed and minimally processed foods: vegetables, fruit, meat, fish, eggs, grains, nuts, plain yogurt and similar foods.

Then there are ingredients we use to cook those foods—things like oils, butter, sugar and salt.

Then there are processed foods made by combining relatively simple ingredients: cheese, canned vegetables, freshly made bread, canned fish and similar foods.

Finally, there are ultra-processed foods: industrial formulations that often contain ingredients or additives you probably wouldn't use when cooking the same thing at home.

That distinction is much more useful than simply dividing the grocery store into “good food” and “bad food.”

My definition of whole-food eating is simpler

I don't think your kitchen needs a rulebook.

My basic philosophy is this: Build most of your meals around foods that still resemble the ingredients they came from.

Vegetables. Fruit. Beans. Whole grains. Meat. Poultry. Seafood. Eggs. Nuts. Seeds. Cultured dairy. Herbs. Spices.

Then cook them into something delicious.

That's the foundation.

But that doesn't mean everything surrounding those ingredients needs to be made from scratch. Maybe you're roasting chicken and vegetables but using a good-quality jarred sauce. Fine.

Maybe you're making tacos with grilled fish, cabbage, avocado and salsa—but you bought the tortillas. Also fine.

Maybe tonight's dinner is whole-grain pasta, vegetables and ground beef with a jar of marinara because you got home late. I'm certainly not calling the food police.

The question I care about is whether the convenience product helps you build a good meal or whether the convenience product has become the meal.

That's an important distinction.

The ingredient list matters.

When I buy a packaged food, one of the first things I do is turn the package around.

The marketing on the front can say practically anything.

“Natural.”

“Protein packed.”

“Made with whole grains.”

“Keto friendly.”

“Plant based.”

Great.

Turn it around.

What's actually in it?

I'm generally looking for an ingredient list that makes sense for what I'm buying.

If I'm buying tomato sauce, I expect to see tomatoes, maybe olive oil, garlic, onion, herbs, salt and spices.

I don't expect tomato sauce to contain exactly what I would put in mine. A commercial product has different food-safety, manufacturing and shelf-life requirements.

But I do want to understand what I'm eating.

And ingredient count alone isn't enough.

A product isn't automatically unhealthy because it has twelve ingredients, and it isn't automatically healthy because it has three.

Context matters.

“Ultra-processed” is useful—but it isn't the whole story

There's good reason people are talking about ultra-processed foods.

Research has repeatedly found associations between diets high in ultra-processed foods and poorer health outcomes. One particularly interesting NIH-controlled feeding study found that participants eating an ultra-processed diet consumed more calories and gained weight compared with when those same participants ate a minimally processed diet—even though the diets offered were designed to have similar amounts of calories and major nutrients.

That's worth paying attention to.

But I also don't think “ultra-processed” should become the newest scary phrase we slap on everything in the pantry.

Food-classification systems have limitations. Depending on formulation and classification, foods that seem nutritionally quite different can end up wearing the same broad label.

That's why I still want to look at the actual food.

How much fiber does it have?

How much added sugar?

How much sodium?

Does it provide useful protein?

What's in the ingredient list?

What are we eating with it?

And maybe most importantly:

How often are we eating it?

There's a huge difference between using a packaged food to make Tuesday night's dinner manageable and building most of your diet around ready-to-eat industrial foods.

Convenience is not the enemy

This is the part I think gets lost in a lot of wellness culture.

Time is an ingredient too.

Families don't have unlimited amounts of it.

If buying frozen vegetables means vegetables actually make it onto the dinner table, I'm buying the frozen vegetables.

If canned beans mean we're having beans tonight instead of waiting until tomorrow because I forgot to soak them, open the can.

If a good jar of marinara turns a chaotic Wednesday into pasta, vegetables and meatballs around the dinner table, that's a win.

The pursuit of nutritional perfection can become its own kind of unhealthy relationship with food.

I would much rather help families develop a kitchen full of good, practical options.

That means learning where convenience makes sense and where making something yourself is actually worth the effort.

And that's something we're going to explore quite a bit here on Dad Man.

The Dad Man pantry test

When I'm deciding whether a packaged food deserves regular space in the kitchen, I tend to think about five things:

1. Does it still resemble food?

I want recognizable foods and ingredients doing most of the work.

2. Does the ingredient list make sense?

Not necessarily short. Not necessarily perfect. Just reasonable for what the product is.

3. Does it bring something useful to the meal?

Protein, fiber, whole grains, vegetables, healthy fats—or simply enough convenience to help get a homemade dinner onto the table.

4. Does it taste good?

This one apparently became controversial somewhere along the way.

I'm a chef. Food should taste good.

If the “healthy” version tastes like cardboard, nobody in your family is going to eat it, and we've accomplished nothing.

5. Does it make real life easier?

This matters.

A product that saves 20 minutes on a school night may have genuine value even if I could technically make a better version myself.

That framework is going to become a big part of the Product Reviews here on Dad Man.

I'll be digging into the packaged foods families actually buy—sauces, breads, tortillas, yogurt, crackers, snacks, frozen foods, condiments, broths and plenty more—to answer a pretty simple question:

Would I put this in my own kitchen?

Sometimes the answer will be yes.

Sometimes it'll be “in a pinch.”

And sometimes we're putting it right back on the shelf.

So what does eating whole foods actually mean?

To me, it means making whole and minimally processed foods the foundation of how we eat without pretending modern families have unlimited time.

It also means recognizing that there isn't one perfect way to eat.

Mediterranean. Paleo. Keto. Plant-based. Carnivore. Low-carb. High-protein. Anti-inflammatory. Every few years—and sometimes every few months—there seems to be another diet promising to be the answer.

We're going to talk about those diets here. We'll look at the research, separate useful ideas from the hype, and figure out which principles might actually deserve a place in the way we feed ourselves and our families.

But Dad Man isn't going to be a diet.

The recipes and meal plans I'm building start from a gluten-free, dairy-flexible foundation, with an emphasis on whole foods, plenty of plants, quality proteins, good fats, fiber and ingredients you can actually recognize.

And here's the important part: Nobody at the dinner table should feel like they're eating “health food.”

I'm a chef first. If I'm going to ask you to cook something for your family, it needs to deliver. Big flavor. Great texture. Food people actually get excited about eating.

The goal isn't to make a “healthy version” of dinner that everyone politely tolerates.

The goal is to make a great dinner that happens to be built from really good food.

Sometimes we'll use dairy. Sometimes I'll show you how to make the same recipe without it. Sometimes we'll borrow ideas from Mediterranean cooking. Other times we might use something we learned from a high-protein, plant-forward or lower-carb approach.

We're going to take the good ideas and leave the dogma behind.

Cook vegetables.

Eat fruit.

Use beans and whole grains.

Buy high-quality meat and seafood when you can.

Cook with real ingredients.

Read labels.

Pay attention to added sugar, sodium and fiber.

Learn a handful of meals you can make without thinking too hard.

And find a few convenience foods you trust.

Most importantly, don't let the pursuit of a perfect diet make feeding your family harder than it needs to be.

Because I don't think we need more anxiety around food.

We need better systems for putting really good food on the table.

And that's really what Dad Man is about.

Dinner's about to get easier.

I'm building a new Dad Man around one simple goal: taking some of the work out of feeding your family.

Coming soon are chef-created recipes, 52 weeks of family meal plans, organized shopping lists, prep guides, product reviews and practical advice for making good food work in real life.

Join the Dad Man newsletter to get new articles and recipes—and be the first to know when the Dad Man Kitchen Club opens.

And don't worry. I'm not going to ask you to make your own mayonnaise.