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

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

You have to have the definition of what you're trying to do across the system.

We start to try to live in tomorrow and the future, and start to think about what we build today as a stepping stone to graduate users.

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.

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

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