2 ms·
Well, a statement like Product > Strategy > Business Model and rationale behind it seems to incorporate a sort of 'hacker-level' understanding of business that
by vinceguidry 13y ago
Well, 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.