Did you conduct interviews before you started building your product? If no, why not?

Question

If yes, what did you learn that you didn't know already?

Tosin Adelowo · Accepted Answer

@thestarkster 😂 Yeah, the interviews can definitely be a distraction but everyone says it's very important. I'm of the school of thought that you should have something tangible and then speak to people

Tosin Adelowo · Answer

@llmcd I think I'm in the same boat, building something to solve my problem but the consensus seems to be that if you don't speak to users before building, you are doing it wrong. I guess there's no one size fits all for things like these

Gurkaran Singh · Answer

Well, I didn't conduct interviews before starting my product, but hey, who needs a crystal ball when you've got some good old user interviews, right? It's like debugging a code you haven't even written yet - unpredictable but essential!

Lacy McDowell · Answer

I think it depends on your defined outcome. I created a product to solve my own problem. My only outcome initially was usefulness to me. When my project came up organically in conversations, people started asking me questions about it. Then I started surveying people with some low level marketing. Currently have early access for folks to test and provide feedback.

What I learned so far is that people can be excited about a product, but it takes more effort to find the people who are willing to pay for your solution.

Did you conduct interviews before you started building your product? If no, why not?

Replies