Ask HN: Do you conduct product/user research before writing code for a product?
I just started working with a friend on a new idea. He works as a product manager in his day job, and he insists that we need to create "personas", come up with a "lean canvas", conduct user studies and interviews etc. before we can determine a set of features and start coding. This feels like massive overkill but I haven't said anything in order to avoid coming across as close-minded.
So I wanted to ask you folks: when you have a new product idea, do you conduct product/user research first to flesh it out, or do you open your favorite code editor and start the development process right away? Or a mix of both?