Building Product, Talking to Users, and Growing

You should have a lot of time — compressed time in a row, really dedicated to immersing yourself in the idea and developing solutions.
The problem statement: You should be able to describe in one sentence.
Think about how does that problem relate to me and am I really passionate about that problem?
It’s a problem I have…is it a problem that other people also have?
You should really take 1 or 2 months just really understanding what all the little bits and pieces of the industry are and how it works.
It’s when you get into the details, that’s when you start seeing things you can exploit, things that are really really inefficient.
If you have a situation like mine where there is a service element of it, you should go and do that service yourself.
Your first users should be the people you are connected with.
There should be no doubt that when you’re building this that you are the expert.
You’re going to get more feedback if you just make someone pay for a product.
What you really should do to understand what you should build, is to manually do it yourself.
When someone tells you to build a feature, you shouldn’t go build it right away. But get to the bottom of why they’re asking you to build that feature.
You’re going to be tempted to try like 5 different growth strategies at 1 time. What you should do is take 1 channel and really execute on it for one entire week. Learn one channel at a time.