3 ms·
I think that may be a character thing Vince, and I don't in any way mean that as a negative. I'm a product guy, not a salesman. I think-up then create products
by pedalpete 13y ago
I think that may be a character thing Vince, and I don't in any way mean that as a negative. I'm a product guy, not a salesman. I think-up then create products (mostly websites and apps). I do it for clients, and often for myself. To me, building product is the easy part. I hate selling myself to employers or clients (though love selling my products).
When you say 'How does one get to product?' do you mean how do you build a product? Or how do you discover a market? Or how do you come up with ideas? If you can elaborate, maybe I or others on HN can help you out.
- vinceguidry 13y agoWell, a statement like Product > Strategy > Business Model and rationale behind it seems to incorporate a sort of 'hacker-level' understanding of business that I would have liked to see extended. Ramit Sethi's freelancing course had that same appeal, that you could reliably build a money-making enterprise the same way you might build a bridge. When building product, how would you boil the steps down? Do you start with ideas? Or by building tools? How do you know when you're done and it's time to move on to Strategy? What's the minimum number of things a Product has to have before you can call it a Product? As a programmer, I tend to focus on personal skills, but skills != product. Every time I start to think about product, I either get bogged down trying to make the wrong things perfect because I don't know which steps are most important. Conceptually, I might understand the basics. But turning those basics into a workable product seems overly complex.