top of page

The Blind Spot of Food: Designing to Understand How We Really Eat

  • Writer: Héctor Mendoza
    Héctor Mendoza
  • Jan 4
  • 2 min read

Updated: Aug 20

There is something curious—and a little worrying—about the way we talk about food today:

No one has a complete picture of how we are actually eating.

There is plenty of data. Isolated metrics. Fragmented reports about consumption, sales, trends, and nutrition.

But we still don't have a clear, everyday view of what might matter most: the real decisions we make around food every single day.

What We Can't See

We know how much gets sold. We know what people order for delivery. We know what's trending.

But we don't know:

  • what someone decides to cook when they get home tired

  • how time, budget, and mood shape that decision

  • when someone chooses to order food and when they choose to cook

  • what we repeat out of habit and what we choose with intention

That gap is a massive blind spot.

And it is precisely where many of the decisions live that affect our health, our time, our relationship with food—and, of course, the products and services we might need.

Food as a Channel

Eating is a primary need.

It isn't optional. It isn't aspirational. It isn't a trend.

And yet, the digital world still hasn't built a real channel that can coexist with this need in a continuous and respectful way.

My vision—and the reason behind my projects—is to help build and strengthen that channel.

Not to control it, but to accompany it.

To create a system that lives alongside everyday food decisions:

  • when you decide to cook

  • and when you decide to order

A channel—or perhaps a bridge—built in the digital world to help us understand, choose, and repeat a little better.

Connecting Decisions, Not Imposing Rules

This isn't about telling people how to eat.

It's about making visible the decisions that are already happening.

Designing tools that help us answer simple questions:

  • Why did I eat this today?

  • What influenced that decision?

  • What worked for me, and what didn't?

The goal is to create a first, clearer picture of what's actually happening.

Not through judgment, but through observation.

Because we can only measure what we begin to understand. And perhaps only then can we improve it.

Designing Systems That Listen

My projects exist for that reason:

To listen without invading.

To record without imposing.

To connect without replacing the human experience.

Food doesn't need more noise. It needs context.

Designing that context—using data, intuition, and real life—is the work I am building.

Not as a definitive answer, but as a living system.

One that learns alongside the people who eat every day.

 
 
 

Comments


bottom of page