You gotta think about your category, your replacement cycle, usage, how these things come together and the dynamics are different.

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.

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

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.

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

I think that 'system think' is a mindset.

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.