Founders, how do you do Product Research?

Neel Patel
27 replies
We discussed this topic on our podcast episode and came with these insights: Research is not a one-off event. Think of it as continuous discovery. Research starts at your desk, don't overcomplicate it with fluff like User Diaries and Focus Groups. Remember, getting out and talking to people is crucial at some point. Research de-risks four major risks: value, usability, feasibility, and viability. The first two (value and usability) are external risks (user-centric) and require stepping out at some point. Research isn't always sequential or structured. Do what works best for you. Applied research wins - means knowing when to stop. (Focus on gathering enough data to inform product design and development) Use visualization techniques/tools. No one wants to read lengthy documents! Key highlights: industry snapshot, technology trends, key players, factors with the most investment (table stakes, must-haves), opportunities (problems with existing solutions), user profiles, and behavioral insights. Design Sprints: The juiciest way to do everything above. Are we missing anything? Here's the full episode: https://youtu.be/ACyfDCTIaS8

Replies

Eric Li
Capture
Capture
Launching soon!
Great post! I think it's important to keep things simple when you're an early stage founder. I'm the founder of a user research platform, yet I still guide 99% of founders to just go and have 1:1 conversations with customers. As an early stage founder you always want to be 1) trying to build a product people love and 2) learning how you can do #1 better. Interviews are the best way to learn, because they allow you to dig deep into what's important to a customer and why. In most cases, you'll get more actionable insights in 5 interviews than across 100 surveys or tests. These conversations don't have to be pure research interviews either. You can include discovery questions in sales calls, customer check-ins, or catch-ups with friends in your network.
Share
Neel Patel
@erictli very true. However I do believe that sometimes customers don’t know enough about the problems so can’t rely on everything they say but of course, there will be patterns.
Share
Eric Li
Capture
Capture
Launching soon!
@neelptl2602 totally agree, I think you can't rely fully on research. Ultimately, it's an input into your own intuitive decisions.
Share
Natha
@erictli Totally agree! I do 1:1 interviews twice a month as part of my routine. It's amazing how much I learn about our users' or potential users' pain points. Every conversation reveals something unique about their experiences. That conversations are gold for understanding what our customers really need.
Share
Vaibhav
You pretty much covered the essential points. Thank you for sharing!
Share
Sarah Clarck
Great episode! I appreciate the breakdown of de-risking major risks. It’s easy to get caught up in just usability and forget about feasibility and viability.
Share
Neel Patel
@sarahclarck_ Thanks for listening through it. I hope it was worth the time. We want to share what works today through NOT the people who have done it in the past but those who are doing it right now :) Would love to bring more juice in all our episodes.
Jinkal Patel
Great insights! Loved helping you on this one ;)
Share
check out google index and do some friends survey
Share
Leo Paz
When it comes to researching competitors, if you're building an AI Application theres a lot of "Ai Repositories" out there that have scraped every website with a .ai domain lol
Share
Neel Patel
@leopaz8 helps 😁
Brigid Stewart
I always include a phase of A/B testing different versions of the product to see what resonates most with users.
Share
Shadman Nazim
Great insights on product research! Continuous discovery is key. In my opinion, for a more streamlined process, consider integrating user feedback loops for real-time insights. Keep iterating! Thank you for bringing the podcast to our attention.
Share
Jake Hamilton-Daynes
When building anything, I take my own pain points as my starting point. VMS systems? Biggest issue is half of them still require ActiveX plugins and are incredibly insecure. Solution: Modern stack + focus on security. After that, I ask a handful of people (5-7) to try it out with ZERO help/advice/explanation. I then take their feedback and adapt.
Share
Neel Patel
@jakeishd Great way to go about it! Thanks for sharing 🤙🏻
Christian Onochie
I start by surveying potential users to gather insights about their needs and pain points.
Share
lilly william
Founders approach product research through a combination of methods to understand market needs, customer preferences, and competitive landscapes. They often start with market analysis, examining industry trends, target demographics, and competitor sheets set groups with potential users provide direct feedback on pain points and desired features. Founders also utilize tools like Google Trends, social media analytics, and keyword research to gauge interest and demand. Prototyping and MVP (Minimum Viable Product) testing allow for iterative improvements based on real user interactions. Finally, continuous monitoring of customer reviews, feedback forums, and industry publications helps founders stay updated and refine their products.
Share
Julia Watson
I start with online surveys to gather initial data, then in depth exploration with one-on-one interviews to understand user pain points better.
Share
Aaron hailey
For me, competitor analysis is crucial. I like to see what similar products are doing right and where they're falling short to identify opportunities.
Share
Larry Kim
I rely heavily on customer feedback and reviews from similar products. They provide real insights into what users are looking for.
Share
Lisa Stanley
I find beta testing with a small group of target users extremely useful. Their feedback helps shape the final product.
Share
Marina Morris
Collaborating with industry experts and consultants helps me understand the market landscape and validate my ideas.
Share