Skip to main content
Business
4 min read

The questions I ask before building a product

Contents

A product can work as designed and still struggle when the problem, audience, or distribution is unclear.

Working across different companies taught me to check the problem, the audience, and how people will find the product before committing to the build.

Across the products I have built and advised, I have seen teams struggle even when the software worked. Sometimes they needed a clearer understanding of the customer, the problem, or how people would find the product.

A working product and encouraging launch feedback are useful. They still leave a question: will people have a reason to return?

Check the assumptions behind the build

In a 2026 survey of 200 founders by Wilbur Labs, 42% wished they had changed direction or their business model sooner. That does not explain every failure, but it is a reason to revisit assumptions while there is still time to change them.

Three upstream failures I keep seeing

Three questions keep coming up in my product work: are we solving the right problem, for the right people, and do we know how to reach them?

Wrong problem

Building a solution before understanding the problem deeply enough. This is the most common one. The team falls in love with the solution and works backward to find a problem it fits.

At Openfair, buyers needed clear financial information before they could decide whether to contact a seller. We put revenue, profit, and asking price on listing cards. That need shaped the product more usefully than a broad brief to build a marketplace.

The lesson: problem clarity comes before product clarity. If you cannot describe the problem in one sentence that a stranger would nod at, the product is building on assumptions.

Wrong audience

Building for the audience you want instead of the audience that has the problem. This one is subtle because the audience you want is often the audience that looks good in a pitch deck, not the audience that will use the product daily.

At Paper, schools bought the platform and students used it to get help. Both mattered. Students hesitated on the topic-selection screen, so we showed the selector over a preview of the chat. Session starts rose by about 25%. Watching the students helped us fix something a conversation with the buyer alone would have missed.

Talk to the people who use the product as well as those who buy it. Their needs can be different, and the product has to account for both.

Wrong distribution

A team also needs a practical plan for reaching its first users. Launching the website does not answer that question.

For a healthcare directory such as 1Health, that means thinking about patients and providers separately. Patients need relevant options when they search for care; providers need a reason to keep their profiles useful and current.

I want a clear answer to how the first users will find the product and what will bring them back.

What I do instead

Before any build starts, I answer three questions. Who has this problem? How do they solve it today? What would make them switch? If I cannot answer all three with specifics, not abstractions, I am not ready to build.

Broad answers such as “everyone” or “a better solution” need more work. I want to know who has the problem and what makes their current way of handling it difficult.

At Grindstone, I started by watching how people worked across the portfolio companies. Mapping the tasks, tools, and handoffs helped us choose which software to build and which processes to improve.

A roadmap is a list of bets. The bets should be on the problem, not the feature. I wrote about this before: a roadmap is a list of bets. The best roadmaps I have run were the ones I was willing to tear up by Friday.

The interface matters once we understand the task. I wrote about that relationship in the best interfaces are the ones you don’t notice.

A test you can run this week

Describe the product to someone outside the team, ideally someone who has the problem you are trying to solve.

Ask how they handle it today, what is difficult, and what would make a change worthwhile. A positive reaction to the description is a starting point. I would still want to see whether they use the product.

I use those conversations to adjust the problem definition and decide what to test next.

Working through a company problem?

Tell me what is changing, what is getting in the way, and what outcome matters now.

Let’s talk