You have to take those concepts and prove them, a little bit like you do a PhD thesis.

I have a daily call thats 2.5 hrs with the entire team: from materials, sourcing, manufacturing, design, sensor, firmware... mechanical engineering - all together and they all have to sit through each other's updates... but then understand what those tradeoffs are and I sort of force that communication.

It has to go to the level of emotional connection, where you feel without it you're lost.

It turned out that building mobile software was a lot more like building hardware... where you had 1 shot and you had to get it right, right out of the gate.

No one is going to tell you what to build. If they did, then they should do it, not you.

What is the user problem that once we solve users can't live without?

You sort of have to separate what are questions you can ask that are going to help make you smarter about your thesis versus... trying to get somebody to validate it for you.