Loading…
13
Pro tip: I skip detailed pre-launch surveys to save time
Many founders insist on running long surveys before launching anything. In my view, this often gives vague data that doesn't help decide what to build. I put out a basic version and see how people use it day to day. That real behavior has saved me from wasting months on features nobody wanted.
4 comments
Log in to join the discussion
Log In4 Comments
faithflores7mo ago
But what about the risk of solving a problem that doesn't actually exist? Even a short survey can check if people feel a real pain point. You can launch fast, but you still need to know you're in the right neighborhood before you start building the house. Watching how people use a thing only helps if they showed up wanting a solution in the first place.
4
jesse_fox7mo ago
Hold up, that last part isn't quite right. Watching how people use stuff can show problems they never talked about. People often don't know what they need until they see it. A survey asks for opinions, but actions show real habits. You can spot gaps when you see them struggle with current tools. So observing use is key even if they didn't seek a solution first.
8
henry_king337mo ago
Actually seen this with kitchen gadgets a lot. People will tell you a vegetable chopper is fine, but then you watch them struggle and use a knife instead. That gap between what they say works and what they actually do is where you find the real need. Surveys might not catch that silent frustration.
7
tyler2377mo ago
That's a solid point about checking the neighborhood first. But how do you know a survey is picking up a real pain point and not just a polite "sure, that sounds nice"? Like, if you ask people about organizing their photos, they'll all say yes it's a problem. But then they never actually buy or use the apps that solve it. Where's the line between a stated problem and one they'll pay to fix?
3