Before You Build Anything, Answer This One Question

Every time I start something new, I come back to the same question: what problem am I actually trying to solve? Not the polished version. Not the one that sounds good on a website. The real one.

Because if you get this wrong, everything else is just movement without direction.

Is it my problem?

This is where I always start. And it’s uncomfortable.

If the problem isn’t mine, I’m immediately suspicious. Not because you can’t solve other people’s problems—but because it’s much harder to care enough when things get difficult. And they always get difficult.

When a problem is yours, you don’t need motivation. You’re already annoyed by it. You’ve already lost time because of it. You’ve already thought, there has to be a better way.

So I ask myself:

• Have I personally struggled with this?

• Has this problem followed me around for years?

• Do I feel it when I’m tired, stressed, or stuck?

If the answer is yes, that’s a good sign. But it’s not enough.

How big is it?

Not in market-size terms. In life terms.

How often does this problem show up? Every day? Every project? Every time I try to move forward?

The problems worth solving usually aren’t dramatic. They’re repetitive. Quiet. They slowly drain people instead of breaking them all at once.

Then I look around.
Do I know other people dealing with the same thing?

Founders. Creators. Friends. People who complain about the same frustration without realizing it’s shared.

And when I find them, I talk to them. Not to pitch. Not to convince. Just to understand.

I ask simple questions:

• When does this problem hurt the most?

• What have you tried to fix it?

• Why didn’t it work?

I listen more than I talk. Because most of the time, the real insight isn’t in the answers—it’s in the pauses, the frustration, the repetition.

Or is it an opportunity problem?

Sometimes the problem isn’t personal. Sometimes I’m not bleeding from it—but I can see it clearly.

These are opportunity problems. Friction people have accepted as normal. Inefficiencies hidden behind “that’s just how it’s done.”

There’s nothing wrong with starting here. But it’s riskier.

Because when the problem isn’t mine, I can easily misunderstand it. I can assume things. I can oversimplify.

So I slow down even more.

I ask:

• How many people actually experience this problem?

• How often does it show up in their lives?

• What does it cost them in time, energy, or money?

• What happens if it never gets solved?

If the answers feel vague or small, I walk away. Life’s too short to build solutions for mild inconveniences.

Then I do the real work: I talk to the people living with that problem every day.

Companies. Teams. Individuals.

I interview them properly. No leading questions. No validation hunting. I let them explain the problem in their own words, even if it challenges my assumptions.

Especially if it challenges my assumptions.

Why I care so much about this

Because I’ve learned the hard way that being busy is not the same as being right.

You can build fast. You can design beautifully. You can market aggressively. And still fail—because you never truly understood the problem.

For me, clarity always comes first.

If the problem is mine, I’ll stay with it longer.
If it’s big, others will recognize themselves in it.
If I listen before I build, I give myself a real chance.

I don’t want to create noise. I want to fix something that actually matters—even if it’s small, even if it’s quiet.

Everything meaningful I’ve seen starts this way.
With honesty.
With listening.
With the courage to sit with the problem long enough to really understand it.

That’s the work.
And that’s where it always begins.

Emidio