The Hardest Part of Product Management Is Not Building the Product

Many people think a Product Manager’s primary responsibility is building products.

In reality, one of the hardest parts of the job is helping people understand why they need a product in the first place.

Customers are usually very good at describing their problems. They know what frustrates them, what slows them down, and what they wish worked better.

However, customers are not always able to imagine a completely new solution.

This idea is often illustrated by a famous quote attributed to Henry Ford:

“If I had asked people what they wanted, they would have said faster horses.”

Whether Henry Ford actually said these words or not, the message remains relevant today.

People naturally think in terms of improving what already exists. They ask for faster, cheaper, simpler, or more reliable versions of current solutions because that is what they know.

Rarely do customers ask for a completely different approach to solving their problem.

A great example is the iPhone.

Before the iPhone was launched, most people were not asking for a touchscreen smartphone with an app ecosystem.

They wanted better mobile phones.

They wanted longer battery life, improved cameras, better keyboards, and stronger network connectivity.

Those were reasonable requests because they were based on existing technology.

But Steve Jobs and his team looked beyond those requests.

They recognized a larger opportunity. They saw how mobile computing, touch interfaces, and software ecosystems could come together to create an entirely new experience.

The result was not just a better phone.

It fundamentally changed how people interacted with technology.

More importantly, Apple showed customers why this new approach mattered.

This is where product management becomes challenging.

A Product Manager cannot simply collect feature requests and prioritize them in a backlog.

If we only build exactly what customers ask for, we often end up creating slightly better versions of existing products.

Instead, Product Managers must dig deeper.

We need to understand:

• What problem is the customer trying to solve?

• Why does that problem exist?

• What assumptions are limiting current solutions?

• What new technologies or approaches can create a better outcome?

Once we identify an opportunity, we must communicate it effectively.

A great idea alone is not enough.

People need to understand how the solution improves their lives, saves time, reduces costs, or creates new possibilities.

In many cases, product success depends as much on storytelling as it does on technology.

One interesting thing about innovation is that it often looks obvious after it succeeds.

Looking back, the iPhone feels inevitable.

Cloud computing feels inevitable.

Kubernetes feels inevitable.

Today, AI agents and autonomous systems may eventually feel inevitable as well.

But before these innovations became mainstream, someone had to imagine a different future and convince others to believe in it.

That requires vision, persistence, and the ability to tell a compelling story.

The best products do more than solve existing problems.

They change how people think about those problems.

As Product Managers, our responsibility is not only to listen to customers but also to understand what is possible beyond what customers can currently imagine.

Sometimes customers ask for faster horses.

Our job is to understand whether the future might actually need a car.