Most failures stem from solving non-problems

I think the simplest place to go when you see a failed product is to ask yourself, what problem did you solve? And I could get into all kinds of other examples outside of Amazon too, but 9 times out of 10, I think that's where... If it wasn't poor execution, if the product was executed correctly, what was wrong with the concept of the product?

The weird aspect of what we call a tarpit idea is an idea that a lot of people come up with and then it seems like an unsolved problem and you get lots of positive feedback for.

One of the biggest things I see, not just in my course but also just as a PM and some of the mistakes that you make as a PM is the idea of you get really attached to a solution.

You don't have to know how to write this spec or PRD or briefings, but instead show your passion around the product itself, around the use case, around the customer. Show who you are and why you care. You have to be able to fall in love with the problem.