I think that 'system think' is a mindset.

Think about where does this stand in the experience continuum that you've been imagining, where the world's going to go.

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 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.

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

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

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.