234 karma · joined March 9, 2015
That being said, what's going on right now? Literally right in this moment.
What is the next, smallest, most immediate action? Do that.
The real question isn't can you have a firm grasp on the product direction/design wheel at a small company. It's can you build something anyone wants at all.
Secondly, can you make a sustainable business at all?
Just build something people want. The rest might follow.
Pay might be a factor. I think people are people, and their behavior and beliefs vary.
Some links: https://www.productplan.com/product-manager-vs-product-owner... https://blog.aha.io/the-product-manager-vs-product-owner/ https://blog.aha.io/product-manager-vs-product-owner-vs-proj... https://www.productplan.com/glossary/product-owner/ https://blog.aha.io/the-product-vs-project-vs-program-manage... https://www.mironov.com/?s=product+owner
As an investment, or a place to live?
What are the alternatives for investing? They might be better, they might not be.
If the time frame you're considering is long enough, presumably yes, it's a great time. And if your time frame is even longer, the answer is it doesn't really matter :)
Both seem about equally likely to lead to Director / VP level positions if you excel. Maybe EM slightly more, but it's similar. You can start one now, the other takes more interviewing or possibly an MBA.
Day to day they will be kind of different. Do you want to worry about how to manage a team of engineers well, help with their professional and personal development, and get them the resources they need? Or help your company figure out what to build, for whom, figure out if that's working, etc? Both require operating well cross functionally, product especially.
If you care equally, I'd do engineering management now. Less resistance, and you can always go into product and / or get an MBA later.
What is an isn't a high bar is all relative.
Summary: Clearly identify a problem, issues with existing solutions, and that it's a priority worth paying for among potential customers.
Validate even MORE about the problem, AND the solution, before building out the solution in a substantial way, or at all. Is the problem clear to the people who have it, and one of their top priorities? Find out by communicating with them, ideally in person, but video chat works and written forms if that's all that is possible. If a competitor exists, great! What's the value proposition of your similar product/service? Why is it so good someone who uses another should switch, or what makes it compelling for someone who is evaluating your product/service?
Instead of positive interest, how many people will sign up in a form you link them to, or a landing page? How many will give their email or some contact information so that you contact them when your thing launches? How many say "I have $x and I will pay you that right now if you make this problem go away!"? How many people will read your blog post about how frustrating a certain problem is? Saying "Yeah, I hate that problem", but not being willing to do anything else. That might a dead end.
Another strategy is to build something that solves your own problem. Minimally, it will be useful to you. If it's useful to you, you won't be putting "effort into something nobody wants". If you have the problem, there's a good chance others do, too, and they may be willing to use and/or pay for your solution. Alternatively, after validating the problem and a potential solution, you can build something for someone you're close to that solves their problem. A spouse, family member, good friend, etc. Small frequent feedback loops, and empathy, are key here.
Another shortcut to running your own software business is starting a software consultancy. You can even do this while you have a day job, by hiring other people to do parts of it, or with smaller projects. If you have many of a similar type of customer (law offices, realtors, whatever), you can find the right product that applies to many of them, while being paid to build other things for your client, or this product itself. This is a traditional approach to bootstrapping a software product, and lots of other people have written or spoken about the it and its trade offs.
What succeeds on 'Show HN' and Product Hunt and similar things isn't predictable. It also doesn't lead to instant success, product usage, or paying customers. It's nice I would imagine, people have shown what it meant in terms of visitors and traction, but it's a blip in the life of a product. Having customers that use your product and pay you money would be better, and it's a bit more in your control.
Here's a good link about validating without spending money or building anything: https://www.startupgrind.com/blog/the-startup-framework-to-v...
Short book on meditation: https://www.amazon.com/Sit-Like-Buddha-Pocket-Meditation/dp/...
Longer book: https://www.amazon.com/Mind-Illuminated-Meditation-Integrati...
Also, try some guidelines to help you choose more intentionally when and how to analyze things. Is it no topic is worth thinking through all outcomes? Or, important topics are worth it, and they are x, y and z? Or, I can do that type of thinking only an hour a day, from 7-8pm? Once a week? A therapist and trial and error can help you figure out what works for you.
Have a counterfactual behavior that you'll do when you notice you're analyzing when you didn't intend to. E.g. if I notice I'm thinking through scenarios, I'll acknowledge that, then focus on my breath.
It might also lead to a good offer you can use to help get better comp / title / growth opportunities / autonomy at your current job.
People on HN have recommended Design for Hackers https://designforhackers.com/
Learn about the design process https://www.slideshare.net/Klonowsa/design-process-overview-...
Some resources on prototyping https://www.productmanual.co/categories/prototyping
Some resources on interaction design https://www.productmanual.co/categories/interaction-design
This book is popular for people wanting to learn a little more about design. It's on my list of things to read. https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things
An application of design that is useful for projects and companies is the Google Ventures sprint is useful http://www.gv.com/sprint/
What your saying about knowing how to use Yelp is right on, but it leads to some dissatisfaction, because a 4 star restaurant should be a 4 star restaurant. More importantly, they manipulate ratings. They pressure businesses to pay them to fix ratings Yelp broke. They let businesses improve ratings when they shouldn't, analogous to Glassdoor and Amazon users getting ratings they don't like kicked off or hidden. There are plenty of fake and misleading reviews. And they have lots of dark patterns e.g. pushing you to their mobile app from the web, requiring you to create an account, etc. Some of these are observable by everyone, others there are many anecdotes.
They're not going away. They provide value to people, me included. But some negativity directed their way makes sense to me.