Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

to me its marketing, sales, and support. things that i avoid learning and doing when thinking that "if i build the product the users will come".


Is that not the biggest problems for software developers? Believing that users come if they have the right product?

You need feedback to create the product and you get feedback by having customers - so go out and sell your product

(Its prop not right for all cases but in general )


For my next project I prefer:

1. Create MVP (0-100hrs work max) without talking to customers (too much) avoids paralysis. Avoids mum-test type issues too. Have some basis that it is a good idea (e.g. competitors, solving your own pain, a pain you see mentioned alot online)

2. Get MVP in front of people then talk to users.

3. Iterate based on that information: talking to people who are taking time to use your service.

It is a nice filter to talk to people who use your service (proof of work!) vs. just interviewing a bunch of people who look like they might be in your persona.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: