The real work of product building.

As we celebrate July 4th and 250 years of freedom, I hope everyone is enjoying time with family, friends, and a moment of reflection.

Over the last few years, working closely with applied agentic AI, I have become more excited than ever about what technology can do.

The technology is incredible. I love it. Proofs of concept are easier than ever to build. AI helps us evaluate tools, compare architectures, test assumptions, and explore ideas at a speed that was not possible before.

It is a great time to be a builder.

But building a product is different.

Reality

A real product cannot start with technology. It has to start with the business problem.

There is a big difference between reading about a technology and building a roadmap around it. Reading makes things feel clear. Building exposes the gaps.

This is especially hard for deeply technical people. We can see where the architecture may break. We can see what is feasible today, what is risky, and what is still just an idea. So we reason carefully. We question whether the roadmap is real, whether the product can scale, and whether the promise can actually be delivered.

At the same time, we are trying to push the boundary.

And sometimes pushing the boundary requires something beyond technology, and even beyond art.

Imagination

It requires imagination. Maybe even manifestation.

You have to believe there is a better way before it is obvious to everyone else. You have to be willing to say, sometimes awkwardly, that the existing process may not be enough anymore.

That does not mean disrespecting what exists. Existing processes were built for a reason. They solved real problems. But every now and then, the world changes enough that we have to ask a harder question:

Is there a better way?

Demonstration

That is an uncomfortable conversation. Because once you say there may be a better way, the next question is simple:

Can you prove it?

Maybe that is the real work.

Not just talking about the future. Not just writing about it. Not just debating it. But demonstrating it. Showing enough of the prototype, the discussion, the story, and the evidence that people can begin to see what you are seeing.

I try to do that.

Learnings

One thing I have learned: moving an idea forward is never just about the idea.

• Sometimes the idea is not obvious to people yet.
• Sometimes people stop coming to meetings.
• Sometimes it is a great idea, but not for now.
• Sometimes people hear the idea, disappear, and try to implement it on their own.

And sometimes they tell you directly:

“This is a bad idea.”
“This will not work.”
“This is not practical.”

Those moments can feel awkward. But they are not bad.

They are gold.

In mathematics, 1 + 1 is always 2.

But product is not mathematics.

Product involves people, ego, judgment, timing, priorities, incentives, politics, fear, ownership, and belief. In product, 1 + 1 can create infinite possibilities.

That is what makes product building hard.

And that is what makes it interesting.

Technology matters. Architecture matters. Execution matters. But the human layer matters just as much. The ability to explain, listen, adjust, absorb feedback, and still keep pushing the boundary is part of the work.

Tools like ChatGPT and Claude can help. They can organize ideas, challenge assumptions, simplify language, and accelerate thinking.

But in the end, it still comes down to storytelling, imagination, and persistence.

The real work

The best product leaders are not just explaining technology. They are helping people see a future clearly enough to question the present, believe in a better way, and build toward it together.

That is the real work.

And that is the work I am most excited about.