In the hardware world, you've got to take your time because your iteration cycles are much more deliberate.

The thinking needs to shift from being less about the actual things, to being about the individual user.

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

In the hardware world, you've got to take your time because your iteration cycles are much more deliberate.

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

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.

We can dream a lot faster than what's possible.