Asking Better Product Questions

Why “Can we build this?” is almost never the right question

When people start building a product, one question usually comes up very early:

“Can we build this?”

It sounds like a smart question. Before spending time and money, you want to know if something is possible.

But this question often pushes teams in the wrong direction.

Because once a team proves something can be built, everything changes.

Plans start forming. Time gets allocated. People become emotionally invested. What started as an idea quickly becomes a commitment.

And that is how many products get built. Not because they should exist, but because they can.

The problem with focusing on what is possible

Today, most things are technically possible.

You can automate tasks. You can generate content. You can analyse data. You can connect systems. You can build tools that did not exist a few years ago.

So the real challenge is no longer whether something can be built.

The real challenge is whether it should be built.

Does it solve a real problem? Does it make life easier for someone? Will people actually use it? Will it still make sense months or years from now?

When teams focus only on technical ability, they often create products that work perfectly but are not needed. They are impressive, but unused. Functional, but disconnected from real life.

Building something is only the beginning

Every product creates responsibility.

Someone has to maintain it. Someone has to explain how it works. Someone has to support users when things go wrong. Someone has to manage updates and improvements.

Every feature also makes things a little more complex. For users and for the team.

So the real question is not just whether you can build something.

The real question is whether you want to live with it long term.

Better questions product teams should ask

If “Can we build this?” is not the best starting point, what should we ask instead?

Here are better questions that lead to better products.

1. Should this exist at all?

This sounds obvious, but many teams skip it.

Is this solving a real problem? Or is it just interesting or new? Would anyone genuinely miss this if it disappeared?

Many ideas feel exciting. Fewer are truly necessary.

2. Who is this really for and what changes for them?

Be specific.

Not “users.” Not “customers.” A real person in a real situation.

What becomes easier for them? What becomes faster? What becomes less stressful?

If nothing meaningful changes in their daily experience, the product is not creating value.

3. What behaviour needs to change?

For a product to work, people often need to do something differently.

They may need to trust new results. Learn new steps. Change habits. Let go of control they used to have.

If using the product feels harder than staying the same, people will not adopt it. Even if it is powerful.

4. What happens if we do nothing?

This question shows how important the idea really is.

If nothing breaks, slows down, or gets worse without this product, then it may not be essential.

Products that solve urgent problems get attention. Products that solve optional problems struggle.

5. What new problems will this create?

Every solution introduces new challenges.

More complexity. More maintenance. More expectations. More things that can go wrong.

Good product thinking looks at the full picture, not just the benefits.

6. How will people learn to trust it?

A product working correctly does not automatically mean people will believe in it.

Users need to understand:

• what it does

• how it makes decisions

• when to rely on it

• when to question it

Trust has to be built intentionally.

Good product teams are good at saying no

Strong product teams are not defined by what they build.

They are defined by what they choose not to build.

Not every good idea is worth turning into a product. Not every capability needs to become a feature.

Clear thinking and restraint save time, money, and energy.

So when should we ask “Can we build this?”

It is still an important question. Just not the first one.

Ask it after you know:

• the problem is real

• the value is clear

• people will use it

• the long-term cost is acceptable

• trust can be built

Then technical feasibility matters.

Not before.

Final thought

Technology keeps expanding what we can create. But possibility alone is not a good reason to build something.

Good product thinking starts with impact, not capability.

So next time a new idea comes up, pause before asking if you can build it.

Ask whether building it will actually make someone’s life better.

That answer matters much more.