Hunger isn't about food

Ask most people why anyone goes hungry and they'll describe a shortage. Not enough food, not enough money, not enough help. It's an intuitive story, and it's almost entirely wrong. The United States produces a staggering surplus of food. We throw away tens of millions of tons of it every year. The problem was never that the food doesn't exist. The problem is that the systems to move it to the people who need it — reliably, on time, and without humiliation — mostly don't.

That's not a supply problem. That's a distribution problem. And distribution is just another word for design.

The shortage story is convenient

The shortage story is comforting because it lets us off the hook. If hunger is a lack, then generosity is the answer, and generosity is something we already know how to feel good about. We hold the food drive. We write the check. We volunteer on a Saturday. The need is enormous and our gesture is small, so we conclude that the gap is simply too big to close — and we go home.

But if hunger is a design failure, the conversation changes completely. Design failures aren't closed by generosity. They're closed by engineering. You stop asking "how much can we give?" and start asking "why does the need keep regenerating, and what would it take to build something that meets it every single week without anyone having to perform their desperation to qualify?"

The resources to solve the problem are almost always already in the room. What's missing is the infrastructure to connect them.

What we built instead

When we started Dion's Chicago Dream, the temptation was to build a bigger pantry. More shelves, more cans, longer lines. We did the opposite. We treated it as a logistics question: given that fresh food exists somewhere in this city today, what is the most reliable, most dignified way to get it to a family's door by the end of the week? Routes. Partners. Data. A standard of care that assumed our neighbors were customers, not cases.

The result moved millions of pounds of food and served thousands of households a week — but the number I care about most is a different one: how little of it depends on me being in the building. A pantry is a place you have to keep showing up to. An infrastructure is a thing that keeps working whether or not you do. That distinction is the whole game.

Dignity is a design specification

Here's the part that gets left out of the shortage story: how food reaches someone matters as much as whether it does. Make people wait in a visible line, ask them to prove they're poor enough, hand them whatever's left over — and you've delivered calories while taking something else away. Dignity isn't a nice-to-have you add at the end. It's a specification you design for from the start, the same way you'd design for cost or speed.

That's why I keep saying the work was never about food. Food is just the clearest example of a pattern that shows up everywhere: scarcity in the middle of abundance, produced not by accident but by systems doing exactly what they were built to do. If we don't like the outcome, the honest response isn't more good intentions. It's a redesign.

Hunger isn't about food. It never was. It's about whether we're willing to build the systems that match the abundance we already have.